Closed biodavidjm closed 1 year ago
This is because of our current efforts to port the QC CV terms to the PSI-MS-CV, our CV here is indeed in a undefined state with some dangling terms. Do you get similar warnings when loading the PSI-MS-CV? Are there CV terms that should get priority for porting from the QC CV to PSI-MS-CV for your R development work?
We have now mostly finished porting our CV terms to the PSI-MS-CV, which should not have these issues.
I get the following warning in R when getting the ontology from
qc-cv.obo