Repository navigation
Auto3Dseg Overly Slow & Raises Error #1713
Replies: 3 comments 5 replies
|
Hi @dongyang0122, could you please help take a look at this issue, thanks. |
Hi @bilalcodehub, I'd suggest you first try the SegResNet architecture.
Here is more information: https://github.com/lassoan/SlicerMONAIAuto3DSeg/?tab=readme-ov-file#how-to-train-a-new-model-from-scratch |
|
Hi all, Just wanted to add to the thread. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Dear All,
I am encountering an issue where Auto3Dseg appears to be running very slow. I think it is not utilising the GPU on our server. I've been working with the introductory tutorials code using some
.mhafiles for multi-organ segmentation, and while everything else functions correctly, I run into problems when executing the following segment:This results in an error after a prolonged period of running. Notably, I am using PyTorch version
2.3.0+cu118andtorch.cuda.is_available()returnsTrue. However, thenvidia-smicommand does not show any GPU activity despite the system having 2 NVIDIA RTX 2090 Ti GPUs.Could anyone provide insights or suggestions on how to resolve this issue?
Thank you for your assistance.
Best regards,
Bilal
All reactions