We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, how to adjust the number of rays in each step of the rendering phase? I saw the argument ray just used in training.
ray
The text was updated successfully, but these errors were encountered:
In rendering parse, function evaluation and render_video are accepting a number of rays.
evaluation
render_video
However, to predict the WebGL. we haven't support for a number of rays. You can simply -no_webgl to avoid the crash.
-no_webgl
But if you really want WebGL.
These following lines are split mpi into 2 pieces. You can change the bigy into more pieces to fit your memory.
bigy
nex-code/train.py
Lines 451 to 453 in eeff38c
Sorry, something went wrong.
I got it. Thanks a lot!
No branches or pull requests
Hi, how to adjust the number of rays in each step of the rendering phase? I saw the argument
ray
just used in training.The text was updated successfully, but these errors were encountered: