mirror of
https://github.com/nerfstudio-project/nerfstudio.git
synced 2026-11-22 07:35:26 +08:00
Fix typo (#1231)
* Fix typo COLAMP->COLMAP * Fix more typo Co-authored-by: Matthew Tancik <tancik@berkeley.edu>
This commit is contained in:
1 parent
53c23ba356
commit
408ab709ec
45 files changed
+72
-72
No files matched your search
@@ -34,7 +34,7 @@ class DataManager(nn.Module):
|
||||
"""Returns the next eval image.
|
||||
|
||||
Returns:
|
||||
The image index from the eval datset, the CameraRayBundle, and the RayGT dictionary.
|
||||
The image index from the eval dataset, the CameraRayBundle, and the RayGT dictionary.
|
||||
"""
|
||||
```
|
||||
|
||||
|
||||
@@ -103,7 +103,7 @@ dataparser_outputs = dataparser.get_dataparser_outputs(split="train")
|
||||
input_dataset = InputDataset(dataparser_outputs)
|
||||
```
|
||||
|
||||
You can also pull out information from the DataParserOutputs for other DataMangager componenets, such as the RayGenerator. The RayGenerator generates RayBundle objects from camera and pixel indices.
|
||||
You can also pull out information from the DataParserOutputs for other DataMangager components, such as the RayGenerator. The RayGenerator generates RayBundle objects from camera and pixel indices.
|
||||
|
||||
```python
|
||||
ray_generator = RayGenerator(dataparser_outputs.cameras)
|
||||
|
||||
@@ -56,7 +56,7 @@ class Field(nn.Module):
|
||||
|
||||
The forward function is the main function you'll use, which takes in RaySamples returns quantities for each sample. You'll notice that the get_density function is called for every field, followed by the get_outputs function.
|
||||
|
||||
The get_outputs function is what you need to implement to return custom data. For example, check out of SemanticNerfField where we rely on different FieldHeads to produce correct dimensional outputs for typical quantiites. Our implemented FieldHeads have the following FieldHeadNames names.
|
||||
The get_outputs function is what you need to implement to return custom data. For example, check out of SemanticNerfField where we rely on different FieldHeads to produce correct dimensional outputs for typical quantities. Our implemented FieldHeads have the following FieldHeadNames names.
|
||||
|
||||
```python
|
||||
class FieldHeadNames(Enum):
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Model components
|
||||
|
||||
It can be difficult getting started with NeRFs. The reserach field is still quite new and most of the key nuggets are burried in academic papers. For this reason, we have consoladated many of the key concepts into a series of guides.
|
||||
It can be difficult getting started with NeRFs. The research field is still quite new and most of the key nuggets are buried in academic papers. For this reason, we have consolidated many of the key concepts into a series of guides.
|
||||
|
||||
```{toctree}
|
||||
:maxdepth: 1
|
||||
|
||||
@@ -145,7 +145,7 @@ A LiDAR enabled iPhone or iPad is necessary.
|
||||
:alt: polycam settings
|
||||
```
|
||||
|
||||
Devoloper settings must be enabled in Polycam. To do this, navigate to the settings screen and select `Developer mode`. Note that this will only apply for future captures, you will not be able to process existing captures with nerfstudio.
|
||||
Developer settings must be enabled in Polycam. To do this, navigate to the settings screen and select `Developer mode`. Note that this will only apply for future captures, you will not be able to process existing captures with nerfstudio.
|
||||
|
||||
### Process data
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ ns-export pointcloud --help
|
||||
|
||||
## Other exporting methods
|
||||
|
||||
Run the folowing command to see other export methods that may exist.
|
||||
Run the following command to see other export methods that may exist.
|
||||
|
||||
```python
|
||||
ns-export --help
|
||||
|
||||
@@ -93,7 +93,7 @@ sphinx-autobuild docs docs/_build/html
|
||||
|
||||
### Adding notebooks
|
||||
|
||||
We support jupyter notbooks in our documentation. To improve the readability, the following custom tags can be added to the top of each code cell to hide or collapse the code.
|
||||
We support jupyter notebooks in our documentation. To improve the readability, the following custom tags can be added to the top of each code cell to hide or collapse the code.
|
||||
|
||||
| Tag | Effect |
|
||||
| ------------- | ---------------------------------------------------- |
|
||||
|
||||
Reference in new issue
Block a user