-
Notifications
You must be signed in to change notification settings - Fork 532
FIX: Permit relative path for concatenated_file input to Concatenate() #1411
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
Conversation
9642522
to
7052512
Compare
Seeing FreeSurfer isn't installed in Circle, so tests can't run. Is this something that should change? |
freesurfer is a nasty download 4.6GB. perhaps we can create a separate minimal freesurfer just for recon-all. more recently i think i've seen an internal docker version. let me look into that. in the meantime, let's not run this on circle. it would also take too long to run. @dgellis90 - since you are running this on your cluster, perhaps you can keep us posted there. |
I'm currently migrating CircleCI tests to docker containers in some other projects. I think this could be the solution to the problem of downloading so large files. |
Freesurfer inside a docker image vs outside of it is still a 4GB download. On Wed, Mar 30, 2016 at 2:48 PM, Coveralls notifications@github.com wrote:
|
@chrisfilo is correct - that's why we need to restrict it to what recon-all needs - which is only about 350MB - but there is indeed an effort to again make freesurfer available through neurodebian - which may become the smallest distribution for the binaries. |
I've tried to slim down FreeSurfer in this NeuroVault docker image On Wed, Mar 30, 2016 at 3:27 PM, Satrajit Ghosh notifications@github.com
|
Okay. So, as far as this PR goes, I can report that |
TraitError occurred in workflow, not when run directly.
The example as given in the docs will fail to run, raising:
While the
ConcatenateInputSpec
seems happy with a relative path, it seemsConcatenateOutputSpec
needs an absolute path, so simply passing it through is insufficient. This change prepends the working directory. I've tested this on my own pipeline, and it resolves an error like the one above.