Skip to content
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.

Sign up for GitHub

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

Jump to bottom

JAMS Sanity checks and logging #93

Open
jonnybluesman opened this issue Nov 2, 2022 · 0 comments
Open

JAMS Sanity checks and logging #93

jonnybluesman opened this issue Nov 2, 2022 · 0 comments
Assignees
@jonnybluesman
Labels
feature A new feature to implement high-priority jams-x Feature to be move to JAMS-X

Comments

@jonnybluesman
Copy link
Member

jonnybluesman commented Nov 2, 2022 •
edited
Loading

As part of a family of tools to validate ChoCo before exporting, we should validate each namespace and generate 2 outputs: (i) a logging file with all the violations for each JAMS (per namespace); and (ii) a coverage metric to tell us the amount of fully legal JAMS / namespaces.

We already have extensive validation support in jams_test.
@jonnybluesman jonnybluesman added feature A new feature to implement high-priority labels Nov 2, 2022
@jonnybluesman jonnybluesman self-assigned this Nov 2, 2022
@jonnybluesman jonnybluesman added the jams-x Feature to be move to JAMS-X label Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonnybluesman jonnybluesman

Labels
feature A new feature to implement high-priority jams-x Feature to be move to JAMS-X
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonnybluesman