The current version of mesh2hrtf.manage_numcalc() caused an issue for me when running on a folder containing multiple Mesh2HRTF projects. Wen starting to compute results for the second project, the first step is to estimate the available RAM. This estimate was was very low, because NumCalc instances from the first project were still running. In fact the RAM estimate was lower than the RAM required for the second project and manage_numcalc stopped with the error not sufficient free RAM for this simulation project.
The suggested fix is to only estimate the available RAM before running the first project but not at the start of the project. It resolved my issue and did not slow down anything.
@SDX-LV does there speak anything against merging this?
The current version of
mesh2hrtf.manage_numcalc()caused an issue for me when running on a folder containing multiple Mesh2HRTF projects. Wen starting to compute results for the second project, the first step is to estimate the available RAM. This estimate was was very low, because NumCalc instances from the first project were still running. In fact the RAM estimate was lower than the RAM required for the second project andmanage_numcalcstopped with the error not sufficient free RAM for this simulation project.The suggested fix is to only estimate the available RAM before running the first project but not at the start of the project. It resolved my issue and did not slow down anything.
@SDX-LV does there speak anything against merging this?