Comments (5)
Whether or not to include units in the CV has been a topic of some discussion already. In the end we settled on having explicit units for the quality metrics in the mzQC files.
There should indeed be restrictions on some values. This is part of what the semantic validation of the official Python parser checks. So far we haven't made these restrictions explicit in the CV, but it might be relevant to consider that.
from mzqc.
Overview of semantic validation in issue #50. Please add any checks that should still be included.
from mzqc.
I agree, that many CVs need further description. It would be great, if the inventors of the metrics, or the persons who created them in their programs/workflows/pipelines could provide a better description.
The descriptions used by me so far where from some documents I found when I started to take over the CV or my own tries to interpret the CV.
The best way to get good descriptions for the items in the CV would be, if you could open an request-new-CV-entry-issue with the description etc.
(I know, I did not have much time in the last weeks, but should have some more to finish v1.0 now).
from mzqc.
Probably the best way to get better descriptions is to ping the tool developers directly and explicitly mention the metrics that need to be improved. Otherwise I'm afraid not much will happen, as I doubt that many people will have seen this issue. :)
from mzqc.
This will be handled by the "comment" information in the CV and the requirements for better descriptions in the future.
from mzqc.
Related Issues (20)
- Our set-of-runs example needs a CV term in PSI-MS HOT 1
- For metabo and set-of-runs example needs a PSI-MS CV terms (instead of QC CV HOT 2
- mtb example has 2 minor issues HOT 1
- mzML example still uses QC CV terms HOT 3
- USI example uses wrong SHA term accession
- individual run example needs updating HOT 2
- QC2 sample needs update
- github representation needs dust-up and proof-read
- Remove QC CV from markup docs
- Some parent terms not found when loading qc-cv.obo HOT 2
- Default values in analysisSoftware for version and uri HOT 2
- Logo for MS-Quality-hub HOT 1
- Repository documentation HOT 1
- Discuss format for date-time fields in mzQC HOT 4
- Add guide to visualisation from metrics HOT 4
- CI for semantic validation of example files not working
- Collection of QC tools
- Update examples to mzQC v1.0 HOT 2
- For non-proteomics MS QC it would be nice to have .. HOT 3
- Provide guidelines on mzQC merging
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 mzqc.