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

adjust the number of rays #39

Open
zhywanna opened this issue Nov 2, 2021 · 2 comments
Open

adjust the number of rays #39

zhywanna opened this issue Nov 2, 2021 · 2 comments

Comments

@zhywanna
Copy link

zhywanna commented Nov 2, 2021

Hi, how to adjust the number of rays in each step of the rendering phase? I saw the argument ray just used in training.
image

@pureexe
Copy link
Contributor

pureexe commented Nov 4, 2021

In rendering parse, function evaluation and render_video are accepting a number of rays.

However, to predict the WebGL. we haven't support for a number of rays.
You can simply -no_webgl to avoid the crash.

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.

nex-code/train.py

Lines 451 to 453 in eeff38c

if sfm.offset > 270:
out = [model.seq1(bigy) for bigy in [bigcoords[:, :int(sh/2)], bigcoords[:, int(sh/2):]]]
out = pt.cat(out, 1)

@zhywanna
Copy link
Author

zhywanna commented Nov 4, 2021

I got it. Thanks a lot!

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