Skip to content

Bad allocation data #2358

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

Open
MLopezPon opened this issue Mar 6, 2025 · 5 comments
Open

Bad allocation data #2358

MLopezPon opened this issue Mar 6, 2025 · 5 comments

Comments

@MLopezPon
Copy link

Good morning,

I am trying to run an optimization with different domain (ex: vertebra L4-L5).
When running the optimisation step I have a "bad allocation" error stoping the process.
It appears rather when I try with a "bigger cohort" (approx. 100 cases) or more domains (L1 to S1).

To minimize the ressources I first try to run a first groom with the remesh option, take these vertebrea_groomed.vtk as an input of the new model.
This doesn't solve the issue.

Thanks for your help.

Image

@akenmorris
Copy link
Contributor

This means that it has run out of memory. How much RAM does the system have?

You might also try the development version of ShapeWorks where some memory usage has been reduced.

https://github.com/SCIInstitute/ShapeWorks/releases/tag/dev-windows

@MLopezPon
Copy link
Author

RAM of my present system is 31.6GB.
I'll try the dev version and keep you updated

@akenmorris
Copy link
Contributor

There was a very inefficient data structure that scaled poorly with the number of triangles in your groomed meshes. It's been fixed in the development version, or you can use re-meshing in the groom options to reduce the triangle count. That could be it.

@MLopezPon
Copy link
Author

The remeshing groom option was already used in the models that has the "bad allocation" error.
The Development version of the software helps thanks.
I also made a swap for the memory but it is still challenging for the heavier projects (I have some 90GB committed for the full lumbar projects which is still not sufficient).

Last question on this: is a "remesh" option on the grooming phase relevant when the input of the model is an already remeshed groomed? (I took my stls, made a remesh grooming and have the vertebra_groomed.vtk became the input of the new model)

@akenmorris
Copy link
Contributor

Last question on this: is a "remesh" option on the grooming phase relevant when the input of the model is an already remeshed groomed? (I took my stls, made a remesh grooming and have the vertebra_groomed.vtk became the input of the new model)

You can remesh again, if that's what you mean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants