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

Generate a benchmark dataset for integration tests #29

Closed
oesteban opened this issue Nov 11, 2020 · 6 comments
Closed

Generate a benchmark dataset for integration tests #29

oesteban opened this issue Nov 11, 2020 · 6 comments

Comments

@oesteban
Copy link

I'd suggest pulling out the MELODIC node of fMRIPrep as run by CircleCI on ds005 (because this dataset is heavily downsampled, so the computational burden is not terrible).

fMRIPrep should also generate the necessary TPMs in native space.

@vinferrer
Copy link
Collaborator

Hi oscar, could you explain a little bit more? I understand that ds005 is lighter than the nilearn data we are using. Where can we find ds005?

@vinferrer
Copy link
Collaborator

This one:

wget --retry-connrefused --waitretry=5 --read-timeout=20 --timeout=15 -t 0 -q \
   -O ds005_downsampled.tar.gz "https://files.osf.io/v1/resources/fvuh8/providers/osfstorage/57f32a429ad5a101f977eb75"

@vinferrer
Copy link
Collaborator

I don't see any motion parameters, do we have to calculate them apart? Also i see no reference image, so do you use the mean of the image or something similar to get the motion parameters? Probably it would be better to run them once and have a separate osf tar file with the motion parameters already there.

@oesteban
Copy link
Author

That's the "BIDS-raw" version of the dataset. We don't store any preprocessed copy.

But now that I think about it, using a downsampled dataset might not help us make the CI load lighter by a lot - but will definitely make it difficult to check the results when we move from standard space to native.

Sorry for the initial suggestions of ds005, but the nilearn data you guys were using could be just fine!

@vinferrer
Copy link
Collaborator

Should we close this issue then?

@oesteban
Copy link
Author

oesteban commented Nov 12, 2020

No, but prepare the dataset based on the nilearn data you were already using.

I realize you're right. Sorry I'm really slow today.

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

No branches or pull requests

2 participants