Converting to CK format #32
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi guys,
If it's of interest, I converted this data to CK format as a part of TETRACOM deliverable.
It will allow us (and the community) to unify access to this data via CK, add/remove/search local entries, visualize them via dashboard, push to cKnowledge.org/repo, etc.
We can also gradually unify and extend meta to ensure reproducibility (we can add it later) ...
You can see dashboard at http://cknowledge.org/repo under "crowd-test OpenGL compilers (beta)"
However, if it's not suitable, feel free to cancel this pull request (or send me a feedback).
Cheers,
Grigori