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
Bug Description
When using ns-viewer in Google Colab, Viser fails to establish a connection to the visualized training instance.
I was hoping to solve this issue by setting the --viewer.make-share-url True flag. A shared URL gets printed when using ns-train but not when using ns-viewer.
As a solution, I would appreciate a suggestion on how to access the shared URL of the ns-viewer or a way to resolve the connection issue with Colab's /localhost:7007/.
To Reproduce
Steps to reproduce the behavior:
Have some trained scene available or train a scene using
Expected behavior
After step 3, I would expect the output to be available through the Colab localhost from step 2. While the port can be accessed by ns-viewer (indicated by a Viser instance on that port), it will always remain in the "Connecting..." state.
Additionally, I would expect a shared link to be printed (as is the case when using ns-train) such that a publicly accessible viewer instance can be accessed.
These two errors combined disallow visualizing any pretrained instances which makes nerfstudio practically incompatible with Google Colab.
Screenshots
Viser never leaves the "Connecting..." state.
Additional context
Here is the full console output that is printed when executing ns-viewer:
2024-05-13 05:54:28.780850: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-05-13 05:54:28.780905: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-05-13 05:54:28.782402: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-05-13 05:54:28.790266: I tensorflow/core/platform/cpu_feature_guard.cc:182] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-05-13 05:54:29.959001: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
[05:54:37] Auto image downscale factor of 1
The text was updated successfully, but these errors were encountered:
Bug Description
When using
ns-viewer
in Google Colab, Viser fails to establish a connection to the visualized training instance.I was hoping to solve this issue by setting the
--viewer.make-share-url True
flag. A shared URL gets printed when usingns-train
but not when usingns-viewer
.As a solution, I would appreciate a suggestion on how to access the shared URL of the
ns-viewer
or a way to resolve the connection issue with Colab's/localhost:7007/
.To Reproduce
Steps to reproduce the behavior:
localhost:7007
:config.yaml
to load the viewer. Use!ns-viewer --viewer.make-share-url True --load-config /content/.../config.yml
Expected behavior
After step 3, I would expect the output to be available through the Colab localhost from step 2. While the port can be accessed by
ns-viewer
(indicated by a Viser instance on that port), it will always remain in the "Connecting..." state.Additionally, I would expect a shared link to be printed (as is the case when using
ns-train
) such that a publicly accessible viewer instance can be accessed.These two errors combined disallow visualizing any pretrained instances which makes nerfstudio practically incompatible with Google Colab.
Screenshots
Viser never leaves the "Connecting..." state.
Additional context
Here is the full console output that is printed when executing
ns-viewer
:The text was updated successfully, but these errors were encountered: