Mercurial > repos > chemteam > ambertools_acpype
comparison acpype.xml @ 0:2e202f6c3034 draft
planemo upload for repository https://github.com/galaxycomputationalchemistry/galaxy-tools-compchem/ commit f1620d2eb7fd3ea43bb4dfe6cee5b45015fd13a3
author | chemteam |
---|---|
date | Thu, 13 Jun 2019 06:16:34 -0400 |
parents | |
children | 597ee2f97479 |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:2e202f6c3034 |
---|---|
1 <tool id="ambertools_acpype" name="Generate MD topologies for small molecules" version="@VERSION@"> | |
2 <description>using acpype</description> | |
3 <macros> | |
4 <import>macros.xml</import> | |
5 </macros> | |
6 <expand macro="requirements"> | |
7 <requirement type="package" version="0.1.0">acpype</requirement> | |
8 </expand> | |
9 <command detect_errors="exit_code"><![CDATA[ | |
10 ln -s '$input1' ./input1.${input1.ext} && | |
11 acpype -i './input1.${input1.ext}' | |
12 -n '$charge' | |
13 -b base | |
14 -m '$multiplicity' | |
15 -a '$atomtype' | |
16 -o gmx | |
17 ]]></command> | |
18 <inputs> | |
19 <param name="input1" type="data" format="pdb,mol2" label="Input file" help="Structure of the compound in pdb or mol2 format"/> | |
20 <param name="charge" type="integer" value="0" label="Charge of the molecule"/> | |
21 <param name="multiplicity" type="integer" value="1" label="Multiplicity" help="Default value is 1, which is correct for almost all organic molecules."/> | |
22 <param name="atomtype" type="select" value="gaff" label="Force field to use for parameterization"> | |
23 <option value="gaff">gaff</option> | |
24 <option value="amber">AMBER14SB</option> | |
25 <option value="gaff2">gaff2</option> | |
26 <option value="amber2">AMBER14SB + gaff2</option> | |
27 </param> | |
28 <param name="save_gro" type="boolean" value="false" label="Save GRO file?" help="Save atomic coordinates of ligand in GRO format."/> | |
29 </inputs> | |
30 <outputs> | |
31 <data format="itp" name="output" label="Topology" from_work_dir='base.acpype/base_GMX.itp'/> | |
32 <data format="gro" name="gro_output" label="Structure file (GRO format, optional)" from_work_dir="base.acpype/base_GMX.gro"> | |
33 <filter>save_gro</filter> | |
34 </data> | |
35 </outputs> | |
36 <tests> | |
37 <test> | |
38 <param name="input1" value="JZ4.mol2"/> | |
39 <param name="save_gro" value="True"/> | |
40 <output name="output"> | |
41 <assert_contents> | |
42 <has_line line="[ atoms ]"/> | |
43 <has_text text=" 15 ha 1 JZ4 H4 15 0.13"/> | |
44 <has_text text=" 18 hc 1 JZ4 H7 18 0.05"/> | |
45 </assert_contents> | |
46 </output> | |
47 <output name="gro_output" file="base_GMX.gro" lines_diff="2"/> | |
48 </test> | |
49 </tests> | |
50 <help><![CDATA[ | |
51 Tool to produce GROMACS topologies for small molecules using the acpype interface to AmberTools. | |
52 | |
53 .. class:: infomark | |
54 | |
55 **Input** | |
56 | |
57 Either a mol2 file (more appropriate for small structures) or a | |
58 pdb file. If you want to parameterize a large macromolecule | |
59 (which is more likely to be stored in PDB format, e.g. a protein) | |
60 consider using a tool such as 'GROMACS initial setup' instead. | |
61 | |
62 .. class:: infomark | |
63 | |
64 **Outputs** | |
65 | |
66 GROMACS topology for the ligand, in itp format. Optional: structure file, in gro format. | |
67 | |
68 | |
69 ]]></help> | |
70 <expand macro="citations"> | |
71 <citation type="doi">doi:10.1186/1756-0500-5-367</citation> | |
72 </expand> | |
73 </tool> |