IDConflictResolverAlgorithm

class pyopenms.IDConflictResolverAlgorithm

Bases: object

Cython implementation of _IDConflictResolverAlgorithm

Documentation is available at http://www.openms.de/current_doxygen/html/classOpenMS_1_1IDConflictResolverAlgorithm.html

__init__()

  • Cython signature: void IDConflictResolverAlgorithm() Resolves ambiguous annotations of features with peptide identifications

  • Cython signature: void IDConflictResolverAlgorithm(IDConflictResolverAlgorithm &)

Methods

__init__

  • Cython signature: void IDConflictResolverAlgorithm()

resolve

  • Cython signature: void resolve(FeatureMap & features)

resolveBetweenFeatures

  • Cython signature: void resolveBetweenFeatures(FeatureMap & features)
resolve()

  • Cython signature: void resolve(FeatureMap & features)

The the filtered identifications are added to the vector of unassigned peptides and also reduced to a single best hit —– :param keep_matching: Keeps all IDs that match the modified sequence of the best hit in the feature (e.g. keeps all IDs in a ConsensusMap if id’d same across multiple runs)

  • Cython signature: void resolve(ConsensusMap & features)

The the filtered identifications are added to the vector of unassigned peptides and also reduced to a single best hit —– :param keep_matching: Keeps all IDs that match the modified sequence of the best hit in the feature (e.g. keeps all IDs in a ConsensusMap if id’d same across multiple runs)

resolveBetweenFeatures()

  • Cython signature: void resolveBetweenFeatures(FeatureMap & features)

This filter removes the peptide sequence annotations from features, if a higher-intensity feature with the same (charge, sequence) combination exists in the map. The total number of features remains unchanged. In the final output, each (charge, sequence) combination appears only once, i.e. no multiplicities

  • Cython signature: void resolveBetweenFeatures(ConsensusMap & features)

This filter removes the peptide sequence annotations from features, if a higher-intensity feature with the same (charge, sequence) combination exists in the map. The total number of features remains unchanged. In the final output, each (charge, sequence) combination appears only once, i.e. no multiplicities