KnowARC logo
University of Luebeck logo

Management of Use Cases

usecaseid Details maintainerid Actions
boxshade -- Alignment pretty printer
	<program name="boxshade" description="Alignment PrettyPrinter yielding PostScript"
		command="boxshade -def -pep -in=alignment.aln -out=postscript.eps -dev=2">
		<icon url="http://www.ch.embnet.org/favicon.ico" />
		<group name="Alignment" />
		<input name="Multiple_Sequence_Alignment_as_MSF">
			<file path="alignment.aln" />
		</input>
		<output name="PostScript_file">
			<fromfile path="postscript.eps" />
			<mime type="text/plain" />
			<mime type="application/postscript" />
		</output>
		<RE name="APPS/BIO/BOXSHADE-3.3.1-4" relation=">=" />
		<test local="test -x /usr/bin/boxshade" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
MSF-formatted alignments of ClustalW or other tools may be converted into pretty-printed post script files. The tool is a bit rough to use non-interactively. Please don t use an earlier version to avoid filling the remote site s disk space.Boxshade Documentation on embnet.ch
t_coffee -- Multiple Sequence Alignment
	<program name="t_coffee" description="call t_coffee"
		command="mkdir .t_coffee ; t_coffee -infile input -outfile output">
		<group name="Alignment" />
		<input name="multiple_sequences_FASTA">
			<file path="input" />
		</input>
		<output name="alignment">
			<fromfile path="output" />
		</output>
		<RE name="APPS/BIO/TCOFFEE-2.5" />
		<test local="/usr/bin/t_coffee" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
A much accepted tool for protein sequence alignment.T-Coffee Server
hmmbuild -- Hidden Markov Model from Alignment
	<program name="hmmbuild"
		description="Preparation of a Hidden Markov Model from a sequence alignment"
		command="hmmbuild hmmfile alignment.msf">
		<group name="Alignment:HMMER" />
		<input name="Multiple_Sequence_Alignment_as_MSF">
			<file path="alignment.msf" />
		</input>
		<output name="HMM">
			<fromfile path="hmmfile" />
		</output>
		<RE name="APPS/BIO/HMMER-2.3.2" />
		<test local="/usr/bin/hmmbuild" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
With a regular sequence alignment as produced by ClustalW or T-Coffee, this program calculates a Hidden Markov Models. It can in turn be used for searches in protein sequence databases, then with hmmsearch. This technology is core of the Pfam database of protein families and domains.HMMER Home Page
hmmcalibrate -- Calibration of HMM
	<program name="hmmcalibrate" description="Calibration of HMM"
		command="hmmcalibrate hmmfile">
		<group name="Alignment:HMMER" />
		<input name="HMM in demand of calibration">
			<file path="hmmfile" />
		</input>
		<output name="Calibrated HMM">
			<fromfile path="hmmfile" />
		</output>
		<RE name="APPS/BIO/HMMER-2.3.2" />
		<test local="test -x /usr/bin/hmmcalibrate" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
Normalisation of an HMM.HMMER Home Page
hmmsearch -- Search with HMM in Sequence database
	<program name="hmmsearch" description="Search with HMM in Sequence database"
		command="hmmcalibrate hmmfile">
		<group name="Alignment:HMMER" />
		<input name="HMM in demand of calibration">
			<file path="hmmfile" />
		</input>
		<output name="Calibrated HMM">
			<fromfile path="hmmfile" />
		</output>
		<RE name="APPS/BIO/HMMER-2.3.2" />
		<test local="test -x /usr/bin/hmmcalibrate" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
The output of hmmbuild can be taken to search for fits to that model in a protein sequence database. That sequence database must be directly accessible on the machine that executes hmmsearch. This is problematic for grid computing since a prior agreement on the database installations must be found.HMMER Home Page
bourne_shell_script -- execute arbitrary shell scripts
	<program name="bourne_shell_script" description="execute shell script"
		command="/bin/sh input">
		<input name="shell script">
			<file path="input" />
		</input>
		<test local="test -x /bin/sh" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
