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! The repo C51 really helps a lot!
However, I have a question. In line 226 and 227: l = b.floor().clamp(0, args.n_atoms - 1) u = b.ceil().clamp(0, args.n_atoms - 1)
l = b.floor().clamp(0, args.n_atoms - 1)
u = b.ceil().clamp(0, args.n_atoms - 1)
It seems that the clamp() function is redundant? Because t_z is already in v_min and v_max. Why do we still use it here?
clamp()
t_z
v_min
v_max
Looking forward to your reply~ Thanks
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi! The repo C51 really helps a lot!
However, I have a question. In line 226 and 227:
l = b.floor().clamp(0, args.n_atoms - 1)u = b.ceil().clamp(0, args.n_atoms - 1)It seems that the
clamp()function is redundant? Becauset_zis already inv_minandv_max.Why do we still use it here?
Looking forward to your reply~
Thanks
The text was updated successfully, but these errors were encountered: