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

High memory consumption #6

Open
MickShen7558 opened this issue Apr 26, 2024 · 1 comment
Open

High memory consumption #6

MickShen7558 opened this issue Apr 26, 2024 · 1 comment

Comments

@MickShen7558
Copy link

Hi,

Thank you for the work and the code!

When I tried to run the DiLiGenT-MV benchmark objects, it seems that the final saving requires very large memory:
129deddcfea7e2e8140b56f12d5c1c2

So is there a way to sacrifice the performance by a little bit and get the result?

@xucao-42
Copy link
Collaborator

xucao-42 commented May 2, 2024

Have you installed pyembree library? This step is to find the ray-mesh intersection for geometry evaluation.

Or you can bypass this step by setting val.eval_metric_freq as a larger number than train.end_iter in the configure file so that the evaluation will not be performed. To still extract the mesh, you can set val.val_mesh_freq as 5000, for example, so that a mesh will be extracted for every 5000 step.

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