This use case allows for the execution of arbitrary scripts on the remote machine. This comes in handy whenever the resulting data can be transferred directly to the target site. More thoughts need to go into this script in order to increase its flexibility with an arbitrary number of input files as arguments and output files other than stdout.
cmbuild -- Preparation of Infernal-based model for RNA structure
	<program name="cmbuild"
		description="Preparation of model for RNA structure with Infernal"
		command="cmbuild cmfile alignment">
		<group name="Alignment:Infernal" />
		<input name="RNA sequence alignment">
			<file path="alignment" />
		</input>
		<output name="Infernal s representation of RNA structure">
			<fromfile path="cmfile" />
		</output>
		<RE name="APPS/BIO/INFERNAL-0.8.1" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
The concept is the same as for HMMs and protein sequences, respectively their alignment. With RNA however, there is also structural information derivable from the sequence since the strand backfolds to form pairs and thus double-stranded regions. Such co-variances between different regions are represented in stochastic grammars.Infernal Home Page
clustalw_protein -- Alignment of Protein Sequences
<program name="clustalw_protein" description="call clustalw"
      command="clustalw -infile=input -outfile=output">
    <icon url="http://www.ebi.ac.uk/favicon.ico" />
  <group name="Alignment" />
  <input name="multiple_sequences_FASTA">
    <file path="input" />
  </input>
  <output name="alignment">
    <fromfile path="output" />
  </output>
  <RE name="APPS/BIO/CLUSTALW-1.8.3" />
  <test local="test -x /usr/bin/clustalw" />
</program>
SteffenMoeller 2011-05-19 edit
delete
show XML
ClustalW is one of the reference tools for protein sequence alignments. It shares some code and authors with the later developed tool T-Coffee.ClustalW Server @ EBI
weka_tree_learn -- Given some data creates a tree model for it
<program name="weka_tree_learn" description="creates tree model"
      command="java -mx1024m weka.classifiers.trees.J48 -t data.arff -i -k -d J48-data.model">
 <input name="arff">
  <file path="data.arff" />
 </input>
 <output name="model">
  <fromfile path="J48-data.model" />
 </output>
 <RE name="APPS/BIO/WEKA-3.4.10" />
</program>
SteffenMoeller 2011-05-13 edit
delete
show XML
mustang_2 -- Alignment of two protein structures
<program name="mustang_2" description="Protein Structure Alignment"
	command="mustang -i first.pdb second.pdb -F msf -s ON -o output">
	<group name="Alignment" />
	<input name="pdb_structure_one">
		<file path="first.pdb" />
	</input>
	<input name="pdb_structure_two">
		<file path="second.pdb" />
	</input>
	<output name="combined_structures">
		<fromfile path="output.pdb" />
	</output>
	<output name="structure_derived_alignment">
		<fromfile path="output.msf" />
	</output>
	<RE name="APPS/BIO/MUSTANG-3.0" relation=">=" />
	<test local="test -x /usr/bin/mustang" />
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
This use case takes Mustang v3 to align two protein structures. The only condition is that the PDB entry shows only a single chain.mustang home page
MyExperiment #377
list_input_test -- list_input_test
	<program name="list_input_test" description="test" command="cat %%listfile%%">
		<input name="images" list="true" concatenate="true" binary="true">
			<tempfile tag="listfile" />
		</input>
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
Several inputs are merged into a single file and put to stdout.
sift_extract -- Run sift extraction
<program name="sift_extraction" description="Run sift extraction"
      command="java -Djava.awt.headless=true -Xms32m -Xmx512m -jar sift.jar %%imagelist%% %%uniqueID%%">
	<group name="Medical Imaging" />
	<input name="jar" binary="true">
		<file path="sift.jar" />
	</input>
	<input name="images" list="true" binary="true">
		<tempfile tag="imagelist" />
	</input>
	<output name="ftsTable">
		<fromfile path="ftsTable.csv" />
	</output>
	<output name="dscpTable">
		<fromfile path="dscpTable.csv" />
	</output>
	<RE name="ENV/JAVA/JRE-1.5.0" />
</program>
SteffenMoeller 2011-05-10 edit
delete
show XML
run sift extraction on a list of files. needs sift jar
mustang -- structural alignment of arbitrary number of protein structures
<program name="mustang" description="structural alignment of multiple proteins"
	command="mustang -i %%spaceseparatedlistoffiles%% -F msf -s ON -o output">
	<group name="Alignment" />
	<input name="pdb_structures" list="true" concatenate="false"
		binary="false">
		<replace tag="spaceseparatedlistoffiles" />
	</input>
	<output name="combined_structures">
		<fromfile path="output.pdb" />
		<mime type="text/plain" />
		<mime type="chemical/x-pdb" />
	</output>
	<output name="structure_derived_alignment">
		<fromfile path="output.msf" />
		<mime type="text/plain" />
	</output>
	<RE name="APPS/BIO/MUSTANG-3.0" relation=">=" />
	<test local="test -x /usr/bin/mustang" />
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
Taverna has the special feature to allow workflow elements with a variable number of inputs. For Mustang, this is directly applicable since it can align any number of proteins, as long as these contain only a single chain!mustang home page
MyExperiment entry 387
autodock4 -- docking flexibile ligand to mostly-static protein receptor
<program name="autodock4" description="docks ligand to fixed-backbone receptor"
	command="sh executeme.sh">
	<icon url="http://autodock.scripps.edu/favicon.ico" />
	<group name="Structure" />
	<input name="Parameters" binary="false">
		<file path="prot.dpf" />
	</input>
	<input name="Macromolecule" binary="false">
		<file path="prot.pdbqt" />
	</input>
	<input name="Ligand" binary="false">
		<file path="prot.dpf" />
	</input>
	<input name="all_created_files_tared_up_for_docking" binary="true">
		<file path="all_files_tared_up_for_docking.tgz" />
	</input>
	<input name="Grid_Maps" list="true" concatenate="false" binary="false">
		<replace tag="spaceseparatedlistoffiles" />
	</input>
	<output name="Log" binary="false">
		<fromfile path="log.dlg" />
	</output>
	<RE name="APPS/BIO/AUTODOCK-4" relation=">=" />
	<static>
		<file path="executeme.sh" />
<content>
tar xzvf all_files_tared_up_for_docking.tgz
autodock4 -p
prot.dpf -l log.dlg
</content>
	</static>
	<test local="test -x /usr/bin/autodock4" />
</program>
SteffenMoeller 2011-05-11 edit
delete
show XML
Traditionally, the docking is performed for a single protein on a magnitude of ligands, and that in parallel. Workflow technologies may contribute to a larger acceptance of blind docking strategies, that varies the proteins against which to dock. ...still under preparation...Script for automated docking, Retrieval of single ZINC entry, Home page
merge_and_kmeans -- merge_and_kmeans
<program name="merge_and_kmeans" description="merge_and_kmeans"
      command="java -Djava.awt.headless=true -Xms32m -Xmx512m -jar kmeans.jar %%featurefilelist%%">
  <group name="Medical Imaging" />
  <input name="jar" binary="true">
	<file path="kmeans.jar" />
  </input>
  <input name="dscpTable_files" list="true">
	<tempfile tag="featurefilelist" />
  </input>
  <output name="clustersFile">
	<fromfile path="clustersFile" />
  </output>
  <output name="clstIndexFile">
	<fromfile path="clstIndexFile" />
  </output>
  <output name="dscpTable_merged">
	<fromfile path="dscpTable" />
  </output>
  <output name="dscpTable_map">
	<fromfile path="dscpTableMap" />
  </output>
</program>
SteffenMoeller 2011-05-10 edit
delete
show XML
merge_and_kmeansKnowARC
upload_tar_return -- upload_tar_return
<program name="upload_tar_return" description="upload_tar_return"
	command="tar cvf out.tar in">
	<input name="in" binary="true">
		<file path="in" />
	</input>
	<output name="orig" binary="true">
		<fromfile path="in" />
	</output>
	<output name="tar" binary="true">
		<fromfile path="out.tar" />
	</output>
</program>
SteffenMoeller 2011-05-11 edit
delete
show XML
upload_tar_return
autogrid4 -- preparation for a docking experiment
<program name="autogrid4"
      command="sed -i -e 's/^receptor.*/receptor receptor.pdbqt/' ;
               autogrid4 -p prot.gpf -l log.dlg ;
               tar czvf all_files_tared_up_for_docking.tgz *.map *.fld *.xyz"
  description="Precalculations for a docking experiment.">
 <icon url="http://autodock.scripps.edu/favicon.ico" />
 <group name="Structure" />
 <input name="Dock_Parameter_File" binary="false">
   <file path="prot.dpf" />
 </input>
 <input name="Grid_Parameter_File" binary="false">
   <file path="prot.gpf" />
 </input>
 <input name="AD4_paramters_dat" binary="false">
  <file path="AD4_parameters.dat" />
 </input>
 <input name="Macromolecule_pdbqt" binary="false">
  <file path="receptor.pdbqt" />
 </input>
 <output name="Logfile" binary="false">
  <fromfile path="log.glg" />
 </output>
 <output name="Receptor_unchanged" binary="false">
  <fromfile path="receptor.pdbqt" />
 </output>
 <output name="all_created_files_tared_up_for_docking" binary="true">
  <fromfile path="all_files_tared_up_for_docking.tgz" />
 </output>
 <RE name="APPS/BIO/AUTOGRID-4" relation=">=" />
 <test local="test -x /usr/bin/autogrid4" />
