Update README.md
Browse files
README.md
CHANGED
@@ -21,7 +21,9 @@ snapshot_download(
|
|
21 |
```
|
22 |
|
23 |
## Images
|
24 |
-
|
|
|
|
|
25 |
|
26 |
## Databases
|
27 |
Unless specified below, all databases `.db` files are produced with
|
@@ -30,11 +32,8 @@ colmap feature_extractor --ImageReader.single_camera 1 --ImageReader.camera_mode
|
|
30 |
colmap exhaustive_matcher --database_path {db_fname}
|
31 |
```
|
32 |
|
33 |
-
For nerf-osr (i.e. those with prefix `nosr_`), `dploy_house4`, urbanscene (`urbn_`), eyeful tower (`eft_`),
|
34 |
-
we
|
35 |
-
|
36 |
-
For eth3d MVS (`eth3d_dslr_`), we populate the databases with author provided ground truth camera intrinsics.
|
37 |
-
This is to keep the eval protocol consistent with Glomap. see [issue 96](https://github.com/colmap/glomap/issues/96).
|
38 |
|
39 |
|
40 |
## Ground truths
|
|
|
21 |
```
|
22 |
|
23 |
## Images
|
24 |
+
* MipNeRF360, Tanks and Temples, NeRF-OSR, DroneDeploy, ZipNeRF and Mill-19 store the images for a scene in the same directory. All the images are used for running SfM.
|
25 |
+
* For Eyeful Tower, images are stored in different subdirectories for each scene. We extract the image paths from the provided `cameras.json`, which contains the GT poses for each image. The subdirectory structure is preserved.
|
26 |
+
* Urbanscene3D also stores images in different subdirectories. We extract the image paths from the refined GT provided [here](https://github.com/cmusatyalab/mega-nerf?tab=readme-ov-file#urbanscene-3d) by [MegaNeRF](https://github.com/cmusatyalab/mega-nerf).
|
27 |
|
28 |
## Databases
|
29 |
Unless specified below, all databases `.db` files are produced with
|
|
|
32 |
colmap exhaustive_matcher --database_path {db_fname}
|
33 |
```
|
34 |
|
35 |
+
* For nerf-osr (i.e. those with prefix `nosr_`), `dploy_house4`, urbanscene (`urbn_`), eyeful tower (`eft_`), we use `--ImageReader.single_camera 0`.
|
36 |
+
* For eth3d MVS (`eth3d_dslr_`), we populate the databases with author provided ground truth camera intrinsics. This is to keep the eval protocol consistent with Glomap. see [issue 96](https://github.com/colmap/glomap/issues/96).
|
|
|
|
|
|
|
37 |
|
38 |
|
39 |
## Ground truths
|