Tashrif Billah

Same error @billlyzhaoyh , didn't updating conda like I suggested help?

> Maybe MRIQC is not expanding the user shortcuts (~/) from some paths? And it is expanding for participant level? Tried again with expanded paths, didn't help.

While trying to find a way around, the following seems to perform group level analysis: > mriqc ~/INTRuST_BIDS_tb571/ ~/mriqc-out/ participant ```bash 2020-03-24 22:54:56,030 mriqc:IMPORTANT Running MRIQC version 0.15.2rc1+36.gf6c7066: * BIDS...

> However, the workaround mentioned by @tashrifbillah does not seem to work for me, the analysis runs, but is set to participant only (as I would expect from the command...

Again, for what it's worth, my command runs on a bare-metal installation, not through docker container.

The command worked. I would vote for keeping it otherwise how else users would be able to see errors? We can keep this instruction somewhere so the user knows how...

Okay, it looks like it isn't even starting properly ... dying right after connecting.

> Can you check if you can launch Slicer successfully on that system It does.  > running Slicer on a headless system. I know about compatibility mode we discussed...

* `grx04.research.partners.org`-- a CentOS 7 node through NoMachine * module load libGLU/9.0.0-foss-2018b * https://jupyterhub.partners.org

@pieper if you please hold, I am looking at `~/.local/share/jupyter/kernels/slicer-4.11/kernel.json` and might have found the problem.