Tide does not exclude from the observed spectrum peaks close to the m/z of the precursor, whereas Crux does:
// skip all peaks within precursor ion mz +/- 15
if(peak_location < precursor_mz + 15 && peak_location > precursor_mz - 15){
continue;
}
We should find out what Comet does, and then make sure that Tide does what Comet does.
Bill
According to Sean, comet controls this behavior with the remove_precursor_peak and remove_precursor_tolerance parameters, The default is do not remove.
I think we should add this option to Tide, and have its behavior mimic that of Comet.
Added in r16263, but add the case for charge reduced peaks post v2.0