You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(5) |
Aug
(4) |
Sep
(4) |
Oct
(10) |
Nov
(1) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
(2) |
Mar
(2) |
Apr
(8) |
May
(40) |
Jun
(30) |
Jul
(61) |
Aug
(21) |
Sep
(12) |
Oct
(56) |
Nov
(99) |
Dec
(83) |
2009 |
Jan
(3) |
Feb
(9) |
Mar
(1) |
Apr
(5) |
May
(88) |
Jun
(43) |
Jul
(60) |
Aug
(54) |
Sep
(4) |
Oct
(18) |
Nov
(9) |
Dec
(5) |
2010 |
Jan
|
Feb
(3) |
Mar
(1) |
Apr
(8) |
May
(10) |
Jun
(8) |
Jul
(10) |
Aug
(18) |
Sep
(11) |
Oct
(19) |
Nov
(14) |
Dec
(26) |
2011 |
Jan
(27) |
Feb
(38) |
Mar
(50) |
Apr
(128) |
May
(54) |
Jun
(116) |
Jul
(79) |
Aug
(163) |
Sep
(21) |
Oct
(14) |
Nov
(19) |
Dec
(9) |
2012 |
Jan
(7) |
Feb
(34) |
Mar
(34) |
Apr
(50) |
May
(70) |
Jun
(23) |
Jul
(8) |
Aug
(24) |
Sep
(35) |
Oct
(40) |
Nov
(276) |
Dec
(34) |
2013 |
Jan
(25) |
Feb
(23) |
Mar
(12) |
Apr
(59) |
May
(31) |
Jun
(11) |
Jul
(21) |
Aug
(7) |
Sep
(18) |
Oct
(11) |
Nov
(12) |
Dec
(18) |
2014 |
Jan
(37) |
Feb
(22) |
Mar
(9) |
Apr
(10) |
May
(38) |
Jun
(20) |
Jul
(15) |
Aug
(4) |
Sep
(4) |
Oct
(3) |
Nov
(8) |
Dec
(5) |
2015 |
Jan
(13) |
Feb
(34) |
Mar
(27) |
Apr
(5) |
May
(12) |
Jun
(10) |
Jul
(12) |
Aug
(3) |
Sep
(1) |
Oct
(13) |
Nov
|
Dec
(6) |
2016 |
Jan
(1) |
Feb
(1) |
Mar
(17) |
Apr
(139) |
May
(120) |
Jun
(90) |
Jul
(10) |
Aug
|
Sep
|
Oct
(11) |
Nov
(6) |
Dec
(2) |
2017 |
Jan
(24) |
Feb
(8) |
Mar
(7) |
Apr
(2) |
May
(5) |
Jun
(11) |
Jul
(5) |
Aug
(9) |
Sep
(6) |
Oct
(4) |
Nov
(2) |
Dec
(4) |
2018 |
Jan
(7) |
Feb
|
Mar
(4) |
Apr
(6) |
May
(10) |
Jun
(6) |
Jul
(7) |
Aug
|
Sep
(7) |
Oct
(5) |
Nov
(3) |
Dec
(3) |
2019 |
Jan
(3) |
Feb
|
Mar
(4) |
Apr
(3) |
May
(2) |
Jun
(6) |
Jul
(3) |
Aug
(2) |
Sep
|
Oct
(2) |
Nov
(12) |
Dec
(1) |
2020 |
Jan
(3) |
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(1) |
Nov
|
Dec
|
2021 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: mayerg97 <ger...@ru...> - 2016-06-06 09:37:56
|
Dear proteomics community, attached there's the new version 3.89.0 of the psi-ms.obo file. It contains a generic neutral loss term and terms for reporter ions. New CV terms in version 3.89.0 of psi-ms.obo: ============================================= ************ Added a string value slot holding the molecular formula in Hill notation [Term] id: MS:1000336 name: neutral loss def: "The loss of an uncharged species during a rearrangement process. The value slot holds the molecular formula in Hill notation of the neutral loss molecule, see PMID: 21182243. This term must be used in conjunction with a child of the term MS:1002307 (fragmentation ion type)." [PSI:MS] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1001055 ! modification parameters ************ New terms for reporter ions ************ The mass can be specified in the value slot. [Term] id: MS:1002668 name: frag: iTRAQ 4plex reporter ion def: "Standard reporter ion for iTRAQ 4Plex. The value slot holds the integer mass of the iTRAQ 4Plex reporter ion, e.g. 114." [PSI:PI] xref: value-type:xsd\:int "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002669 name: frag: iTRAQ 8plex reporter ion def: "Standard reporter ion for iTRAQ 8Plex. The value slot holds the integer mass of the iTRAQ 8Plex reporter ion, e.g. 113." [PSI:PI] xref: value-type:xsd\:int "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002670 name: frag: TMT reporter ion def: "Standard reporter ion for TMT. The value slot holds the integer mass of the TMT reporter ion and can be suffixed with either N or C, indicating whether the mass difference is encoded at a Nitrogen or Carbon atom, e.g. 127N." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002671 name: frag: TMT ETD reporter ion def: "Standard reporter ion for TMT with ETD fragmentation. The value slot holds the integer mass of the TMT ETD reporter ion and can be suffixed with either N or C, indicating whether the mass difference is encoded at a Nitrogen or Carbon atom, e.g. 127C." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002672 name: no modification threshold def: "No statistical threshold for accepting or rejecting that a modification position." [PSI:PI] is_a: MS:1002555 ! PTM localization score threshold [Term] id: MS:1002673 name: OpenXQuest def: "Cross-Linking MS search engine." [PSI:PI] is_a: MS:1000752 ! TOPP software [Term] id: MS:1002674 name: X500R QTOF def: "SCIEX X500R QTOF, a quadrupole - quadrupole - time-of-flight mass spectrometer." [PSI:MS] is_a: MS:1000121 ! SCIEX instrument model Changed CV terms in version 3.89.0 of psi-ms.obo: ================================================= ************ Changed the regular expression to allow null for the interaction position [Term] id: MS:1002665 name: regular expression for protein interaction scores derived from cross-linking def: "([:digit:]+[.][a|b]:([:digit:]+|null):[:digit:]+[.][:digit:]+([Ee][+-][0-9]+)*:(true|false]\{1\})" [PSI:PI] is_a: MS:1002479 ! regular expression ************ Obsoleted the following terms. [Term] id: MS:1002455 name: H2O neutral loss def: "OBSOLETE Neutral loss of water." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value H2O. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true [Term] id: MS:1002456 name: NH3 neutral loss def: "OBSOLETE Neutral loss of ammonia." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value NH3. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true [Term] id: MS:1002457 name: H3PO4 neutral loss def: "OBSOLETE Neutral loss of phosphoric acid." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value H3PO4. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true ************ REARRANGEMENT OF PSM-level result details BRANCH ************ ************ The following two terms moved from ************ is_a: MS:1001872 ! distinct peptide-level e-value ************ to is_a: MS:1002353 ! PSM-level e-value [Term] id: MS:1001328 name: OMSSA:evalue def: "OMSSA E-value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002353 ! PSM-level e-value [Term] id: MS:1001330 name: X\!Tandem:expect def: "The X!Tandem expectation value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002353 ! PSM-level e-value ************ The following two terms moved from ************ is_a: MS:1001870 ! distinct peptide-level p-value ************ to is_a: MS:1002352 ! PSM-level p-value [Term] id: MS:1001329 name: OMSSA:pvalue def: "OMSSA p-value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002352 ! PSM-level p-value [Term] id: MS:1001396 name: Phenyx:PepPvalue def: "The p-value of a peptide sequence match in Phenyx." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002352 ! PSM-level p-value ************ The following two terms moved from ************ is_a: MS:1002347 ! PSM-level identification confidence metric ************ to is_a: MS:1001092 ! peptide identification confidence metric [Term] id: MS:1001872 name: distinct peptide-level e-value def: "Estimation of the e-value for distinct peptides once redundant identifications of the same peptide have been removed (id est multiple PSMs have been collapsed to one entry)." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." MS:1001092 ! peptide identification confidence metric relationship: has_domain MS:1002306 ! value greater than zero [Term] id: MS:1001870 name: distinct peptide-level p-value def: "Estimation of the p-value for distinct peptides once redundant identifications of the same peptide have been removed (id est multiple PSMs have been collapsed to one entry)." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." MS:1001092 ! peptide identification confidence metric relationship: has_domain MS:1002305 ! value between 0 and 1 inclusive Best Regards, Gerhard -- *--* *Dipl. Inform. med., Dipl. Wirtsch. **Inf. GERHARD MAYER* *PhD student* *Medizinisches Proteom-Center* *DEPARTMENT Medical Bioinformatics* *Building *ZKF E.049a | Universitätsstraße 150 | D-44801 Bochum *Fon *+49 (0)234 32-21006 | *Fax *+49 (0)234 32-14554 *E-mail***ger...@ru... <mailto:ger...@ru...> www.medizinisches-proteom-center.de <http://www.medizinisches-proteom-center.de/> RUB Logo ANNOUNCEMENT de.NBI summer school September 2016: *Analysis of Mass-Spectrometric Data - * *Big Data Bioinformatics in Proteomics and Metabolomics* http://www.denbi.de/index.php/11-training-cat/95-lss2016 |
From: Chambers, M. <mat...@gm...> - 2016-06-03 20:20:06
|
Hi Gerhard, Could you add a term for the new Sciex X500R QTOF? [Term] id: MS:1000xxx name: X500R QTOF def: "SCIEX X500R QTOF, a quadrupole - quadrupole - time-of-flight mass spectrometer." [PSI:MS] is_a: MS:1000121 ! SCIEX instrument model Thanks, -Matt On 6/3/2016 4:05 AM, mayerg97 wrote: > > Dear proteomics community, > > attached there's the release candidate 3.89.0_rc3 of the psi-ms.obo file. > > > New CV terms in version 3.89.0_rc3 of psi-ms.obo: > ================================================= > ************ Added a string value slot holding the molecular formula in Hill notation > [Term] > id: MS:1000336 > name: neutral loss > def: "The loss of an uncharged species during a rearrangement process. The value slot holds the molecular formula in Hill notation of the > neutral loss molecule, see PMID: 21182243. This term must be used in conjunction with a child of the term MS:1002307 (fragmentation ion > type)." [PSI:MS] > xref: value-type:xsd\:string "The allowed value-type for this CV term." > is_a: MS:1001055 ! modification parameters > > ************ New terms for reporter ions > ************ The mass can be specified in the value slot. > [Term] > id: MS:1002668 > name: frag: iTRAQ 4plex reporter ion > def: "Standard reporter ion for iTRAQ 4Plex. The value slot holds the mass of the iTRAQ 4Plex reporter ion." [PSI:PI] > xref: value-type:xsd\:int "The allowed value-type for this CV term." > is_a: MS:1002307 ! fragmentation ion type > > [Term] > id: MS:1002669 > name: frag: iTRAQ 8plex reporter ion > def: "Standard reporter ion for iTRAQ 8Plex. The value slot holds the mass of the iTRAQ 8Plex reporter ion." [PSI:PI] > xref: value-type:xsd\:int "The allowed value-type for this CV term." > is_a: MS:1002307 ! fragmentation ion type > > [Term] > id: MS:1002670 > name: frag: TMT reporter ion > def: "Standard reporter ion for TMT. The value slot holds the mass of the iTRAQ 8Plex reporter ion and can be suffixed with either N or C, > indicating whether the mass difference is encoded at a Nitrogen or Carbon atom." [PSI:PI] > xref: value-type:xsd\:string "The allowed value-type for this CV term." > is_a: MS:1002307 ! fragmentation ion type > > [Term] > id: MS:1002671 > name: frag: TMT ETD reporter ion > def: "Standard reporter ion for TMT with ETD fragmentation. The value slot holds the mass of the iTRAQ 8Plex reporter ion and can be > suffixed with either N or C, indicating whether the mass difference is encoded at a Nitrogen or Carbon atom." [PSI:PI] > xref: value-type:xsd\:string "The allowed value-type for this CV term." > is_a: MS:1002307 ! fragmentation ion type > > [Term] > id: MS:1002672 > name: no modification threshold > def: "No statistical threshold for accepting or rejecting that a modification position." [PSI:PI] > is_a: MS:1002555 ! PTM localization score threshold > > [Term] > id: MS:1002673 > name: OpenXQuest > def: "Cross-Linking MS search engine." [PSI:PI] > is_a: MS:1000752 ! TOPP software > > > Changed CV terms in version 3.89.0_rc3 of psi-ms.obo: > ===================================================== > ************ Changed the regular expression to allow null for the interaction position > [Term] > id: MS:1002665 > name: regular expression for protein interaction scores derived from cross-linking > def: "([:digit:]+[.][a|b]:([:digit:]+|null):[:digit:]+[.][:digit:]+([Ee][+-][0-9]+)*:(true|false]\{1\})" [PSI:PI] > is_a: MS:1002479 ! regular expression > > ************ Obsoleted the following terms. > [Term] > id: MS:1002455 > name: H2O neutral loss > def: "OBSOLETE Neutral loss of water." [PSI:PI] > comment: This term was obsoleted because it should be replaced by MS:1000336 with value H2O. > is_a: MS:1000336 ! neutral loss > is_a: MS:1002473 ! ion series considered in search > is_obsolete: true > > [Term] > id: MS:1002456 > name: NH3 neutral loss > def: "OBSOLETE Neutral loss of ammonia." [PSI:PI] > comment: This term was obsoleted because it should be replaced by MS:1000336 with value NH3. > is_a: MS:1000336 ! neutral loss > is_a: MS:1002473 ! ion series considered in search > is_obsolete: true > > [Term] > id: MS:1002457 > name: H3PO4 neutral loss > def: "OBSOLETE Neutral loss of phosphoric acid." [PSI:PI] > comment: This term was obsoleted because it should be replaced by MS:1000336 with value H3PO4. > is_a: MS:1000336 ! neutral loss > is_a: MS:1002473 ! ion series considered in search > is_obsolete: true > > ************ REARRANGEMENT OF PSM-level result details BRANCH ************ (see attached figure) > ************ The following two terms moved from > ************ is_a: MS:1001872 ! distinct peptide-level e-value > ************ to is_a: MS:1002353 ! PSM-level e-value > [Term] > id: MS:1001328 > name: OMSSA:evalue > def: "OMSSA E-value." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > is_a: MS:1001143 ! search engine specific score for PSMs > is_a: MS:1001153 ! search engine specific score > is_a: MS:1002353 ! PSM-level e-value > > [Term] > id: MS:1001330 > name: X\!Tandem:expect > def: "The X!Tandem expectation value." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > is_a: MS:1001143 ! search engine specific score for PSMs > is_a: MS:1001153 ! search engine specific score > is_a: MS:1002353 ! PSM-level e-value > > ************ The following two terms moved from > ************ is_a: MS:1001870 ! distinct peptide-level p-value > ************ to is_a: MS:1002352 ! PSM-level p-value > [Term] > id: MS:1001329 > name: OMSSA:pvalue > def: "OMSSA p-value." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > is_a: MS:1001143 ! search engine specific score for PSMs > is_a: MS:1001153 ! search engine specific score > is_a: MS:1002352 ! PSM-level p-value > > [Term] > id: MS:1001396 > name: Phenyx:PepPvalue > def: "The p-value of a peptide sequence match in Phenyx." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > is_a: MS:1001143 ! search engine specific score for PSMs > is_a: MS:1001153 ! search engine specific score > is_a: MS:1002352 ! PSM-level p-value > > ************ The following two terms moved from > ************ is_a: MS:1002347 ! PSM-level identification confidence metric > ************ to is_a: MS:1001092 ! peptide identification confidence metric > [Term] > id: MS:1001872 > name: distinct peptide-level e-value > def: "Estimation of the e-value for distinct peptides once redundant identifications of the same peptide have been removed (id est > multiple PSMs have been collapsed to one entry)." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > MS:1001092 ! peptide identification confidence metric > relationship: has_domain MS:1002306 ! value greater than zero > > [Term] > id: MS:1001870 > name: distinct peptide-level p-value > def: "Estimation of the p-value for distinct peptides once redundant identifications of the same peptide have been removed (id est > multiple PSMs have been collapsed to one entry)." [PSI:PI] > xref: value-type:xsd\:double "The allowed value-type for this CV term." > MS:1001092 ! peptide identification confidence metric > relationship: has_domain MS:1002305 ! value between 0 and 1 inclusive > > > Best Regards, > Gerhard > > -- > > *--* > > *Dipl. Inform. med., Dipl. Wirtsch. **Inf. GERHARD MAYER* > > *PhD student* > > *Medizinisches Proteom-Center* > > *DEPARTMENT Medical Bioinformatics* > > *Building *ZKF E.049a | Universitätsstraße 150 | D-44801 Bochum > > *Fon *+49 (0)234 32-21006 | *Fax *+49 (0)234 32-14554 > > *E-mail***ger...@ru... > > www.medizinisches-proteom-center.de > > RUB Logo > > ANNOUNCEMENT de.NBI summer school September 2016: > > *Analysis of Mass-Spectrometric Data - * > > *Big Data Bioinformatics in Proteomics and Metabolomics* > > <http://www.denbi.de/index.php/11-training-cat/95-lss2016>http://www.denbi.de/index.php/11-training-cat/95-lss2016 > |
From: mayerg97 <ger...@ru...> - 2016-06-03 09:05:31
|
Dear proteomics community, attached there's the release candidate 3.89.0_rc3 of the psi-ms.obo file. New CV terms in version 3.89.0_rc3 of psi-ms.obo: ================================================= ************ Added a string value slot holding the molecular formula in Hill notation [Term] id: MS:1000336 name: neutral loss def: "The loss of an uncharged species during a rearrangement process. The value slot holds the molecular formula in Hill notation of the neutral loss molecule, see PMID: 21182243. This term must be used in conjunction with a child of the term MS:1002307 (fragmentation ion type)." [PSI:MS] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1001055 ! modification parameters ************ New terms for reporter ions ************ The mass can be specified in the value slot. [Term] id: MS:1002668 name: frag: iTRAQ 4plex reporter ion def: "Standard reporter ion for iTRAQ 4Plex. The value slot holds the mass of the iTRAQ 4Plex reporter ion." [PSI:PI] xref: value-type:xsd\:int "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002669 name: frag: iTRAQ 8plex reporter ion def: "Standard reporter ion for iTRAQ 8Plex. The value slot holds the mass of the iTRAQ 8Plex reporter ion." [PSI:PI] xref: value-type:xsd\:int "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002670 name: frag: TMT reporter ion def: "Standard reporter ion for TMT. The value slot holds the mass of the iTRAQ 8Plex reporter ion and can be suffixed with either N or C, indicating whether the mass difference is encoded at a Nitrogen or Carbon atom." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002671 name: frag: TMT ETD reporter ion def: "Standard reporter ion for TMT with ETD fragmentation. The value slot holds the mass of the iTRAQ 8Plex reporter ion and can be suffixed with either N or C, indicating whether the mass difference is encoded at a Nitrogen or Carbon atom." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1002307 ! fragmentation ion type [Term] id: MS:1002672 name: no modification threshold def: "No statistical threshold for accepting or rejecting that a modification position." [PSI:PI] is_a: MS:1002555 ! PTM localization score threshold [Term] id: MS:1002673 name: OpenXQuest def: "Cross-Linking MS search engine." [PSI:PI] is_a: MS:1000752 ! TOPP software Changed CV terms in version 3.89.0_rc3 of psi-ms.obo: ===================================================== ************ Changed the regular expression to allow null for the interaction position [Term] id: MS:1002665 name: regular expression for protein interaction scores derived from cross-linking def: "([:digit:]+[.][a|b]:([:digit:]+|null):[:digit:]+[.][:digit:]+([Ee][+-][0-9]+)*:(true|false]\{1\})" [PSI:PI] is_a: MS:1002479 ! regular expression ************ Obsoleted the following terms. [Term] id: MS:1002455 name: H2O neutral loss def: "OBSOLETE Neutral loss of water." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value H2O. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true [Term] id: MS:1002456 name: NH3 neutral loss def: "OBSOLETE Neutral loss of ammonia." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value NH3. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true [Term] id: MS:1002457 name: H3PO4 neutral loss def: "OBSOLETE Neutral loss of phosphoric acid." [PSI:PI] comment: This term was obsoleted because it should be replaced by MS:1000336 with value H3PO4. is_a: MS:1000336 ! neutral loss is_a: MS:1002473 ! ion series considered in search is_obsolete: true ************ REARRANGEMENT OF PSM-level result details BRANCH ************ (see attached figure) ************ The following two terms moved from ************ is_a: MS:1001872 ! distinct peptide-level e-value ************ to is_a: MS:1002353 ! PSM-level e-value [Term] id: MS:1001328 name: OMSSA:evalue def: "OMSSA E-value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002353 ! PSM-level e-value [Term] id: MS:1001330 name: X\!Tandem:expect def: "The X!Tandem expectation value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002353 ! PSM-level e-value ************ The following two terms moved from ************ is_a: MS:1001870 ! distinct peptide-level p-value ************ to is_a: MS:1002352 ! PSM-level p-value [Term] id: MS:1001329 name: OMSSA:pvalue def: "OMSSA p-value." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002352 ! PSM-level p-value [Term] id: MS:1001396 name: Phenyx:PepPvalue def: "The p-value of a peptide sequence match in Phenyx." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for PSMs is_a: MS:1001153 ! search engine specific score is_a: MS:1002352 ! PSM-level p-value ************ The following two terms moved from ************ is_a: MS:1002347 ! PSM-level identification confidence metric ************ to is_a: MS:1001092 ! peptide identification confidence metric [Term] id: MS:1001872 name: distinct peptide-level e-value def: "Estimation of the e-value for distinct peptides once redundant identifications of the same peptide have been removed (id est multiple PSMs have been collapsed to one entry)." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." MS:1001092 ! peptide identification confidence metric relationship: has_domain MS:1002306 ! value greater than zero [Term] id: MS:1001870 name: distinct peptide-level p-value def: "Estimation of the p-value for distinct peptides once redundant identifications of the same peptide have been removed (id est multiple PSMs have been collapsed to one entry)." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." MS:1001092 ! peptide identification confidence metric relationship: has_domain MS:1002305 ! value between 0 and 1 inclusive Best Regards, Gerhard -- *--* *Dipl. Inform. med., Dipl. Wirtsch. **Inf. GERHARD MAYER* *PhD student* *Medizinisches Proteom-Center* *DEPARTMENT Medical Bioinformatics* *Building *ZKF E.049a | Universitätsstraße 150 | D-44801 Bochum *Fon *+49 (0)234 32-21006 | *Fax *+49 (0)234 32-14554 *E-mail***ger...@ru... <mailto:ger...@ru...> www.medizinisches-proteom-center.de <http://www.medizinisches-proteom-center.de/> RUB Logo ANNOUNCEMENT de.NBI summer school September 2016: *Analysis of Mass-Spectrometric Data - * *Big Data Bioinformatics in Proteomics and Metabolomics* http://www.denbi.de/index.php/11-training-cat/95-lss2016 |
From: Mathias W. <not...@gi...> - 2016-06-01 16:28:00
|
--- You are receiving this because you are subscribed to this thread. View it on GitHub: https://github.com/HUPO-PSI/mzIdentML/releases/tag/mzIdentMLValidator_GUI_v1.4.17-SNAPSHOT |
From: Mathias W. <not...@gi...> - 2016-06-01 16:02:50
|
I updated the release to the current and fixed the link on the start page to the release page. @germa if you could create a github release (https://github.com/HUPO-PSI/psi-ms-CV/releases/new) when you release a new version of the validator, welcome page will always point to the most recent validator. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/21#issuecomment-223040900 |
From: andrewrobertjones <not...@gi...> - 2016-06-01 15:51:08
|
Agreed to this change e.g. <cvParam name = "neutral loss" value = "H2O"/> @germa Can you action this, and I will add this to the spec doc --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/34#issuecomment-223037152 |
From: andrewrobertjones <not...@gi...> - 2016-06-01 15:32:49
|
Discussed the correct behaviour should be to check 2 or 4 having the same value --> 4 for the case of stable isotopes only --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/31#issuecomment-223030612 |
From: andrewrobertjones <not...@gi...> - 2016-06-01 15:27:56
|
Discussed on the call today - generally this seems sensible, I will provisionally add this to the spec doc --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/30#issuecomment-223029637 |
From: Mathias W. <not...@gi...> - 2016-06-01 15:21:26
|
I just saw that Yasset already built github releases for the validator :smiley: So for a better accessibility, we would just have to update the releases and link to the release site from the repository start page. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/21#issuecomment-223027231 |
From: Mathias W. <not...@gi...> - 2016-06-01 15:16:30
|
In the telco I was referring to that: https://github.com/HUPO-PSI/psi-ms-CV/releases --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/21#issuecomment-223025390 |
From: Gerhard M. <not...@gi...> - 2016-06-01 13:58:05
|
Should we define a generic neutral loss term as proposed by Steffen Neumann, see https://sourceforge.net/p/psidev/mailman/psidev-ms-vocab/?viewmonth=201605&viewday=25 and should be the terms id: MS:1002455 ! H2O neutral loss, id: MS:1002456 ! NH3 neutral loss and id: MS:1002457 ! H3PO4 neutral loss then be made obsolete? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/34 |
From: F. G. <not...@gi...> - 2016-06-01 08:42:52
|
Closed #4. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/4#event-678102993 |
From: Jones, A. <And...@li...> - 2016-06-01 08:23:42
|
Hi all, Apologies for the short notice. Assuming people can join, let's have an mzid 1.2 call at 4pm UK today (1st June): http://www.timeanddate.com/worldclock/fixedtime.html?iso=20160601T16&p1=301 We will work through the issue list: https://github.com/HUPO-PSI/mzIdentML/issues as far as possible. Please check in any updates to example files, and report back whether the validator appears to be catching both good and bad examples correctly. Best wishes Andy Numbers: + UK: 0808 109 5644 + US: 877-420-0272 + Belgium: 0800 509 80 + Germany: 0800 101 2079 + Switzerland: 0800 000 860 + Generic international: +44 (0) 20 8322 2500 (UK number) Access code: 297427 # |
From: Mathias W. <not...@gi...> - 2016-05-31 16:15:51
|
**One idea** would be to allow strings in the values of ```<FragmentArray>``` elements and by convention let these strings be accessions to CVs defined in the ```<Measurement>```. **The other** would be to introduce an additional abstraction of ```<FragmentArray>``` for ```<FragmentCVREFArray>```. ```<Measurement>``` for these would have to be allowed to carry several cv, one for each possible type of annotation flag. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/32#issuecomment-222739736 |
From: Mathias W. <not...@gi...> - 2016-05-31 16:12:09
|
If we would decide to introduce CVs like frag: y ion - alpha, ... this would also add to the bloat of the file, as there would be more ```<IonType>``` elements. This would also bloat the CV. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/32#issuecomment-222738013 |
From: Mathias W. <not...@gi...> - 2016-05-31 16:04:46
|
For any software it would not make much sense to rip apart the annotations to one spectrum - and puzzle it back together. - Though this would solve the problem of denoting alpha/beta, not so for ci/xi ions. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/32#issuecomment-222736546 |
From: Mathias W. <not...@gi...> - 2016-05-31 15:52:58
|
Merged #33. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/pull/33#event-677212464 |
From: Mathias W. <not...@gi...> - 2016-05-31 15:48:46
|
You can view, comment on, or merge this pull request online at: https://github.com/HUPO-PSI/mzIdentML/pull/33 -- Commit Summary -- * removed annotations from initial example -- File Changes -- M examples/1_2examples/crosslinking/OpenxQuest_example.mzid (344) -- Patch Links -- https://github.com/HUPO-PSI/mzIdentML/pull/33.patch https://github.com/HUPO-PSI/mzIdentML/pull/33.diff --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/pull/33 |
From: Eugen N. <not...@gi...> - 2016-05-31 15:34:09
|
We are trying to implement fragment annotations for cross-linked peptides in OpenMS and uploaded an example file under examples/1_2examples/crosslinking/OpenxQuest_example.mzid. In the case of cross-linking we have fragments resulting from cleavages of both peptides in one spectrum. Therefore distributing the annotations between several SIIs would make further usage e.g. visualization of these annotations more complicated and the separation would not be possible in more complex fragmentation patterns, e.g. cross-linked fragments where both peptides were cleaved. So we would prefer to store the annotations for one PSM under one SII, e.g. the light alpha case. The example suggests adapting FragmentArray to also carry strings (words) or have an additional array carrying these (not in the example). The specific CVs we would need are: One Array for "cross-link chain" containing CV strings for "donor" or "acceptor" for each fragment. One Array for "cross-link ion category" containing CV strings for "common ion" or "cross-linked ion" for each fragment. The example file shows roughly how that could look like. Another way to do it would be to introduce additional IonTypes and therefore separate these types into different arrays. In that case we would need all four combinations of donor/receiver with common/cross-linked --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/32 |
From: Gerhard M. <not...@gi...> - 2016-05-31 14:59:41
|
Closed #8. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/8#event-677129821 |
From: Gerhard M. <not...@gi...> - 2016-05-31 14:57:49
|
Solved now. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/8#issuecomment-222715139 |
From: Eugen N. <not...@gi...> - 2016-05-31 14:24:02
|
The CV accession="MS:1002511" name="cross-link spectrum identification item" must have the same value for SIIs that represent a pair of cross-linked peptides. Currently the validator only allows exactly two equal values, but we have 4 SIIs for the same cross-link when using isotope labelled linkers. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/31 |
From: Eugen N. <not...@gi...> - 2016-05-31 14:15:23
|
Closed #14. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/14#event-677064751 |
From: Gerhard M. <not...@gi...> - 2016-05-31 12:34:13
|
Closed #29. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/29#event-676932979 |
From: Gerhard M. <not...@gi...> - 2016-05-31 12:34:10
|
Fixed in version 1.4.17 --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/HUPO-PSI/mzIdentML/issues/29#issuecomment-222674877 |