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.

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

Bep018 #828

Merged
merged 20 commits into from
Mar 10, 2020
Merged

Bep018 #828

merged 20 commits into from
Mar 10, 2020

Conversation

rwblair
Copy link
Member

@rwblair rwblair commented Aug 27, 2019

- [ ] Add valid genetic_info.json to an example dataset.
Added valid genetic_info.json else where in tests.

@codecov
Copy link

codecov bot commented Jan 15, 2020

Codecov Report

❗ No coverage uploaded for pull request base (master@1fa5827). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##             master     #828   +/-   ##
=========================================
  Coverage          ?   86.69%           
=========================================
  Files             ?       75           
  Lines             ?     2203           
  Branches          ?      454           
=========================================
  Hits              ?     1910           
  Misses            ?      250           
  Partials          ?       43

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1fa5827...b88d1ac. Read the comment docs.

@rwblair rwblair changed the title [WIP] Bep018 Bep018 Jan 15, 2020
Copy link
Member

@sappelhoff sappelhoff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @rwblair - I have given this a coarse look (not comparing directly with the specification draft yet).

@CPernet could you also have a look at the code and check if some keywords are missing or optional/mandatory keywords are treated appropriately? No specific JS skills needed here, it's very readable.

Another point: Have you tested this on an example dataset @rwblair? If yes, which one? Can we edit a dataset on https://github.com/bids-standard/bids-examples to include genetics information?

@CPernet
Copy link
Contributor

CPernet commented Jan 16, 2020

I'm finishing a UK biobank example, will push it soon as a PR = we can test the validator

@rwblair
Copy link
Member Author

rwblair commented Jan 22, 2020

New specification PR bids-standard/bids-specification/pull/395 for discussion.

@rwblair
Copy link
Member Author

rwblair commented Mar 3, 2020

@sappelhoff @CPernet has made an example dataset that can be found here:
https://github.com/CPernet/bids-examples/

I have a PR from my branch of his examples back to his master that passes using this validator:
https://github.com/rwblair/bids-examples/tree/cpernet

I figure we merge validator first and then examples? The validator uses the examples in its tests and the examples use the validators in its tests. One of them has to be merged first, the examples will never pass against a specified version of the validator without the necessary changes to the validator being merged.

@effigies
Copy link
Collaborator

effigies commented Mar 4, 2020

@rwblair Let's merge the validator first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants