Comments (7)
New CV Terms in the PRIDE Ontology:
id: PRIDE:0000544
name: MS1 mass analyzer
def: "MS1 mass analyzer" []
is_a: MS:1000451 ! mass analyzer
created_by: yperez
[Term]
id: PRIDE:0000545
name: MS2 mass analyzer
def: "MS2 mass analyzer" []
is_a: MS:1000451 ! mass analyzer
Created
from proteomics-sample-metadata.
You would like two columns?:
MS1 mass analyzer type
MS2 mass analyzer type
Yep, sounds perfect.
Lets use comment[normalized collision energy]
But sometimes collision energy isn't normalized. I think instead of making two comments, it may be better to make one, [collision energy]
with possible units "NCE" and "eV", so the first one would be for normalized collision energy and the second one for non-normalised one?
And then the structure will be a number and unit.
from proteomics-sample-metadata.
Is there a way to specify fragmentation energy in an annotation? Should I just use comment[collision energy]
and fill it with e.g. '28 NCE' / '20 eV' ?
Update: found it in the "major changes #214 " with exactly this way to specify it.
from proteomics-sample-metadata.
- For some Orbitraps it's possible to measure fragments in the ion trap or the Orbitrap. It would be nice to add this information (probably next to the
comment [instrument]
). It may be a bit redundant since there is information about fragment tolerance, but an explicit "MS2 analyzer type" column would be a more straightforward characterization of the experiment.
-
@lisavetasol in the ols, you can check under
mass analyzer
all the possible values mass analyzer. Those that make sense? Some examples: -
time-of-flight
-
quadrupole
- There seems to be no way of specifying HCD/CID energy. Since some tools can predict fragmentation spectra for particular energy, this parameter may be helpful with in silico libraries for DIA and different dot product scores.
In the ols two terms can be use to define energy:
Please, if you think one of these is the appropriate terms let me know. I can add that to the documentation. AS I said before these terms (columns) should be optional (RECOMMENDED).
from proteomics-sample-metadata.
- these
mass analyzer type
values look good, but the issue is that it should be possible to specify different mass analyzer types for MS1 and MS/MS spectra. - I think collision energy is the right term, but there should be also normalized collision energy since most of instruments measuring it not explicitly in eV, but in NCE.
from proteomics-sample-metadata.
- these
mass analyzer type
values look good, but the issue is that it should be possible to specify different mass analyzer types for MS1 and MS/MS spectra.
-
You would like two columns?:
-
MS1 mass analyzer type
-
MS2 mass analyzer type
- I think collision energy is the right term, but there should be also normalized collision energy since most of instruments measuring it not explicitly in eV, but in NCE.
- Lets use
comment[normalized collision energy]
from proteomics-sample-metadata.
@lisavetasol In the normalized collision energy what will be the structure of the value? A Number, a Number with a unit?
from proteomics-sample-metadata.
Related Issues (20)
- Request Project Annotation [PXD015270]
- [ENH] Add check for outdated link targets to CI HOT 1
- MassIVE download links are still FTP HOT 7
- Metaproteomics datasets annotation
- Help needed [ PXD010436]
- Request Project Annotation [ PXD009199]
- Request Project Annotation [PXD010436 ]
- Annotation questions (general & bacteria specific) HOT 3
- Version 1.1 requirements and improvements
- FAIRsharing query - current status of Investigation Description Format for Proteomics (IDF)
- Extending SDRF for Metabolomics HOT 13
- Add comment [ms3 mass analyzer] and [ms3 dissociation method] for MS3 level? HOT 6
- JSON representation for the SDRF format
- SDRF for affinity proteomics datasets
- Instrument - timsTOF HT HOT 3
- Fields to decide for the sdrf metabolomics; [REQUIRED, RECOMMENDED, OPTIONAL] HOT 1
- Metabolomnics technology type HOT 4
- SDRF error: Value is not match with ontology HOT 2
- Labelling in metabolomics HOT 3
- Extending SDRF for metaproteomics
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from proteomics-sample-metadata.