</program>
SteffenMoeller 2011-05-13 edit
delete
show XML
The receptor must have been converted from PDB to the PDBQT format prior to the submission to this usecase. The receptor is passed as an argument and is looped through as an output unchanged. Internally it is renamed to receptor.pdbqt and the grid parameter file that is passed as an argument is changed accordingly. The AD4_parameters.dat file also needs to be submitted, which is may be retrieved from here.AutoDock Home Page
charcounter -- charcounter
	<program name="charcounter" description="simple test"
		command="java -jar charcounter.jar inputfile">
		<input name="jar" binary="true">
			<file path="charcounter.jar" />
		</input>
		<input name="countme">
			<file path="inputfile" />
		</input>
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
a simple demo. counts the number of chars in the file
testR -- testR
	<program name="testR" description="cont images" command="java tryRun /etc">
		<input name="classFile" binary="true">
			<file path="tryRun.class" />
		</input>
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
Simple test : conts the image files on a specified directory
HelloWorld -- interprets an internally delivered script
<program name="HelloWorld" description="interprets an internally delivered script"
      command="/bin/sh script.sh">
  <group name="Testing" />
  <static>
<file path="script.sh" />
<content>
echo Hello World!
</content>
  </static>
</program>
SteffenMoeller 2011-05-19 edit
delete
show XML
Test case for contents that directly influences the job execution that is delivered together with the description of the use case and not an input of the workflow. In this example this extra content is a shell script.NorduGrid.org
hostname -- Name of host with domainname
	<program name="hostname"
		description="long hostname of machine executing the workflow element"
		command="hostname -f">
		<group name="Testing" />
	</program>
HajoKrabbenhoeft 2010-10-23 edit
delete
show XML
No input for this workflow element required. STDOUT offers the name of the host that executes the job.KnowARC
add -- forming sum of two integers
<program name="add" description="adding two numbers"
	command="sh addthem.sh number1.txt number2.txt">
	<group name="Testing" />
	<input name="First number">
		<file path="number1.txt" />
	</input>
	<input name="Second number">
		<file path="number2.txt" />
	</input>
	<RE name="APPS/BIO/MUSTANG-3.0" relation=">=" />
	<static>
		<file path="addthem.sh" />
<content>
if [ ! -r "$1" ]; then
        echo "Cannot read file indicated by first argument '$1'." ;
        exit -1 ;
fi ;

if [ ! -r "$2" ];then
   echo "Cannot read file indicated by second argument '$1'." ;
   exit -1 ;
fi ;

if [ ! -x /usr/bin/bc ]; then
   echo "The bc tool is not installed as /usr/bin/bc, if installed at all." ;
   exit -1 ;
fi ;

a=$(cat $1|tr -d '\n') ;
b=$(cat $2|tr -d '\n') ;
echo "$a+$b" | bc | tr -d '\n'
  
</content>
		</static>
	</program>
2011-05-06 edit
delete
show XML
piping two numbers connected with '+' through bc. This script was prepared for educational purposes.KnowARC
ps2pdf -- ps2pdf
	<program name="ps2pdf" description="Convert a Postscript text to binary PDF"
		command="ps2pdf input.ps output.pdf">
		<icon url="http://www.ebi.ac.uk/favicon.ico" />
		<input name="postscript">
			<file path="input.ps" />
			<mime type="text/plain" />
			<mime type="application/postscript" />
		</input>
		<output name="pdf" binary="true">
			<fromfile path="output.pdf" />
			<mime type="application/pdf" />
		</output>
		<RE name="APPS/BIO/CLUSTALW-1.8.3" />
		<test local="test -x /usr/bin/clustalw" />
	</program>
HajoKrabbenhoeft 2010-10-25 edit
delete
show XML
Convert a Postscript text to binary PDF
cat -- UNIX tool cat wrapper for concatenation of two files
<program name="cat"
	description="concatenation of two streams"
	command="cat file1.txt file2.txt">
	<group name="Testing" />
	<input name="First file">
		<file path="file1.txt" />
	</input>
	<input name="Second file">
		<file path="file2.txt" />
	</input>
</program>
SteffenMoeller 2011-05-10 edit
delete
show XML
UNIX command line wrapper.debianmed.blogspot.com
g_luck -- GROMACS fortune cookie
<program name="g_luck"
	description="Quote from Gromacs"
	command="g_luck">
	<group name="GROMACS" />
</program>
SteffenMoeller 2011-05-10 edit
delete
show XML
Testing installation and availability of Gromacs.debianmed.blogspot.com
g_pdb2gmx_gro_top -- Conversion of PDB entry to gromacs format
<program name="pdb2gmx_gro_top"
	description="Conversion of PDB entry to gromacs format"
	command="sh executeme.sh">
   <group name="GROMACS" />
   <input name="PDB entry">
      <file path="protein.pdb" />
   </input>
  <static>
    <file path="executeme.sh" />
<content>
set -e
pdb2gmx -f protein.pdb -o protein.gro -p protein.top -water spc -ff gromos43a2 -ignh ;
touch topology_include_files.itp ;
tar czf topology_include_files.tar.gz *.itp
</content>
  </static>
  <output name="GROMACS gro protein">
      <fromfile path="protein.gro" />
  </output>
  <output name="GROMACS top topology">
      <fromfile path="protein.top" />
  </output>
  <output name="GROMACS itp topology_include_files tgz">
      <fromfile path="topology_include_files.tar.gz" />
  </output>
</program>
SteffenMoeller 2011-05-19 edit
delete
show XML
Common start of many workflows using GROMACS, the input needs to be converted. The script by default requests the interactive adjustment of parameters by users. Those are now fixed (as in "overwrite with your settings" or "send us comments about it") to "-water spc -ff gromos43a2".debianmed.blogspot.com
g_editconf_gro2pdb -- Using GROMACS tool editconf to convert GROMACS .gro file to PDB format
<program name="gro2pdb"
	description="Using GROMACS tool editconf to convert GROMACS .gro file to PDB format"
	command="tar xzf topology_include_files.tgz ; editconf -f protein.gro -o protein.pdb">
   <group name="GROMACS" />
  <input name="GROMACS gro protein">
      <file path="protein.gro" />
  </input>
  <input name="GROMACS top topology">
      <file path="protein.top" />
  </input>
  <input name="GROMACS itp topology include files tgz" binary="true">
      <file path="topology_include_files.tgz" />
  </input>
   <output name="PDB entry">
      <fromfile path="protein.pdb" />
      <mime type="chemical/x-pdb" />
      <mime type="text/plain" />
   </output>
</program>
SteffenMoeller 2011-05-25 edit
delete
show XML
Especially for inspection of the results in regular PDB viewers, this use of the GROMACS editconf comes very handy. The this use of editconf is presented as 'gro2pdb', in analogy to pdb2gmx.debianmed.blogspot.com
g_grompp -- Preparation of molecular dynamics run
<program name="grompp"
  description="Using GROMACS tool to prepare md run"
      command="tar xzf topology_include_files.tgz ; grompp -v -f minim.mdp -c protein.gro -p protein.top -o protein.tpr">
   <group name="GROMACS" />
   <output name="GROMACS tpr file">
      <fromfile path="protein.tpr" />
   </output>
   <output name="GROMACS mdp file">
      <fromfile path="mdout.mdp" />
   </output>
   <input name="GROMACS gro protein">
      <file path="protein.gro" />
   </input>
   <input name="GROMACS top topology">
      <file path="protein.top" />
   </input>
   <input name="GROMACS itp topology include files tgz" binary="true">
      <file path="topology_include_files.tgz" />
   </input>
   <input name="GROMACS mdp file">
      <file path="minim.mdp" />
   </input>
</program>
SteffenMoeller 2011-05-25 edit
delete
show XML
One first starts grompp and then mdrun.debianmed.blogspot.com
g_mdrun -- Execution of molecular dynamics
<program name="mdrun"
         description="Using GROMACS tool to run molecular dynamics"
         command="tar xzf topology_include_files.tgz ; mdrun -v -deffnm protein -c protein_last_step.gro">
   <group name="GROMACS" />
   <input name="GROMACS tpr file">
      <file path="protein.tpr" />
   </input>
  <input name="GROMACS gro protein">
      <file path="protein.gro" />
  </input>
  <output name="GROMACS gro protein with last step">
      <fromfile path="protein_last_step.gro" />
  </output>
   <input name="GROMACS top topology">
      <file path="protein.top" />
   </input>
  <input name="GROMACS itp topology include files tgz" binary="true">
      <file path="topology_include_files.tgz" />
  </input>
   <input name="GROMACS mdp file">
      <file path="minim.mdp" />
   </input>
  <output name="GROMACS trr trajectory file">
      <fromfile path="protein.trr" />
  </output>
  <output name="GROMACS log log file">
      <fromfile path="protein.log" />
   </output>
  <output name="GROMACS edr file">
      <fromfile path="protein.edr" />
  </output>
</program>
SteffenMoeller 2011-05-25 edit
delete
show XML
This job may take real long.debianmed.blogspot.com
gzip -- Compressing single file to STDOUT
<program name="gzip"
  description="Compressing single file to STDOUT"
      command="gzip -c fred > fred.gz">
<group name="system" />
<input name="file to compress" binary="true">
 <file path="fred" />
</input>
<output name="gzipped file" binary="true">
 <fromfile path="fred.gz" />
</output>
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
Wrapping gzip command. STDOUT will always be empty.debianmed.blogspot.com, myExperiment #2125
gunzip -- Uncompressing file to STDOUT
<program name="gunzip"
  description="Uncompressing single file to STDOUT"
      command="gunzip -c fred.gz > fred">
<group name="system" />
<input name="gzipped file" binary="true">
 <file path="fred.gz" />
</input>
<output name="decompressed file" binary="true">
 <fromfile path="fred" />
</output>
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
Uncompressing gzipped file to STDOUT.debianmed.blogspot.com, myExperiment #2125
diff -- UNIX tool diff wrapper for differences between two text files
<program name="diff"
  description="UNIX tool diff wrapper for differences between two text files"
     command="diff -u from.txt to.txt">
 <input name="original_file">
  <file path="from.txt" />
 </input>
 <input name="modified_file">
  <file path="to.txt" />
 </input>
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
The tool 'diff' is commonly used to prepare patches of results of various sorts against an original version of some file. It is called with the '-u' option that is commonly perceived as a standard to increase legibility. Differences are sent to STDOUT, STDERR should be empty. For the time speaking, this entry runs into the trap of diff not exiting with a status 0 when there are differences but with the exit 1. This is why if diff -q a b; then echo "Files a and b differ." fi works but for the moment this deadly irritates the wrapper. debianmed.blogspot.com
diff_works -- diff redirecting to separate output file
<program name="diff_works"
  description="UNIX tool diff wrapper for differences between two text files"
     command="diff -u from.txt to.txt | tee difference.txt">
 <group name="system" />
 <input name="original_file">
  <file path="from.txt" />
 </input>
 <input name="modified_file">
  <file path="to.txt" />
 </input>
 <output name="difference_file">
  <fromfile path="difference.txt" />
 </output>
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
It seems like STDOUT is not working without a separate output file ...
openjpeg14_tif2j2k_simple -- Encoding a RGB/Grayscale TIFF image to JPEG2000 (JP2)
<program name="openjpeg_tif2j2k_simple"
  description="Encoding a RGB/Grayscale TIFF image to JPEG2000 (JP2)"
      command="image_to_j2k -i input.tif -o output.jp2 -SOP -EPH">
         <input name="inputfile" binary="true">
                <file path="input.tif" />
                <mime type="image/tif" />
         </input>
         <output name="outputimage" binary="true">
                <fromfile path="output.jp2" />
                <mime type="image/jp2" />
         </output>
</program>
SteffenMoeller 2011-05-18 edit
delete
show XML
The command image_to_j2k is executed with not specification of any particular path. If running Debian or Ubuntu, the tool comes in the package openjpeg-tools. The wrapper was contributed by Sven Schlarb.
openjpeg_tif2j2k -- Encoding a RGB/Grayscale TIFF image to JPEG2000 (JP2)
<program name="openjpeg_tif2j2k"
 description="Encoding a RGB/Grayscale TIFF image to JPEG2000 (JP2)">
<command>
image_to_j2k -r %%compression%% -n %%resolutions%% -b %%codeblocksize%% -t %%tilesize%% -p %%progressionorder%% -s %%subsamplingfactor%% -i input.tif -o output.jp2 -SOP -EPH
</command>
   <input name="compression">
      <replace tag="compression"/>
   </input>
   <input name="resolutions">
      <replace tag="resolutions"/>
   </input>
   <input name="codeblocksize">
      <replace tag="codeblocksize"/>
   </input>
   <input name="tilesize">
      <replace tag="tilesize"/>
   </input>
   <input name="progressionorder">
     <replace tag="progressionorder"/>
   </input>
   <input name="subsamplingfactor">
     <replace tag="subsamplingfactor"/>
   </input>
   <input name="inputfile" binary="true">
         <file path="input.tif" />
      <mime type="image/tif" />
   </input>
   <output name="outputimage" binary="true">
        <fromfile path="output.jp2" />
      <mime type="image/jp2" />
   </output>
</program>
SteffenMoeller 2011-05-24 edit
delete
show XML
The conversion from tiff to jpeg2000 is performed with the tool image_to_j2k from the openjpeg tools. Contribution by Sven Schlarb
editconf_box -- Creation of bounding box around GROMACS protein
<program name="editconf_box"
  description="Generation of dodecahedric bounding box."
      timeout="1800" preparing_timeout="1200">
  <command>editconf -f protein_in.gro -o protein_out.gro -bt dodecahedron -d 1.2</command>
  <group name="GROMACS" />
  <input name="protein_in">
    <file path="protein_in.gro" />
  </input>
  <output name="protein_out">
    <fromfile path="protein_out.gro" />
  </output>
</program>
SteffenMoeller 2011-05-23 edit
delete
show XML
Generation of dodecahedric bounding box.http://debianmed.blogspot.com
genbox_soluble -- Fill box with water
<program name="genbox_soluble"
  description="Fills box with water">
  <command>tar xzf topology_include.tgz ; 
genbox -cp protein_in.gro -cs spc216.gro -p protein.top -o protein_out.gro ; 
touch topology_include_files.itp ;
tar czf topology_include_files.tar.gz *.itp
</command>
  <group name="GROMACS" />
  <input name="GROMACS_protein_in_gro">
    <file path="protein_in.gro" />
  </input>
  <input name="GROMACS_topology_top">
    <file path="protein.top" />
  </input>
  <input name="GROMACS_topology_include_files_itp_tgz" binary="true">
    <file path="topology_include.tgz" />
  </input>
  <output name="GROMACS_topology_top">
    <fromfile path="protein.top" />
  </output>
  <output name="GROMACS_topology_include_files_itp_tgz" binary="true">
    <fromfile path="topology_include.tgz" />
  </output>
  <output name="GROMACS_protein_out_gro">
    <fromfile path="protein_out.gro" />
  </output>
</program>
SteffenMoeller 2011-05-25 edit
delete
show XML
The protein is already in a box, which is now filled with the solute. This is water for the moment.debianmed.blogspot.com
genion_salt -- Adding Na+ and Cl- ions
<program name="genion_salt"
  description="Adding Na+ and Cl- ions to achieve neutrality">
<command>tar xzf topology_include.tgz ; 
echo SOL | genion -s protein-water.tpr -o protein-solvated.gro -conc 0.15 -neutral -p protein.top -pname NA -nname CL ;
touch topology_include_files.itp ;
tar czf topology_include_files.tar.gz *.itp
</command>
  <group name="GROMACS" />
  <input name="GROMACS_topology_top">
    <file path="protein.top" />
  </input>
  <input name="GROMACS_topology_include_files_itp_tgz" binary="true">
    <file path="topology_include.tgz" />
  </input>
  <input name="GROMACS_protein_in_tpr">
    <file path="protein-water.tpr" />
  </input>
  <output name="GROMACS_protein_out_gro">
    <fromfile path="protein-solvated.gro" />
  </output>
  <output name="GROMACS_topology_top">
    <fromfile path="protein.top" />
  </output>
  <output name="GROMACS_topology_include_files_itp_tgz" binary="true">
    <fromfile path="topology_include.tgz" />
  </output>
</program>
SteffenMoeller 2011-05-25 edit
delete
show XML
The system shall be neutral in its charge. No sure if the .top is needed as an input.debianmed.blogspot.com

Create a new entry.

Show all entries as XML, List.

Login

Home · Use Case · Runtime Environment · Maintainer

KnowARC · NorduGrid · NDGF BioGrid

Help