-
Notifications
You must be signed in to change notification settings - Fork 157
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
How to run "ciftify usage example" in a docker #81
Comments
And if I may could you specify which version of msm should be run with ciftify ? Do you have an idea about this bug ? |
Thanks for your interest! You highlight the fact that I need to update the documentation very soon to reflect some upgrades/changes that were implemented in the last two weeks. A major addition is that this project now contains two Docker files
Some more details on these use cases are in this poster https://docs.google.com/presentation/d/1QFrfzw7JMfHzDhuuOgATdrlYcBWK12sMaLcMGghTJ-s/edit?usp=sharing. More instructrions from running the container are in this repo https://github.com/edickie/bids-on-scinet. The examples in the repo work from singularity image built from the dockerhub image. To answer your second question. No, the version of MSM in FSL is not the one currently packaged with FSL. There's some odd politics going on there. And Matt Glasser is strongly insisting on the github one. You can download the complied binary's directly from the releases section of their github though (https://github.com/ecr05/MSM_HOCR/releases). (or just use tigrlab/fmriprep_cifitify) |
All right, it is so much clearer now. It's so kind to reply, thanks a lot. |
First of all, thank a lot to share your work.
I wish to run ciftify in a docker so I cloned from github the project ciftify, build the Dockerfile and ran it....
But I do not understand how that can work ....because It seems to me that the dockerfile open only a jupyter notebook and thats it ...
I think I have missed something....
Could you please say a word on that ?
The text was updated successfully, but these errors were encountered: