![]() |
OpenMS
2.4.0
|
Fix output in parallel mode, change assignment of charges to threads, add parallel TOPP test (Marc)
Implement user-specified seed lists support (Marc)
Implement reading of pepXML and protXML (Andreas)
Allow reading of zipped XML files (David, Hiwi)
Implement support for labeled MRM experiments, Q1 m/z value and charges. (Andreas)
Implement support for more than one mass delta, e.g. from missed cleavages and so on (Andreas)
ProteinInference -- Protein inference based on an aggregation of the scores of the identified peptides. Version: 2.4.0-HEAD-2019-01-18 Jan 18 2019, 21:06:42, Revision: 8ddd6a9 To cite OpenMS: Rost HL, Sachsenberg T, Aiche S, Bielow C et al.. OpenMS: a flexible open-source software platform for mass spectrometry data analysis. Nat Meth. 2016; 13, 9: 741-748. doi:10.1038/nmeth.3959. Usage: ProteinInference <options> Options (mandatory options marked with '*'): -in <file>* Input file(s) (valid formats: 'idXML') -out <file>* Output file (valid formats: 'idXML') -merge_runs <choice> If your idXML contains multiple runs, merge them beforehand? (default: 'no' valid: 'no', 'all') -annotate_indist_groups <choice> If you want to annotate indistinguishable protein groups, either for reporting or for group based quant. later. Only works with a single ID run in the file. (default: 'true' valid: 'true', 'false' ) Merging: -Merging:annotate_origin <choice> If true, adds a map_index MetaValue to the Peptid eIDs to annotate the IDRun they came from. (defau lt: 'true' valid: 'true', 'false') Algorithm: -Algorithm:score_aggregation_method <choice> How to aggregate scores of peptides matching to the same protein? (default: 'maximum' valid: 'max imum', 'product', 'sum') -Algorithm:treat_charge_variants_separately <text> If this is true, different charge variants of the same peptide sequence count as individual evidences. (default: 'true') -Algorithm:treat_modification_variants_separately <text> If this is true, different modification variants of the same peptide sequence count as individual evidences. (default: 'true') -Algorithm:use_shared_peptides <text> If this is true, shared peptides are used as evid ences. (default: 'true') -Algorithm:skip_count_annotation <text> If this is true, peptide counts won't be annotate d at the proteins. (default: 'false') Common TOPP options: -ini <file> Use the given TOPP INI file -threads <n> Sets the number of threads allowed to be used by the TOPP tool (default: '1') -write_ini <file> Writes the default configuration file --help Shows options --helphelp Shows all options (including advanced)INI file documentation of this tool:
Document which metavalues of Protein/PeptideHit are filled when reading ProtXML (Chris)
Writing of protXML is currently not supported
Handle Modifications (Andreas)
Complete rewrite of the parser (and those of InsPecT and PepNovo), the code is bullshit... (Andreas)