Menu
▾
▴
psidev-pi-dev
|
From: <cod...@go...> - 2009-06-17 16:36:13
|
Comment #78 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 In response to comment 77, I think you should use: id: MS:1001125 name: manual validation I'm not sure about user comments. Currently, values are not allowed for this CV term but we could allow a string value to be populated with comments. Any opinions? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-17 19:23:22
|
Comment #79 on issue 42 by pierrealainbinz: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 A string would be minimally ok, but I would suggest a kind of binary value: true /false or accepted/rejected -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-17 19:52:41
|
Comment #80 on issue 42 by dcreasy: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 I think that the passThreshold="true" or passThreshold="false" attributes should still apply? It's just that it is the user's own threshold in this case. In which case, adding a string value to the comments would be fine. Um... looks like it can take a string already: [Term] id: MS:1001125 name: manual validation def: "Result of quality estimation: decision of a manual validation." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." Perhaps we just need to add this to one of the examples? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-23 10:45:01
|
Comment #81 on issue 42 by dcreasy: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 We seem to have two different ways of specifying taxonomy: <SequenceCollection> <DBSequence id="DBSeq_HSP7D_MANSE" length="652" SearchDatabase_ref="SDB_SwissProt" accession="HSP7D_MANSE" > <seq>MAKAPAVGIDLGTTYSCVGVFQHGKVEIIANDQGNRTTPSYVAFTDTDRLIGDAAKNQVAMNP...</seq> <cvParam accession="MS:1001088" name="protein description" cvRef="PSI-MS" value="Heat shock 70 kDa protein cognate... - Manduca sexta ..." /> <cvParam accession="MS:1001469" name="taxonomy: scientific name" cvRef="PSI-MS" value="Manduca sexta"/> <cvParam accession="MS:1001467" name="taxonomy: NCBI TaxID" cvRef="PSI-MS" value="7130"/> </DBSequence> and <cv id="NCBI-TAXONOMY" fullName="NCBI-TAXONOMY" URI="ftp://ftp.ncbi.nih.gov/pub/taxonomy/taxdump.tar.gz"></cv> . . . <DatabaseFilters> <Filter> <FilterType> <cvParam accession="MS:1001020" name="DB filter taxonomy" cvRef="PSI-MS" /> </FilterType> <Include> <cvParam accession="NCBI:33208" name="Metazoa" cvRef="NCBI-TAXONOMY" /> </Include> </Filter> </DatabaseFilters> Obviously we should be consistent and get rid of one of the methods. The other CV that could be used in the first example is: id: MS:1001470 name: taxonomy: Swiss-Prot ID id: MS:1001468 name: taxonomy: common name I suggest that we ditch the second method and allow: MS:1001467 - taxonomy: NCBI TaxID MS:1001468 - taxonomy: common name MS:1001469 - taxonomy: scientific name MS:1001470 - taxonomy: Swiss-Prot ID to be included in DatabaseFilters/Filter/Include For MS:1001468, MS:1001469, MS:1001470, I would like to see something like this added to the def: Recommend using MS:1001467 where possible For MS:1001467, the type should be an unsigned 32 bit integer -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-23 15:49:05
|
Comment #82 on issue 42 by a.bertsch0815: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Should the FDR threshold terms be allowed to have units? i.e. "MS:1001447 - prot:FDR threshold" and the respective pep term. per cent? parts per notation? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-24 08:29:35
|
Comment #83 on issue 42 by eisenachM: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 We use percent, but both should be allowed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-25 15:52:01
|
Comment #84 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Decided to allow the following two terms only: [Term] id: UO:0000186 name: dimensionless unit def: "A derived unit which is a standard measure of physical quantity consisting of only a numerical number without any units." [Wikipedia:Wikipedia "http://www.wikipedia.org/"] is_a: UO:0000046 ! derived unit [Term] id: UO:0000187 name: percent def: "A dimensionless ratio unit which denotes numbers as fractions of 100." [Wikipedia:Wikipedia "http://www.wikipedia.org/"] synonym: "%" EXACT [] is_a: UO:0000190 ! ratio we need examples of these i.e. "5" "percent" and "0.05" "dimensionless unit" -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-26 10:33:02
|
Comment #85 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Fixing the mapping for taxonomy, a similar mapping is required for 3 parts of the schema: - Sample (previously called GenericMaterial) - DBSequence - Filter Include/Exclude Filter currently maps to "database filtering" which has a child term: DB filter taxonomy. This term should be depracated. I have added a mapping for all three to the child terms of MS:1001089 "molecule taxonomy" I have also added a mapping from FilterType to the exact term (no child terms) "molecule taxonomy" "molecule taxonomy" is currently a child of "database sequence details" so we should move it up the hierarchy so it covers samples as well. Andreas, can you give me a mail offline to check through these changes? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-26 13:29:46
|
Comment #86 on issue 42 by eisenachM: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 When correcting the MPC example it became obvious that some CV terms are missing: [Term] id: MS:1001XXX name: ProteinScape:SearchResultId def: "The SearchResultId of this peptide as SearchResult in the ProteinScape database." xref: value-type:xsd\:positiveInteger "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:SearchEventId def: "The SearchEventId of the SearchEvent in the ProteinScape database." xref: value-type:xsd\:positiveInteger "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:ProfoundProbability def: "The Profound probability score stored by ProteinScape." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: Profound:z value def: "The Profound z value." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: Profound:Cluster def: "The Profound cluster score." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: Profound:ClusterRank def: "The Profound cluster rank." xref: value-type:xsd\:positiveInteger "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: MSFit:Mowse score def: "The MSFit Mowse score." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: Sonar:Score def: "The Sonar score." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:PFFSolverExp def: "The ProteinSolver exp value stored by ProteinScape." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:PFFSolverScore def: "The ProteinSolver score stored by ProteinScape." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:IntensityCoverage def: "The intensity coverage of the identified peaks in the spectrum calculated by ProteinScape." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinScape:SequestMetaScore def: "The Sequest meta score calculated by ProteinScape from the original Sequest scores." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001143 ! search engine specific score for peptides is_a: MS:1001153 ! search engine specific score [Term] id: MS:1001XXX name: ProteinExtractor:Score def: "The score calculated by ProteinExtractor." xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001116 ! single protein result details is_a: MS:1001153 ! search engine specific score -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-26 14:09:53
|
Comment #87 on issue 42 by eisenachM: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 The validator gives errors for the MPC example, because value types of some CV terms are set to 'boolean', although they should have: type string: 'MS:1001424 - ProteinExtractor:Methodname' type positiveInteger: 'MS:1001427 - ProteinExtractor:MaxNumberOfProteins' type double, unit Dalton: 'MS:1001428 - ProteinExtractor:MaxProteinMass' type positiveInteger: 'MS:1001429 - ProteinExtractor:MinNumberOfPeptides' -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-29 14:21:11
|
Comment #88 on issue 42 by a.bertsch0815: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Implemented changes in CV and mapping file Addressing comments 81-84,86,87 Semantic Validator is also up-to-date -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-30 14:53:02
|
Comment #89 on issue 42 by dcreasy: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Latest Mascot examples give these errors. I think that the mapping needs to be changed! Obsolete CV term: 'MS:1001020 - DB filter taxonomy' at element '/mzIdentML/AnalysisProtocolCollection/SpectrumIdentificationProtocol/DatabaseFilters/Filter/FilterType' CV term used in invalid element: 'MS:1001316 - mascot:SigThreshold' at element '/mzIdentML/AnalysisProtocolCollection/ProteinDetectionProtocol/Threshold' CV term used in invalid element: 'MS:1001316 - mascot:SigThreshold' at element '/mzIdentML/AnalysisProtocolCollection/SpectrumIdentificationProtocol/Threshold' Violated mapping rule 'ProteinDetectionProtocolThreshold_rule' at element '/mzIdentML/AnalysisProtocolCollection/ProteinDetectionProtocol/Threshold' exactly one of the allowed terms must be used! Violated mapping rule 'SpectrumIdentificationProtocolThreshold_rule' at element '/mzIdentML/AnalysisProtocolCollection/SpectrumIdentificationProtocol/Threshold' exactly one of the allowed terms must be used! -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-30 14:54:11
|
Comment #90 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 This has been added to the CV for prot:FDR threshold relationship: has_units UO:0000186 ! dimensionless unit relationship: has_units UO:0000187 ! percent The same needs to be added for pep:FDR threshold -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-06-30 16:06:21
|
Comment #91 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 I have updated the mapping for threshold to include: "search engine specific input parameter" and changed XOR to OR -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-07-08 15:51:36
|
Comment #92 on issue 42 by eisenachM: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 I checked some (from MS:100100X to approx. MS:1001051) CV terms and found some errors: very many CV terms have no "[PSI:PI]" after the definition. Is it necessary? MS:1001420, SpectraST:delta: wrongly spelled: "[:PSI-PI]" instead of "[PSI:PI]" MS:1001007, sequest:Output lines: value type missing (xsd:nonNegativeInteger ?) MS:1001014, database local file path: value type xsd:string is missing MS:1001016, database version: value type xsd:string is missing There is a "version" attribute in the <Searchdatabase> element. One of both is not necessary. MS:1001017, database release date: value type xsd:string is missing There is a "releaseDate" attribute in the <Searchdatabase> element. One of both is not necessary. MS:1001019, database filtering: In the definition, what does "public or private" mean? MS:1001020, DB filter taxonomy: def should be changed: "A taxonomy filter was applied to the search database." [PSI:PI] MS:1001024, translation frame: value type is missing In the Mascot NA example, a <DatabaseTranslation> element is used, using a "frames" attribute. Is the CV term obsolete? MS:1001028, sequest:SequenceHeaderFilter: value type missing (xsd:string ?) MS:1001032, sequest:SequencePartialFilter: value type missing (xsd:string ?) MS:1001035, date / time search performed: value type missing (xsd:dateTime) The <SpectrumIdentification> element has an "activityDate" attribute. One of both is not necessary. MS:1001037, sequest:ShowFragmentIons: value type missing (xsd:boolean) MS:1001038, sequest:Consensus: value type missing (xsd:positiveInteger) MS:1001051, multiple enzyme combination rules: value type missing (xsd:string ?) The term is not referenced in the mapping file (nor is cleavage agent details, its parent). Additionally the <Enzyme> element has an "independent" attribute. Can this CV term be deleted? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-07-09 10:41:07
|
Comment #93 on issue 42 by javizca74: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 I sent my comments to Andreas. I am not including here minor typo errors. I am also attaching Andreas comments (### lines). 1) These 2 terms are somehow redundant. The def of MS:1001013 should be changed (remove the examples, I guess): [Term] id: MS:1001011 name: search database details def: "Details about the database searched." [PSI:PI] is_a: MS:1001249 ! search input details [Term] id: MS:1001013 name: database name def: "The name of the search database (nr, SwissProt or est_human)." [PSI:PI] is_a: MS:1001011 ! search database details ##### the 1001013 term is used for mapping to ##### /mzIdentML/DataCollection/Inputs/SearchDatabase/DatabaseName/cvParam/@accession ##### all the child term of the 1013 are allowed here, but not the term itself ##### the first term is mapped to /mzIdentML/DataCollection/Inputs/SearchDatabase/cvParam/@accession ##### and contains a large collection of terms ##### however, some of the child terms of 1001011 should not be used. ##### maybe we should restructure the CV, to only allow term that make sense? 2) Perhaps the def should be changed in the definition? (range:-3, +3, not zero, instead of 1-6). [Term] id: MS:1001024 name: translation frame def: "The translated open reading frames from a nucleotide database considered in the search (range: 1-6)." [PSI:PI] is_a: MS:1001011 ! search database details 3) Perhaps change term name DB filter on sequences” to “DB filter on amino acid sequence pattern”? [Term] id: MS:1001027 name: DB filter on sequences def: "Filtering applied specifically by amino acid sequence pattern." [PSI:PI] is_a: MS:1001019 ! database filtering ##### maybe "DB filter on sequence pattern"? The phrase amino acid would restrict it to protein databases 4)Change term name to quality estimation method details? [Term] id: MS:1001060 name: quality estimation details def: "Method for quality estimation (manually or wih decoy database)." [PSI:PI] is_a: MS:1001249 ! search input details #### accepted and done 5) Delete this one? [Term] id: MS:1001060 name: quality estimation details def: "Method for quality estimation (manually or wih decoy database)." [PSI:PI] is_a: MS:1001249 ! search input details #### same as above? 6) Updated def. I would change the name to “database type nucleotide”: [Term] id: MS:1001079 name: database type NA def: "Database contains nucleic acid sequences." [PSI:PI] is_a: MS:1001018 ! database type #### accepted and done 7) I would update the term to “sequence coverage”. [Term] id: MS:1001093 name: coverage def: "The percent coverage for the protein based upon the matched peptide sequences (can be calculated)." [PSI:PI] xref: value-type:xsd\:decimal "The allowed value-type for this CV term." is_a: MS:1001116 ! single protein result details #### accepted and done 8) Update def: [Term] id: MS:1001115 name: scan number(s) def: "Take from mzData. TODO: What does this mean?" [PSI:PI] is_a: MS:1001105 ! peptide result details 9) Change this term: this is not a name for any database. It could be changed to “database type EST”. Or if you are referring to the EST database from NCBI, it should be called: dbEST. [Term] id: MS:1001178 name: database EST is_a: MS:1001013 ! database name 10) Add synonyms to all terms containing “product ion” (fragment ion). [Term] id: MS:1001225 name: product ion m/z def: "The m/z of the product ion." [PSI:PI] is_a: MS:1001221 ! fragmentation information [Term] id: MS:1001226 name: product ion intensity def: "The intensity of the product ion." [PSI:PI] is_a: MS:1001221 ! fragmentation information [Term] id: MS:1001227 name: product ion m/z error def: "The product ion m/z error (ADD more docu here)." [PSI:PI] is_a: MS:1001221 ! fragmentation information #### accepted and done 11) This term name is wrong. There is no database called EST (dbEST is the one from the NCBI, for instance). [Term] id: MS:1001295 name: decoy DB from EST is_a: MS:1001284 ! decoy DB derived from #### see 9) above 12) Is it pending to add more mascot related terms? [Term] id: MS:1001326 name: TODO_add_others is_a: MS:1001302 ! search engine specific input parameter 13) These terms are redundant: [Term] id: MS:1001343 name: NA sequence def: "The sequence is a nucleic acid sequence." [PSI:PI] is_a: MS:1001342 ! database sequence details [Term] id: MS:1001344 name: AA sequence def: "The sequence is a amino acid sequence." [PSI:PI] is_a: MS:1001342 ! database sequence details There are those ones: [Term] id: MS:1001073 name: database type AA def: "Database contains amino acid sequences." [PSI:PI] is_a: MS:1001018 ! database type [Term] id: MS:1001079 name: database type NA def: "Database contains nucleic acid sequences." [PSI:PI] is_a: MS:1001018 ! database type #### right these are redundant. However, they can be used in different locations #### I would suggest to keep them -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-07-09 11:00:09
|
Comment #94 on issue 42 by javizca74: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 Some ion types are missing in the CV. We have added to the PRIDE CV, in order to provide fragment ion annotation. - At the moment there are no -H2O and -NH3 ions for ions c, x and z. - The same above for precursor ion. - We have also found that mascot reports the specific type of immonium ion: immonium A immonium C immonium D immonium E immonium F immonium H immonium I immonium K immonium L immonium M immonium N immonium P immonium Q immonium R immonium S immonium T immonium V immonium W immonium Y -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
|
From: <cod...@go...> - 2009-07-09 13:55:30
|
Comment #95 on issue 42 by andrewrobertjones: Issues with the CV http://code.google.com/p/psi-pi/issues/detail?id=42 These are all fairly minor so can probably be fixed without discussion 1. I think this term need a unit: e.g. relationship: has_units UO:0000221 ! dalton relationship: has_units UO:0000222 ! kilodalton [Term] id: MS:1001361 name: alternate mass def: "List of masses a non-standard letter code is replaced with." [PSI:PI] xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001359 ! ambiguous residues 2. I don't see the point of this term: [Term] id: MS:1001057 name: tolerance on types def: "Tolerance on types." [PSI:PI] is_a: MS:1001055 ! modification parameters 3. Most of the children of quantification have errors (missing data type/unit) but we can probably leave these for now: [Term] id: MS:1001129 name: quantification information def: "Quantification information." [PSI:PI] relationship: part_of MS:1001000 ! spectrum interpretation 4. This term needs a datatype (xref: value-type:xsd\:string "The allowed value-type for this CV term.") [Term] id: MS:1001051 name: multiple enzyme combination rules def: "Description of multiple enzyme digestion protocol, if any." [PSI:PI] is_a: MS:1001044 ! cleavage agent details 5. This term and related terms need units e.g. relationship: has_units UO:0000221 ! dalton relationship: has_units UO:0000222 ! kilodalton [Term] id: MS:1001201 name: DB MW filter maximum xref: value-type:xsd\:double "The allowed value-type for this CV term." is_a: MS:1001512 ! Sequence database filters 6. This term needs a URI datatype? (xsd:anyURI) [Term] id: MS:1001014 name: database local file path def: "Local file path of the search database from the search engine's point of view." [PSI:PI] is_a: MS:1001011 ! search database details 7. Add date type to this (xsd:dateTime) [Term] id: MS:1001017 name: database release date def: "Release date of the search database." [PSI:PI] is_a: MS:1001011 ! search database details 8. Change string datatype to URI? [Term] id: MS:1001015 name: database original uri def: "URI, from where the search database was originally downloaded." [PSI:PI] xref: value-type:xsd\:string "The allowed value-type for this CV term." is_a: MS:1001011 ! search database details 9. Needs a string datatype: [Term] id: MS:1001016 name: database version def: "Version of the search database ." [PSI:PI] is_a: MS:1001011 ! search database details 10. this needs a datatype (not exactly sure if an int or a string?): [Term] id: MS:1001024 name: translation frame def: "The translated open reading frames from a nucleotide database considered in the search (range: 1-6)." [PSI:PI] is_a: MS:1001011 ! search database details -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X