tink/nerfstudio
4
0 Fork 0
mirror of https://github.com/nerfstudio-project/nerfstudio.git synced 2026-11-14 11:54:01 +08:00
Code Activity

chore: remove redundant words in comment (#3544)

Browse Source 
* chore: remove redundant words in comment

Signed-off-by: clonefetch <c0217@outlook.com>

* small typo change

---------

Signed-off-by: clonefetch <c0217@outlook.com>
Co-authored-by: Alexander Kristoffersen <alexanator28@icloud.com>
This commit is contained in:
clonefetchandAlexander Kristoffersen authored and GitHub committed 2024-12-22 19:52:11 +00:00
1 parent 555d554008
commit 14f1d4ed62
3 files changed
+3 -3
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/developer_guides/viewer/local_viewer.md
+1 -1
View File
@@ -1,6 +1,6 @@
# (Legacy Viewer) Local Server
**Note:** this doc only applies to the legacy version of the viewer, which was the default in in Nerfstudio versions `<=0.3.4`. It was deprecated starting Nerfstudio version `1.0.0`, where it needs to be opted into via the `--vis viewer_legacy` argument.
**Note:** this doc only applies to the legacy version of the viewer, which was the default in Nerfstudio versions `<=0.3.4`. It was deprecated starting Nerfstudio version `1.0.0`, where it needs to be opted into via the `--vis viewer_legacy` argument.
---
nerfstudio/data/utils/pixel_sampling_utils.py
+1 -1
View File
@@ -23,7 +23,7 @@ from torch import Tensor
def dilate(tensor: Float[Tensor, "bs 1 H W"], kernel_size=3) -> Float[Tensor, "bs 1 H W"]:
"""Dilate a tensor with 0s and 1s. 0s will be be expanded based on the kernel size.
"""Dilate a tensor with 0s and 1s. 0s will be expanded based on the kernel size.
Args:
kernel_size: Size of the pooling region. Dilates/contracts 1 pixel if kernel_size is 3.
nerfstudio/utils/tensor_dataclass.py
+1 -1
View File
@@ -280,7 +280,7 @@ class TensorDataclass:
) -> TensorDataclassT:
"""Applies a function to all fields of the tensor dataclass.
TODO: Someone needs to make a high level design choice for whether not not we want this
TODO: Someone needs to make a high level design choice for whether or not we want this
to apply the function to any fields in arbitray superclasses. This is an edge case until we
upgrade to python 3.10 and dataclasses can actually be subclassed with vanilla python and no
janking, but if people try to jank some subclasses that are grandchildren of TensorDataclass