What kind of thresholding do you do? Enabling that in msconvert is overdue - the backend code to support it is already in place.
MzXML2Search is failing because it depends on a strict DTA name scheme with 5 digits. This is going to break with long LTQ Velos runs so it needs to be fixed regardless of the Agilent scanId issue. It's ironic that a Thermo file is the one to break the Thermo-centric assumptions. :P -Matt dctrud wrote: > MzXML2Search conversion to mgf fails for me on mzXML / mzML created > using msconvert from Agilent 6520 QTOF data. > > Trapper numbers spectra using an index starting at 1, whilst msconvert > uses the Agilent scan ID (can be a very large number). MzXML2Search > conversion of the resulting file into mgf then fails once it reaches a > scan ID > 99,999. > > Have seen similar problems with other programs and contacted Matt > Chambers who said that the numbering would stay the same, and that > it's better if programs which can't cope with the large numbers are > fixed. Is this possible (desirable?) for MzXML2Search and any other > TPP tools that might be affected? > > I can't use Trapper as I need to extract Profile MS + Centroid MS/MS > from a dual mode file (msconvert supported). I can't directly convert > to mgf with msconvert as I need to do peak thresholding to get file > sizes down to a reasonable level. > > Cheers, > > DT --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
