fmriprep-docker : The term ‘fmriprep-docker’ is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
PS C:\Users\axl666> fmriprep-docker
fmriprep-docker : The term ‘fmriprep-docker’ is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
Hi Stevan,
Initially I have installed python and docker desktop and then after
I went t the site Docker Hub
and just copied this command in powershell
docker pull nipreps/fmriprep
So that is only installing the Docker container. fmriprep-docker is a wrapper function, which means it is a way to conveniently call fmriprep. However, fmriprep-docker needs to be installed, which you can do using pip install fmriprep-docker
fmriprep-docker : The term ‘fmriprep-docker’ is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
PS C:\Users\axl666> fmriprep-docker
fmriprep-docker : The term ‘fmriprep-docker’ is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1
I’m guessing python packages are not added to your path. Are you using python through Anaconda? Either way, if you have the docker container on your machine, you can alternatively call fmriprep through docker run (see below for an example)
I am used to dealing with python as part of an Anaconda installation, so I don’t know where the pip packages would be for a stand-alone python installation
Try putting quotes around “.\Nifti” “.\Derivatives” “.\license.txt”. Also I forgot the participant label argument but you can add that at the end. I am not a windows powershell user, but I imagine this might be due to how paths are coded differently in Windows vs Linux/Mac ("/" vs “\”).