<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE knimeNode PUBLIC "-//UNIKN//DTD KNIME Node 2.0//EN" "http://www.knime.org/Node.dtd">
<knimeNode icon="generic_node.png" type="Manipulator">
    <name>OMSSAAdapter</name>
    
    <shortDescription>
        Annotates MS/MS spectra using OMSSA.
    </shortDescription>
    
    <fullDescription>
        <intro><p>Annotates MS/MS spectra using OMSSA.</p>
		<p>
			<a href="http://ftp.mi.fu-berlin.de/OpenMS/release-documentation/html/TOPP_OMSSAAdapter.html">Web Documentation for OMSSAAdapter</a>
		</p>

        </intro>
        
		<option name="version">Version of the tool that generated this parameters file.</option>
		<option name="precursor_mass_tolerance">Precursor mass tolerance (Default: Dalton)</option>
		<option name="precursor_mass_tolerance_unit_ppm">If this flag is set, ppm is used as precursor mass tolerance unit</option>
		<option name="fragment_mass_tolerance">Fragment mass error in Dalton</option>
		<option name="min_precursor_charge">Minimum precursor ion charge</option>
		<option name="max_precursor_charge">Maximum precursor ion charge</option>
		<option name="fixed_modifications">Fixed modifications, specified using UniMod (www.unimod.org) terms, e.g. 'Carbamidomethyl (C)' or 'Oxidation (M)'</option>
		<option name="variable_modifications">Variable modifications, specified using UniMod (www.unimod.org) terms, e.g. 'Carbamidomethyl (C)' or 'Oxidation (M)'</option>
		<option name="pc">The number of pseudocounts to add to each precursor mass bin</option>
		<option name="hs">the minimum number of m/z values a spectrum must have to be searched</option>
		<option name="tez">scaling of precursor mass tolerance with charge (0 = none, 1= linear)</option>
		<option name="tom">product ion search type, with 0 = monoisotopic, 1 = average, 2 = monoisotopic N15, 3 = exact</option>
		<option name="tem">precursor ion search type, with 0 = monoisotopic, 1 = average, 2 = monoisotopic N15, 3 = exact</option>
		<option name="tex">threshold in Da above which the mass of a neutron should be added in an exact mass search</option>
		<option name="zt">minimum precursor charge to start considering multiply charged products</option>
		<option name="z1">the fraction of peaks below the precursor used to determine if the spectrum is charge +1</option>
		<option name="zc">should charge +1 be determined algorithmically (1=yes)</option>
		<option name="zcc">how should precursor charges be determined? (1=believe the input file,2=use the specified range)</option>
		<option name="zoh">set the maximum product charge to search</option>
		<option name="v">number of missed cleavages allowed</option>
		<option name="enzyme">The enzyme used for peptide digestion.</option>
		<option name="no">minimum size of peptides for no-enzyme and semi-tryptic searches</option>
		<option name="nox">maximum size of peptides for no-enzyme and semi-tryptic searches</option>
		<option name="i">comma delimited list of id numbers of ions to search</option>
		<option name="sp">number of product ions to search</option>
		<option name="sb1">should first forward (e.g. b1) product ions be searched (1 = no, 0 = yes)</option>
		<option name="sct">should c terminus ions (e.g. y1) be searched (1 = no, 0 = yes)</option>
		<option name="x">comma delimited list of NCBI taxonomy ids to search (0 = all.  This is the default)</option>
		<option name="hm">the minimum number of m/z matches a sequence library peptide must have for the hit to the peptide to be recorded</option>
		<option name="ht">number of m/z values corresponding to the most intense peaks that must include one match to the theoretical peptide</option>
		<option name="hl">maximum number of hits retained for one spectrum. Note: even when set to 1 OMSSA may report multiple hits with different charge states</option>
		<option name="he">the maximum e-value allowed in the hit list. If you set this parameter too small (e.g., he=1), this will effectively introduce FDR filtering. Thus, allowing a less stringent FDR during post-processing will nevertheless return the (better) FDR introduced here, since mediocre hits are not even reported.</option>
		<option name="mm">the maximum number of mass ladders to generate per database peptide</option>
		<option name="mnm">n-term methionine should not be cleaved</option>
		<option name="is">evalue threshold to include a sequence in the iterative search, 0 = all</option>
		<option name="ir">evalue threshold to replace a hit, 0 = only if better</option>
		<option name="ii">evalue threshold to iteratively search a spectrum again, 0 = always</option>
		<option name="chunk_size">Number of spectra to submit in one chunk to OMSSA. Chunks with more than 30k spectra will likely cause memory allocation issues with 32bit OMSSA versions (which is usually the case on Windows). To disable chunking (i.e. submit all spectra in one big chunk), set it to '0'.</option>
		<option name="log">Name of log file (created only when specified)</option>
		<option name="debug">Sets the debug level</option>
		<option name="threads">Sets the number of threads allowed to be used by the TOPP tool</option>
		<option name="no_progress">Disables progress logging to command line</option>
		<option name="force">Overwrite tool specific checks.</option>
		<option name="test">Enables the test mode (needed for internal use only)</option>

    </fullDescription>
    
    <ports>
		<inPort index="0" name="in [mzML]">Input file  [mzML]</inPort>
		<inPort index="1" name="database [psq,fasta]">NCBI formatted FASTA files. The .psq filename should be given, e.g. 'SwissProt.fasta.psq'. If the filename does not end in '.psq' (e.g., SwissProt.fasta) the psq suffix will be added automatically. Non-existing relative file-names are looked up via'OpenMS.ini:id_db_dir' [psq,fasta]</inPort>
		<outPort index="0" name="out [idXML]">Output file  [idXML]</outPort>
 </ports>
    <views>
        <view index="0" name="OMSSAAdapter Std Output">The text sent to standard out during the execution of OMSSAAdapter.</view>
        <view index="1" name="OMSSAAdapter Error Output">The text sent to standard error during the execution of OMSSAAdapter. (If it appears in gray, it's the output of a previously failing run which is preserved for your trouble shooting.)</view>
    </views>    
</knimeNode>
