-
Notifications
You must be signed in to change notification settings - Fork 22
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
numpy.core._exceptions._ArrayMemoryError #22
Comments
The function mesh.split costs much memory. Please comment it out and directly output |
Thank you, it has been a great help to me! |
May I ask what the specific results are represented by the output of 'vis/vis_201_d2s. ply' and 'vis/vis_201_s2d_ply' in 'eval. py'? How should I obtain valid information from them? |
Hi! 'vis/vis_201_d2s. ply' and 'vis/vis_201_s2d_ply' represent the closest distances between output and ground truth. Red parts indicate large error. And please check that you have reinstall the package with the right version. And you could print the rendered images during training to check training process. |
I retrieved the latest version of the code and conducted the training process, but unfortunately, the grid results I extracted were not ideal and differed significantly from the results provided on the project page. |
Hello. When I ran the evaluation code, the following errors occurred: numpy.core._exceptions._ArrayMemoryError:Unable to allocate 19.1MiB for an array with shape (1537052,) and data type [('vertex_indices', [('f0', 'u1'), ('f1', '<u4', (3, ))])]. I don't understand why it occupies up to 64GB of memory. I would like to know if you have encountered such a problem before.
The text was updated successfully, but these errors were encountered: