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
3dSkullStrip errors out inside screen #651
Comments
Hi @stjep, the latest mriqc update was supposed to address this. It seems that |
@oesteban, my bad, my vm instance did not have Seems to be running fine now so I'm closing this. Will re-open if the bug re-appears, but looks good so far. |
I'm getting this with 0.9.9 on OpenNeuro: https://openneuro.org/datasets/ds000007/versions/00001?app=MRIQC&version=46 Surprisingly it only happened for one subject out of many. I would suggest switching to including (in the Docker image) a version of AFNI that does not depend on display. |
I talked to one of the afni developer's about an xvfb issue like this. For shared machines where you don't have access to docker this problem is solved nicely in afni's @chaufeur_afni (tcsh), have a look with:
Specifically the following can be used to keep trying different displays until it succeeds :
xvfb-run -a does this but seems to cause issues with image opacity. |
I'm running into this more often on OpenNeuro. Would be great to ship with version of 3dskullstrip that does not require display. |
I also wonder why it started happening now - was AFNI updated? |
Run into this again on OpenNeuro. |
Running the latest mriqc (0.9.9) within Docker, I get the following error if it is run inside of
screen
, which doesn't forward X11. Running it outside ofscreen
does not produce the error, but also doesn't seem to need X11 forwarding. The crash file is:The text was updated successfully, but these errors were encountered: