You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for your awesome project! I wanted to discuss the possibility of merging the features you've developed for the NeuS2_TCNN repository into the tiny-cuda-nn repository. The accompanying paper suggests that these features could complement the goals of tiny-cuda-nn and enhance its capabilities.
Considering the well-established testing period and ongoing maintenance of tiny-cuda-nn, merging your features could lead to a more robust and future-proof codebase. This collaboration would avoid duplication of efforts and ensure that your features stay compatible with the latest updates.
I'd appreciate your thoughts on this proposal and whether it aligns with your vision for the projects. Let's discuss the potential benefits and the path forward. Thank you!
The text was updated successfully, but these errors were encountered:
Hi @gerwang, thanks for your consideration and great proposal. It would be really nice if NeuS2_TCNN could be integrated into the tiny-cuda-nn repository. However, I have some concerns:
Our implementation of the backward_backward_input is tailored for the Relu-based MLPs only.
Some codes need to be refined before integration.
We may still need the NeuS2_TCNN for NeuS2 repository since we have modified some APIs.
Hello @19reborn,
Thanks for your awesome project! I wanted to discuss the possibility of merging the features you've developed for the NeuS2_TCNN repository into the tiny-cuda-nn repository. The accompanying paper suggests that these features could complement the goals of tiny-cuda-nn and enhance its capabilities.
Considering the well-established testing period and ongoing maintenance of tiny-cuda-nn, merging your features could lead to a more robust and future-proof codebase. This collaboration would avoid duplication of efforts and ensure that your features stay compatible with the latest updates.
I'd appreciate your thoughts on this proposal and whether it aligns with your vision for the projects. Let's discuss the potential benefits and the path forward. Thank you!
The text was updated successfully, but these errors were encountered: