Hi, Msconvert allows the user to specify the required precision of output peak data - either 32-bit or 64-bit. Trapper does not seem to have an equivalent switch (at least there is no mention of it in the usage documentation).
(1) Is there a way to force Trapper to generate 64-bit precision output? (2) I'm wondering if I would "lose" data by using Trapper for Agilent MassHunter ".d" data. I'm not comfortable enough with C++ to answer this for myself - when Trapper/Msconvert call the Agilent interface, do they receive back 32- bit or 64-bit data? I'd like to know if the 64-bit precision of Msconvert is actually giving me real data, or just padding out 32-bit numbers to help collapse my hard drive? (3) This is probably a question I should be able to answer myself, and might be much too broad for here, but might there be any practical benefit for having 64-bit data rather than 32-bit? I suspect that the different might be negligible in the sense that the difference between a 32-bit and 64-bit m/z would have no impact on things like peptide identification or feature detection for quantification? Thanks again, bio.x2y -- You received this message because you are subscribed to the Google Groups "spctools-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spctools-discuss?hl=en.
