Mercurial > repos > metexplore > met4j
comparison build/tools/BipartiteDistanceMatrix/BipartiteDistanceMatrix.xml @ 6:7a6f2380fc1d draft
planemo upload for repository https://forgemia.inra.fr/metexplore/met4j-galaxy
| author | metexplore |
|---|---|
| date | Wed, 17 May 2023 13:26:37 +0000 |
| parents | |
| children | 1436e9cde9c9 |
comparison
equal
deleted
inserted
replaced
| 5:35c9abcd8934 | 6:7a6f2380fc1d |
|---|---|
| 1 <?xml version="1.0" encoding="UTF-8"?> | |
| 2 <tool id="met4j_BipartiteDistanceMatrix" name="BipartiteDistanceMatrix" version="1.3.0"> | |
| 3 <description>Create a compound to reactions distance matrix.</description> | |
| 4 <xrefs> | |
| 5 <xref type="bio.tools">met4j</xref> | |
| 6 </xrefs> | |
| 7 <requirements> | |
| 8 <container type="singularity">oras://registry.forgemia.inra.fr/metexplore/met4j/met4j-singularity:1.3.0</container> | |
| 9 </requirements> | |
| 10 <command detect_errors="exit_code"><![CDATA[sh /usr/bin/met4j.sh networkAnalysis.BipartiteDistanceMatrix -i "$inputPath" | |
| 11 #if str($sideCompoundFile) != 'None': | |
| 12 -sc "$sideCompoundFile" | |
| 13 #end if | |
| 14 #if str($rExclude) != 'None': | |
| 15 -re "$rExclude" | |
| 16 #end if | |
| 17 #if str($metFile) != 'None': | |
| 18 -m "$metFile" | |
| 19 #end if | |
| 20 #if str($rxnFile) != 'None': | |
| 21 -r "$rxnFile" | |
| 22 #end if | |
| 23 #if str($weightFile) != 'None': | |
| 24 -w "$weightFile" | |
| 25 #end if | |
| 26 $undirected | |
| 27 $full | |
| 28 -o "$outputPath" | |
| 29 ]]></command> | |
| 30 <inputs> | |
| 31 <param argument="-i" format="sbml" label="input SBML file" name="inputPath" optional="false" type="data" value=""/> | |
| 32 <param argument="-sc" format="txt" label="an optional file containing list of side compounds to ignore" name="sideCompoundFile" optional="true" type="data" value=""/> | |
| 33 <param argument="-re" format="txt" label="an optional file containing list of reactions to ignore" name="rExclude" optional="true" type="data" value=""/> | |
| 34 <param argument="-m" format="txt" label="an optional file containing list of compounds of interest." name="metFile" optional="true" type="data" value=""/> | |
| 35 <param argument="-r" format="txt" label="an optional file containing list of reactions of interest." name="rxnFile" optional="true" type="data" value=""/> | |
| 36 <param argument="-w" format="tsv" label="an optional file containing weights for compound pairs" name="weightFile" optional="true" type="data" value=""/> | |
| 37 <param argument="-u" checked="false" falsevalue="" label="Ignore reaction direction" name="undirected" truevalue="-u" type="boolean" value="false"/> | |
| 38 <param argument="-f" checked="false" falsevalue="" label="compute full pairwise matrix from both reactions and compounds lists" name="full" truevalue="-f" type="boolean" value="false"/> | |
| 39 </inputs> | |
| 40 <outputs> | |
| 41 <data format="csv" name="outputPath"/> | |
| 42 </outputs> | |
| 43 <tests/> | |
| 44 <help><![CDATA[Create a compound to reactions distance matrix. | |
| 45 The distance between two nodes (metabolite or reaction) is computed as the length of the shortest path connecting the two in the bipartite graph, Bipartite graph are composed of two distinct sets of nodes and two nodes can be linked only if they are from distinct sets. | |
| 46 Therefore a metabolite node can be linked to a reaction node if the metabolite is a substrate or product of the reaction. | |
| 47 An optional custom edge weighting can be used, turning the distances into the sum of edge weights in the lightest path, rather than the length of the shortest path.Custom weighting can be provided in a file. In that case, edges without weight are ignored during path search. | |
| 48 If no edge weighting is set, it is recommended to provide a list of side compounds to ignore during network traversal.]]></help> | |
| 49 <citations/> | |
| 50 </tool> |