Closed araikes closed 1 year ago
Yes, we found that bug on the release and it is fixed, but we are currently fixing building the new container that will replace that version. You could build the container from the Docker file provide in master. That branch is already working. We are sorry for the inconvenience.
Ah, sounds good. Glad it was a known issue and not a new problem.
Thanks
Apologies @rcruces or @PeerHerholz, one other question...
In master
the Dockerfile still has FSL at v. 6.0.0 vs. 6.0.3 as is up on DockerHub. Are the only updates needed there to update to change relevant paths (both from FSL and for the install path) to 6.0.3?
@rcruces and @PeerHerholz,
Curious if 0.1.5 is going to get a build on Dockerhub? I'd build it myself but the Dockerfile in master
hasn't been updated in 2 years, so I'm assuming it to be out of date.
We just updated some features on the new release, and we were having some difficulties while building the docker. But we will updated and upload a new container possibly by next week. We'll keep you post.
This feature was fixed on the v0.1.5
and the container usage was deeply test for our latest release v0.2.0
please have a look at it.
https://github.com/MICA-MNI/micapipe/releases/tag/v0.2.0
I pulled the current version of micapipe (v. 0.1.4) today in a Singularity image for use on my HPC. To check everything running, I was going to run single participant in very stepwise progression to make sure I understood the outputs at each step. My intention is to reuse my already run Freesurfer 7.3.1 data but is somewhat optional. This is my call:
This is the output when I do so:
It generates the relevant file tree as expected but fails after creating the folders. The same command works for my v0.1.2 singularity image.