[Psidev-ms-dev] additional feature request: precursor m/z method logging?

[Eric D. <eri...@gm...>]

From: Joshua Tasman 

Hi all,

Can we figure out a way to add a note regarding the determination of the
precursor m/z ("parent" m/z)?  There are a few ways to do it for Thermo
software with the Xcalibur API, at least, and I can imagine that someone
might write their own processing routines to include in the converters.

So: 1) can we clarify that the software/processing section can handle
multiple entries for the same software (for example, "thermo API filter
line", "thermo API trailer label value", etc.
and 2) some way to reference this near the info at the scan level?

Thanks,

Josh