Hi Hannes, I had a quick peek at your file and while I didn’t do any testing a few things come to mind.
1) It could be that because you’re using mzXML (you meant to use mzML, didn’t you? ;-) SpectraST might not be not detecting that these are HCD spectra when building the library? The peptides are labeled (CID) when I they should be labeled (HCD) I assume? When creating the library, maybe -cIHCD would help? Just guessing
2) Unless I mis-count, there are only 2 spectra in the sptxt?
3) The mzML has some unusual carriage returns in the third spectrum. It could be causing some problem possibly..
I would investigate those first, but maybe it’s something else..
Eric
--
You received this message because you are subscribed to the Google Groups "spctools-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spctools-discu...@googlegroups.com.
To post to this group, send email to spctools...@googlegroups.com.
Visit this group at https://groups.google.com/group/spctools-discuss.
For more options, visit https://groups.google.com/d/optout.
I ran SpectraST on your file with –V and it seems to show that it is not reading the precursor mz from you file somehow. All the precursormzs in the verbose output are 0. I peeked in the file and I do see precursor mzs in there, but I don’t know if they are encoded correctly.
Where did this mzXML file come from?
> email to spctools-discuss+unsubscribe@googlegroups.com.
> To post to this group, send email to spctools-discuss@googlegroups.com.
> Visit this group at https://groups.google.com/group/spctools-discuss.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "spctools-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/spctools-discuss/MMwABWl4Iqs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> spctools-discuss+unsubscribe@googlegroups.com.
> To post to this group, send email to spctools-discuss@googlegroups.com.
Dear Hannes, sorry for this problem you had, and thanks so much for tracking this down exactly and sending us the offending code and solution. After investigating this a bit more we’ve determined that the problem was introduced in a check-in to trunk on Oct 2. Yesterday we checked in some new code that fixes this problem and adds some additional functionality as well from other development. We did not use your patch exactly as is, but thank you for sending it.
Please try updating to the latest trunk and using that code, and let us know if you have further trouble with it.
A note to everyone else: if you compiled TPP yourself from trunk during the month of October, please recompile with the latest trunk to fix this problem. Official TPP releases are not affected by this problem as far as we know. We plan to release TPP 5.1 next week and this will be fixed.
Thanks,
Eric
From: spctools...@googlegroups.com [mailto:spctools...@googlegroups.com] On Behalf Of Hannes Roest
Sent: Tuesday, October 24, 2017 7:38 AM
To: spctools-discuss <spctools...@googlegroups.com>
Subject: Re: [spctools-discuss] spectrast produces empty output file
Dear Eric
I have now tracked down the problem to a bit of logic in TPP in mzParser/RAMPface.cpp
> You received this message because you are subscribed to a topic in the
> Google Groups "spctools-discuss" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/spctools-discuss/MMwABWl4Iqs/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> spctools-discu...@googlegroups.com.
> To post to this group, send email to spctools...@googlegroups.com.
> Visit this group at https://groups.google.com/group/spctools-discuss.
> For more options, visit https://groups.google.com/d/optout.