-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automated validation #9
Comments
Very good idea. Based on the previously implemented PR #173 in
|
There has been some progress on this. The suggestions from @Hao-Chalmers are already implemented as workflow with GitHub Actions in the |
As mentioned in #16, the SBML fle should be tested with MEMOTE. |
As mentioned in #13, the SBML should contain taxonomy name, taxonomy ID, and reference genome. |
From the continued discussion in #16: perhaps one can devise a test to check the compatibility of |
I opened a separate discussion on the topic of identifiers and semantic overloading at #27. |
For a clearer separation of concerns, the automated validation work has been promoted to a separate repository called standard-GEM-validation. The action points from this issue have been migrated to the new repository as distinct issues. |
This repository contains a branch (for)
automated-validation
. In short, the aim of that branch is to use GitHub Actions to validate all public repositories that followstandard-GEM
and output a machine-readable file with the results, eg which version of the GEM follows which standard,MEMOTE
results,cobrapy
testing.Documentation of the most up-to-date implementation is on the wiki.
Ideas and feedback are welcome!
edit: This could be implemented with eg Toil.
The text was updated successfully, but these errors were encountered: