-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update FastSurfer Docker containers #72
Conversation
Still need to test whether this runs successfully. |
did you have any luck getting the surface reconstruction to run? |
…ideas/fastsurfer:cpu-xnat` See also HealthBioscienceIDEAS/MedICSS-Project-Repro-Pipelines#24
3ab544c
to
e486995
Compare
The `container_service_client` role uploads only files that end in `*-command.json` (https://github.com/UCL-MIRSG/xnat-aws/blob/e4869957fc4ffe567b465978faea3619ebcbfcbf/configure/playbooks/roles/container_service_client/tasks/main.yml#L69-L70).
Prevents creation of container on `t3.large` otherwise.
Re-running it now an a different image. Seems to be running for longer already than previously, so 🤞 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had to change the limit-cpu
value to 2 to get the containers to run on the current setup. We might consider using one of the Compute-optimized EC2 instances for the Container Service though to reduce runtimes. Or completely switch to GPU (#51).
The FastSurfer analysis runs successfully now but there is still an issue with the output files. For some reason, XNAT fails to upload them (see screenshot), though they are present in the correct path (manually confirmed by I'm going to merge this now but I'll create another issue for this problem: #74. |
t3.large
for the Container Service instance to handle FastSurferFixes #70