add checkm2 #6542
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| name: checkm2 | ||
| owner: iuc | ||
| description: Rapid assessment of genome bin quality using machine learning | ||
| long_description: Enhanced version of checkm, using machine learning models for greater speed and accuracy | ||
| homepage_url: https://github.com/chklovski/CheckM2 | ||
| remote_repository_url: https://github.com/galaxyproject/tools-iuc/ | ||
| categories: | ||
| - Metagenomics | ||
| type: unrestricted | ||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,124 @@ | ||||||
| <tool id="checkm2" name="checkm2" version="@TOOL_VERSION@+galaxy@VERSION_SUFFIX@" profile="23.1"> | ||||||
| <description>Rapid assessment of genome bin quality using machine learning</description> | ||||||
| <macros> | ||||||
| <token name="@TOOL_VERSION@">1.0.2</token> | ||||||
| <token name="@VERSION_SUFFIX@">0</token> | ||||||
| <token name="@IDX_DATA_TABLE@">checkm2</token> | ||||||
| </macros> | ||||||
| <xrefs> | ||||||
| <xref type="bio.tools">checkm</xref> | ||||||
| </xrefs> | ||||||
| <requirements> | ||||||
| <requirement type="package" version="@TOOL_VERSION@">checkm2</requirement> | ||||||
| </requirements> | ||||||
| <command detect_errors="exit_code"><![CDATA[ | ||||||
| #import re | ||||||
| mkdir input_dir && | ||||||
| #for $i, $file in enumerate($input): | ||||||
| #set $cleaned = re.sub('[^\s\w\-\\.]', '_', str($file.element_identifier)) | ||||||
| ln -s $file input_dir/${cleaned}.dat && | ||||||
|
There was a problem hiding this comment.
Suggested change
|
||||||
| #end for | ||||||
| checkm2 predict | ||||||
| --input input_dir | ||||||
| $model | ||||||
| $genes | ||||||
| #if $ttable: | ||||||
| --ttable $ttable | ||||||
| #end if | ||||||
| -x .dat | ||||||
| --threads "\${GALAXY_SLOTS:-1}" | ||||||
| --database_path '$database.fields.path' | ||||||
| --output-directory output | ||||||
| ]]></command> | ||||||
| <inputs> | ||||||
| <param name="input" type="data" format="fasta" label="Input MAG/SAG datasets" multiple="true"/> | ||||||
| <param name="database" type="select" label="Select reference genome" help="Checkm2 Diamond database"> | ||||||
|
There was a problem hiding this comment. Would it be of interest if users upload their own dmnd databases (https://github.com/galaxyproject/tools-iuc/blob/main/tools/diamond/diamond_makedb.xml)? There was a problem hiding this comment. Based on the wording on their repo, I was under the impression you needed to use their specific diamond db? |
||||||
| <options from_data_table="@IDX_DATA_TABLE@"> | ||||||
| <filter type="sort_by" column="2"/> | ||||||
| </options> | ||||||
| <validator type="no_options" message="No databases are available for this version of Checkm2. Please contact the Galaxy adminstrators to request one be installed."/> | ||||||
| </param> | ||||||
|
|
||||||
| <param argument="genes" type="boolean" truevalue="--genes" falsevalue="" label="Treat input files as protein files"/> | ||||||
| <param name="model" type="select" label="Model options"> | ||||||
| <option value="">None</option> | ||||||
| <option value="--general">Force the use of the general quality prediction model (gradient boost)</option> | ||||||
| <option value="--specific">Force the use of the specific quality prediction model (neural network)</option> | ||||||
| <option value="--allmodels">Output quality prediction for both models for each genome.</option> | ||||||
| </param> | ||||||
| <!-- It's not all numbers and there's a check internally if it's in a specific list, so it had to be spelled out --> | ||||||
| <param argument="ttable" type="select" label="Prodigal table" optional="true"> | ||||||
| <option value="1">1. The Standard Code</option> | ||||||
| <option value="2">2. The Vertebrate Mitochondrial Code</option> | ||||||
| <option value="3">3. The Yeast Mitochondrial Code</option> | ||||||
| <option value="4">4. The Mold, Protozoan, and Coelenterate Mitochondrial Code and the Mycoplasma/Spiroplasma Code</option> | ||||||
| <option value="5">5. The Invertebrate Mitochondrial Code</option> | ||||||
| <option value="6">6. The Ciliate, Dasycladacean and Hexamita Nuclear Code</option> | ||||||
| <option value="9">9. The Echinoderm and Flatworm Mitochondrial Code</option> | ||||||
| <option value="10">10. The Euplotid Nuclear Code</option> | ||||||
| <option value="11">11. The Bacterial, Archaeal and Plant Plastid Code</option> | ||||||
| <option value="12">12. The Alternative Yeast Nuclear Code</option> | ||||||
| <option value="13">13. The Ascidian Mitochondrial Code</option> | ||||||
| <option value="14">14. The Alternative Flatworm Mitochondrial Code</option> | ||||||
| <option value="16">16. Chlorophycean Mitochondrial Code</option> | ||||||
| <option value="21">21. Trematode Mitochondrial Code</option> | ||||||
| <option value="22">22. Scenedesmus obliquus Mitochondrial Code</option> | ||||||
| <option value="23">23. Thraustochytrium Mitochondrial Code</option> | ||||||
| <option value="24">24. Rhabdopleuridae Mitochondrial Code</option> | ||||||
| <option value="25">25. Candidate Division SR1 and Gracilibacteria Code</option> | ||||||
| <option value="26">26. Pachysolen tannophilus Nuclear Code</option> | ||||||
| <option value="27">27. Karyorelict Nuclear Code</option> | ||||||
| <option value="28">28. Condylostoma Nuclear Code</option> | ||||||
| <option value="29">29. Mesodinium Nuclear Code</option> | ||||||
| <option value="30">30. Peritrich Nuclear Code</option> | ||||||
| <option value="31">31. Blastocrithidia Nuclear Code</option> | ||||||
| <option value="33">33. Cephalodiscidae Mitochondrial UAA-Tyr Code</option> | ||||||
| </param> | ||||||
| </inputs> | ||||||
| <outputs> | ||||||
| <data name="quality" label="${tool.name} on ${on_string}: Quality report" format="tabular" from_work_dir="output/quality_report.tsv"/> | ||||||
| <collection name="protein_files" label="${tool.name} on ${on_string}: protein files" type="list"> | ||||||
| <discover_datasets pattern="__name__" format="fasta" directory="output/protein_files"/> | ||||||
|
There was a problem hiding this comment.
There was a problem hiding this comment. is there a difference between |
||||||
| </collection> | ||||||
| <collection name="diamond_files" label="${tool.name} on ${on_string}: Diamond files" type="list"> | ||||||
|
There was a problem hiding this comment. Should we add here that this is of type |
||||||
| <discover_datasets pattern="__name__" ext="tsv" directory="output/diamond_output"/> | ||||||
| </collection> | ||||||
| </outputs> | ||||||
| <tests> | ||||||
| <!-- These cannot run without a multi-gb db and will therefore fail. See README for details --> | ||||||
| <test expect_exit_code="1" expect_failure="true"> | ||||||
| <param name="input" value="test1.faa,test2.faa"/> | ||||||
| <param name="model" value="--allmodels"/> | ||||||
| <param name="genes" value="--genes"/> | ||||||
| <param name="ttable" value="13"/> | ||||||
| <assert_command> | ||||||
| <has_text text="checkm2 predict --input input_dir"/> | ||||||
| <has_text text="--allmodels --genes --ttable 13 -x .dat"/> | ||||||
| <has_text text="--output-directory output"/> | ||||||
| </assert_command> | ||||||
| </test> | ||||||
| <test expect_exit_code="1" expect_failure="true"> | ||||||
| <param name="input" value="test1.tst,test2.tst"/> | ||||||
| <param name="model" value="--specific"/> | ||||||
| <assert_command> | ||||||
| <has_text text="checkm2 predict --input input_dir"/> | ||||||
| <has_text text="--specific -x .dat"/> | ||||||
| <has_text text="--output-directory output"/> | ||||||
| </assert_command> | ||||||
| </test> | ||||||
| </tests> | ||||||
| <help><![CDATA[ | ||||||
| Unlike CheckM1, CheckM2 has universally trained machine learning models it applies regardless of taxonomic lineage to predict the completeness and contamination of genomic bins. | ||||||
| This allows it to incorporate many lineages in its training set that have few - or even just one - high-quality genomic representatives, by putting it in the context of all other organisms in the training set. | ||||||
| As a result of this machine learning framework, CheckM2 is also highly accurate on organisms with reduced genomes or unusual biology, such as the Nanoarchaeota or Patescibacteria. | ||||||
|
|
||||||
| CheckM2 uses two distinct machine learning models to predict genome completeness. The 'general' gradient boost model is able to generalize well and is intended to be used on organisms not well | ||||||
| represented in GenBank or RefSeq (roughly, when an organism is novel at the level of order, class or phylum). The 'specific' neural network model is more accurate when predicting completeness | ||||||
| of organisms more closely related to the reference training set (roughly, when an organism belongs to a known species, genus or family). CheckM2 uses a cosine similarity calculation to automatically | ||||||
| determine the appropriate completeness model for each input genome, but you can also force the use of a particular completeness model, or get the prediction outputs for both. There is only one contamination | ||||||
| model (based on gradient boost) which is applied regardless of taxonomic novelty and works well across all cases. | ||||||
| ]]></help> | ||||||
| <citations> | ||||||
| <citation type="doi">10.1038/s41592-023-01940-w</citation> | ||||||
| </citations> | ||||||
| </tool> | ||||||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ##Checkm2 versioned indexes | ||
| #build_id display_name path version | ||
| 001 test_db ${__HERE__}/Checkm2_database/uniref100.KO.1.dmnd 1.0.2 |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This could be more precise pointing to the folder.