-
Notifications
You must be signed in to change notification settings - Fork 8
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
Runtime error trying to run TS1 model #56
Comments
Hi @fedorov, Thanks for your feedback. I've downloaded the sample and performed inference. Here is the result: https://github.com/lassoan/SlicerMONAIAuto3DSeg/assets/11991079/30065149-5775-4b6f-9b20-26ef9c7c5156 I see the volume you're referring to is 512x512x156 with a spacing of 0.7x0.7x2mm - After resampling to 1.5mm, it becomes: 254x 243x208 It took around 25 seconds and 17GB of GPU memory to run. Which spec does your machine have? Can you please try on the CPU to check if it runs on your end? BTW, this is the very first version of the whole-body CT segmentation model on TSV1. I'm working on getting the second version - potentially more accurate :) Thanks! |
Here are the specs
Some other models I tried on that same volume worked without errors. Below is "Whole body segmentation - TS1 quick". I tried on CPU, and it errored as well:
It is not in my critical path - I am just reporting in case this helps with your development. No urgency! |
Thanks again for the feedback, @fedorov. |
CPU has 15 GB. |
For a full resolution model, 15GB total CPU RAM can be really tight. What operating system are you using? How much virtual memory is available? |
If you need anything other than below, let me know what I should run!
|
I tried to run the TS1 model using the extension from Slicer 5.7.0-2024-04-24 r32828 / 4a60ea6 on the CT series from the NLST collection and ran into the error below. Is this expected? What are the RAM requirements for this model?
You can access the same CT series that I used by installing SlicerIDCBrowser extension, and plugging this
1.2.840.113654.2.55.252662084823127974216855931259749568803
into theSeriesInstanceUID
of the downloader section of the UI.The text was updated successfully, but these errors were encountered: