New version and structure of repository about mzqc HOT 7 CLOSED

👍
I just created a label for v1.0
and a management board

from mzqc.

Playing necromancer here for a bit, finding what happened to the old CV's was challenging with current documentation. I'd suggest including a note somewhere in either the readme or the spec-doc as bread-crumbs for anyone getting up to speed.

from mzqc.

Which version did you need specifically, and what is different about it?

Normally CV updates will only consist of additions, so the latest version should have all the terms of older versions as well. Why would you need an older version of the CV?

from mzqc.

from mzqc.

I think loading the OBO from the old branch is going to be the best solution.

Moving from qcML to mzQC was a non-backwards compatible change, and merging the QC CV with the MS now, as required before finalization of mzQC v1.0 (#141), will definitely not be fully backwards compatible either.
This is not a major issue imo, because there are very few legacy systems that support qcML. Probably OpenMS is the only such system.

Are there blocking issues that require maintaining qcML support in OpenMS, rather than switching to mzQC? mzQC is easier to write and read and more powerful to store data, so why stick with qcML as only tool that supports it?

from mzqc.

Axel is working on that in OpenMS already, no? But if need be, we could create a dedicated legacy qcML branch, with the old stuffs, I suppose.

from mzqc.

If we are the only software that's going to have to worry about backwards compatibility of reading the old files then I can just make a note in our code that uses the old CVs.

from mzqc.