-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
isotope labelled cross-linkers (in mzIdentML)? #12
Comments
Logically I would assume they have for four SII, in two different SIR. But I find that a bit problematic, as you could also interpret this as a higher order cross-link of some kind. E.g. if I would write a cross-link between four distinct peptides I would write one SIL with four SII that have the same MS:1002511 'value'. This way to represent the xquest results sounds like a good way to give everybody a hard time in the future. I would rather have the heavy and light labeled identifications as two distinct sets of IDs that have potentially another cvparam linking them as a pair. |
from the spec:
Its not super clear but I think it means within a single SIR. As far as I can tell, the following is what's been happening with the validator (HUPO-PSI/mzIdentML#105 , HUPO-PSI/mzIdentML#100)... First it was passing files if there were exactly 2 or 4 occurrences of MS:1002511 with same value in the SIL. Now I think it passes if there are an even number of occurrences of MS:1002511 with same value in SIL. I can't test this properly because I can't build the validator. If you can contribute anything to the HUPO/mzIdentML project to help with this then please do - I made a bit of a mess of it over there. |
yup, from example file https://github.com/HUPO-PSI/mzIdentML/blob/master/examples/1_2examples/crosslinking/OpenxQuest_example.mzid it looks like 4 within SIR (e.g. search '6054414965487887') |
fix pdbdev routes, merge work from suresh
After getting some things wrong on the mzIdentML github project, I now know about isotope labelled cross-linkers.
These have four SII with the same MS:1002511 'value' within the same SIR.
We don't support this aspect of mzIdentMl at the moment.
The text was updated successfully, but these errors were encountered: