From: Martin E. <mar...@ru...> - 2008-08-07 13:51:07
|
> > This seems to work pretty well (as expected!!) > > The interesting thing is that there are two sets of residue masses, two > > SpectrumIdentificationList (one for light, one for heavy) but just one > > ProteinDetectionList. At first glance I thought it would be better to have one residue mass list and a modification for N15 (see below). But I saw it was a bad solution. It indeed works like you modeled it, because we don't report any masses for DBSequences or Proteins. > > And (possibly confusing at first glance!) unmodified peptides with > > different masses like this: > > > > <Peptide id="peptide_48_1" sequenceMass="1025.481796" > > > <peptideSequence>STNLDWYK</peptideSequence> > > </Peptide> > > > > <Peptide id="peptide_53_1" sequenceMass="1036.449188"> > > <peptideSequence>STNLDWYK</peptideSequence> > > </Peptide> > > I think this is where I come in with the mod specifications for > peptide results. I'll try and add this as an example to issue 35 It could be possible in the current schema with the CustomModification element. But that should be "extended" to report "elements" (N, C, O) instead of "locations". Or PSI-MOD has to include "N15 mod of amino acid X" with the respective mass or delta mass, which maybe there already. But that would be quite verbose. Bye Martin |