Skip to content
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

NumCalc runtime error #130

Open
leverscut1 opened this issue May 22, 2024 · 9 comments
Open

NumCalc runtime error #130

leverscut1 opened this issue May 22, 2024 · 9 comments

Comments

@leverscut1
Copy link

I'm encountering a runtime error when calculating using NumCalc script. The error message is as follows:
"... waiting for resources and checking every second (May 22 2024, 13:02:07)
1 NumCalc instances running at 3.80% CPU load
247.32 GB RAM available (8.59 GB used), 19.61 GB required

terminate called after throwing an instance of 'std::bad_array_new_length'
what(): std::bad_array_new_length

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."

Any insights or recommendations to resolve this issue would be greatly appreciated.

@f-brinkmann
Copy link
Contributor

I don't think I encountered that before. @schaastrommla do you have an idea?

@schaastrommla
Copy link
Contributor

Hard to tell, I seems NumCalc wants to allocate some memory with zero or a negative value, but I have no idea where. Can be anything from a missing parameter in the inputfile to a programming error or some integer value getting too big. What is the background of the problem? A "simple" calculation, or a restart with just a different evaluation grid, or just a memory check? How many elements, how many clusters?

@leverscut1
Copy link
Author

This problem may be caused by too many faces in the calculated model, because the AEL of the input .stl model is about 1mm, and there are about 380,000 meshes. This problem will not occur when calculating a model with an AEL of 2mm, but I hope can fix this problem

@f-brinkmann
Copy link
Contributor

Definately worth a try. If your on windows, Meshmixer is an easy way to remesh to a constant edge length. If its a head, you could also use the grading tools in https://github.com/Any2HRTF/Mesh2HRTF/tree/master/mesh2hrtf/Mesh2Input/Meshes

@leverscut1
Copy link
Author

Thank you very much for your suggestion. However, I have tried several remeshing methods to obtain a uniform mesh with AEL=1mm, but the error still occurs. I guess it might not be an issue with the mesh structure.

@f-brinkmann
Copy link
Contributor

Did you try to remesh the ears with 1 mm and everything else with approx. 2 mm?

@leverscut1
Copy link
Author

Did you try to remesh the ears with 1 mm and everything else with approx. 2 mm?
This approach is feasible and completes the calculation, but I still wish to try running the entire head with an AEL of 1mm to evaluate its accuracy. I also have a significant amount of memory (about 250GB). However, a bug is preventing this from being accomplished.

@f-brinkmann
Copy link
Contributor

I understand and agree that it would be nice to know whats happening there. I think @schaastrommla is currently on vacation. Maybe he could have a look if you upload the project somewhere.

Regarding the accuracy, I think you are very fine with the 1 mm for the ears - at least according to what we know from literature...

@leverscut1
Copy link
Author

Understood.
Thanks for answering these questions, and best regards.

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

3 participants