-
Notifications
You must be signed in to change notification settings - Fork 1
implement CI check_data_consistency #27
base: master
Are you sure you want to change the base?
Conversation
To fit <100MB github requirement
derivatives/labels folder and csfseg-manual masks
Fix wrong acquisition date in participants.tsv
Implement CI testing for BIDS
Add manually corrected dwi SC segmentations.
Update dwi SC seg for sub-vuiisAchieva06
Add manually corrected dwi SC segmentations
- remove sapienza04 gmseg - correct gmseg for sapienza01
manual correction of t1w and t2w images
* fix defaced image * change permissions * add fslPrisma dataset * rename sapienza to fslAchieva * deface images * fix defacing dresden02_T2w * remove other defaced images * rename test * fix rename
Output from current master:
|
@jcohenadad This PR is ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please do not merge-- we need to wait for @kousu to tell us what to do
Yes. I won't, I'll wait for your approval. |
Sorry! You're going to have to remake this over in the remade https://github.com/spine-generic/data-multi-subject. And you'll have to add a I also would caution about running that on every CI run because that means downloading 10G to travis every time. That is going to make CI slow. Travis supports caching specific dirs: https://docs.travis-ci.com/user/caching/ but they have a warning that caching doesn't do much unless you're caching processing steps -- because each VM needs to download the data fresh each time; still it might be worth experimenting at least for an hour or two with. What if we only ran the validator in the nightly cronjob? |
Answered my own question: https://travis-ci.com/github/spine-generic/data-multi-subject-2/builds/179667411. Hard yes:
|
Fixes spine-generic/data-multi-subject#24