Add Cleaverna tool#1739
Conversation
bgruening
left a comment
There was a problem hiding this comment.
- can you please remove the entire planemo/lib/ folder
- please add a .shed.yml
- please add https://docs.galaxyproject.org/en/latest/dev/schema.html#tool-required-files-include for all your data files
- please add a creator https://docs.galaxyproject.org/en/latest/dev/schema.html#tool-creator-person
|
|
||
| <xml name="training_prediction_mode"> | ||
| <param name="prediction_mode" type="select" label="Analysis mode" hidden="true"> | ||
| <option value="default" selected="true">Default - Standard cleavage site prediction</option> |
There was a problem hiding this comment.
is there any other option? Otherwise, we can skip this select box isn't it?
There was a problem hiding this comment.
is there any other option? Otherwise, we can skip this select box isn't it?
Yes, in training mode it’s just set to “default,” and we can skip it.
| echo "16,8,\"AU,GU\",23,GGCUAGCUACAACGA" >> SARS_default_params.csv && \ | ||
| cleaverna \ | ||
| --model_name "${mode_selection.training_source.model_name}" \ | ||
| --target_files_training '${__tool_directory__}/data/1.fasta' '${__tool_directory__}/data/2.fasta' '${__tool_directory__}/data/3.fasta' '${__tool_directory__}/data/4.fasta' '${__tool_directory__}/data/5.fasta' '${__tool_directory__}/data/6.fasta' '${__tool_directory__}/data/7.fasta' '${__tool_directory__}/data/8.fasta' '${__tool_directory__}/data/9.fasta' '${__tool_directory__}/data/10.fasta' '${__tool_directory__}/data/11.fasta' '${__tool_directory__}/data/12.fasta' '${__tool_directory__}/data/13.fasta' '${__tool_directory__}/data/14.fasta' '${__tool_directory__}/data/15.fasta' '${__tool_directory__}/data/16.fasta' '${__tool_directory__}/data/17.fasta' '${__tool_directory__}/data/18.fasta' '${__tool_directory__}/data/19.fasta' '${__tool_directory__}/data/20.fasta' \ |
There was a problem hiding this comment.
would it make sense to put all those files into one FASTA file?
There was a problem hiding this comment.
would it make sense to put all those files into one FASTA file?
The tool currently accepts multiple FASTA files, but I can add this option if needed.
There was a problem hiding this comment.
I think that would make it much easier for us to pass in the database(s) here. One single file
|
|
||
| --output_dir outputs | ||
| #end if | ||
| && ls -la outputs/ |
There was a problem hiding this comment.
remove at the end when you are finished
| </param> | ||
| <when value="individual"> | ||
| <param name="LA" type="integer" min="1" max="50" value="15" label="LA - Left arm length" help="The length of the left binding arm of DNAzyme (1-50 nucleotides)"> | ||
| <validator type="in_range" min="1" max="50" message="Left arm length must be between 1 and 50"/> |
There was a problem hiding this comment.
I think you can remove the validator since you restirct the main param with min/max
| <option value="false">No - Hide file details</option> | ||
| </param> | ||
| <when value="true"> | ||
| <param name="training_dataset_info" type="text" value="HPBC_user_merged_num.csv" |
There was a problem hiding this comment.
that is strange, this is a text param but you want a file?
| </repeat> | ||
|
|
||
| <param name="output_info" type="text" | ||
| value="📋 Output format: LA,RA,CS,Start_End_Index,Tem,CA (Start_End_Index format: target_file.fasta:start-end)" |
There was a problem hiding this comment.
is that value correct? its a bit strange and I don't think a user can manipulate this.
| </outputs> | ||
| <tests> | ||
| <!-- Updated test: Training mode with all required fields --> | ||
| <test expect_num_outputs="2"> |
There was a problem hiding this comment.
we need many more tests here, for each conditional at least one ... again the galaxy-lanuage server can help here and generate tests.
| For detailed instructions and parameter descriptions, please refer to the tool documentation. | ||
| </help> | ||
| <citations> | ||
| <citation type="bibtex"> |
Co-authored-by: Björn Grüning <[email protected]>
|
Something went wrong here in the branch? I think you need to rebase against the latest master-git branch. Or you create a new PR with your tool. |
I updated the branch. Is the problem fixed now, or should I create a new branch? |
bgruening
left a comment
There was a problem hiding this comment.
please take the PR out of Draft mode, if you think its ready
I want to add more tests and change some header words to be more user-friendly. I will take it out of draft as soon as I am done with these changes. |
|
@reyhaneh-tavakoli if this one is ready please take it out of the draft mode. |
|
@bgruening |
|
Hi Björn, |
| <include path="data/BCL-3.fasta"/> | ||
| <include path="data/BCL-4.fasta"/> | ||
| <include path="data/BCL-5.fasta"/> | ||
| <include path="data/HPBC_generated_train_dataset.csv"/> |
There was a problem hiding this comment.
This is one of the large files, but where is it used?
Can you check if all files are actually used?
There was a problem hiding this comment.
This is one of the large files, but where is it used?
Can you check if all files are actually used?
I have reviewed and updated them. However, we still have files exceeding 1MB that are necessary as inputs for the prediction step.
|
@bgruening Thank you very much for your guidance. |
|
Forget about the file-size we can merge it with that if you like. But planemo test is also failing, you see the error messages here; https://github.com/bgruening/galaxytools/actions/runs/22135865788 |
| --model_name "${mode_selection.training_source.model_name}" \ | ||
| --target_files_training '${__tool_directory__}/data/HPV.fasta' '${__tool_directory__}/data/BCL-1.fasta' '${__tool_directory__}/data/BCL-2.fasta' '${__tool_directory__}/data/BCL-3.fasta' '${__tool_directory__}/data/BCL-4.fasta' '${__tool_directory__}/data/BCL-5.fasta' \ | ||
| --params HPBC_default_params.csv \ | ||
| --prediction_mode default \ |
There was a problem hiding this comment.
This should be selected from prediction_prediction_mode
| --model_name "${mode_selection.training_source.model_name}" \ | ||
| --target_files_training '${__tool_directory__}/data/1.fasta' '${__tool_directory__}/data/2.fasta' '${__tool_directory__}/data/3.fasta' '${__tool_directory__}/data/4.fasta' '${__tool_directory__}/data/5.fasta' '${__tool_directory__}/data/6.fasta' '${__tool_directory__}/data/7.fasta' '${__tool_directory__}/data/8.fasta' '${__tool_directory__}/data/9.fasta' '${__tool_directory__}/data/10.fasta' '${__tool_directory__}/data/11.fasta' '${__tool_directory__}/data/12.fasta' '${__tool_directory__}/data/13.fasta' '${__tool_directory__}/data/14.fasta' '${__tool_directory__}/data/15.fasta' '${__tool_directory__}/data/16.fasta' '${__tool_directory__}/data/17.fasta' '${__tool_directory__}/data/18.fasta' '${__tool_directory__}/data/19.fasta' '${__tool_directory__}/data/20.fasta' \ | ||
| --params SARS_default_params.csv \ | ||
| --prediction_mode default \ |
There was a problem hiding this comment.
This should be selected from prediction_prediction_mode
| #else: | ||
| #if $mode_selection.training_source.advanced_dnazyme_params.param_source.param_mode == "manual": | ||
| echo "LA,RA,CS,Tem,CA" > temp_params.csv && | ||
| #set $cs_list = ','.join($mode_selection.training_source.advanced_dnazyme_params.param_source.CS) |
There was a problem hiding this comment.
Is CS defined in param_source
|
Thanks @reyhaneh-tavakoli. It looks like that you have used too much nested macros and sections. Is it possible to somehow reduce that? It makes it much easier to review and help. cheers |
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Co-authored-by: Amirhossein Nilchi <[email protected]>
Hi Amir, Thank you for reviewing my PR and for your comments and suggestions. I’ve updated the branch based on your commits. Some parts are still pending, as I need more time to focus on them after this long gap. I’d like to reduce nested macros and sections, but I need some help with this, as well as a stable internet connection to work on it. Unfortunately, I currently have limited internet access. I’m working on it whenever I can and would really appreciate any guidance or support. Thanks again! |
@bgruening
Hi Bjorn, Merry Christmas!
This pull request adds the Cleaverna tool to the Galaxy platform. The tool supports two execution modes: Training and Prediction. In both modes, it requires a parameter CSV file as input. To facilitate proper usage within Galaxy, this XML file is written so that it can generate the required CSV file directly using Galaxy tools, allowing it to be passed seamlessly as input to Cleaverna.
Could you please review my PR and check whether the CSV file generation part is defined correctly?