Understanding 'olsson' dataset

[Padarn]

I'm trying to run gtsfm, but the README seems out of date, the command

python gtsfm/runner/run_scene_optimizer.py --config_name {CONFIG_NAME} --dataset_root {DATASET_ROOT} --image_extension jpg --num_workers {NUM_WORKERS}

can no longer work, as the gtsfm/runner/run_scene_optimizer.py has been removed.

I tried to instead use

gtsfm/runner/run_scene_optimizer_olssonloader.py --config_name {CONFIG_NAME} --dataset_root {DATASET_ROOT} --image_extension jpg --num_workers {NUM_WORKERS}

but I don't fully understand the format of the dataset expected, currently, I get an error

raise ValueError(f"No intrinsics found for index {index}.")

Are there any docs on how the data should be structured in the dataset_root?

(also, related, do intrinsics need to be specified, or can they be inferred?

[ayushbaid]

Thanks for raising this issue. You are right that run_scene_optimizer.py has been removed. Instead of defaulting to the format of Olsson dataset, we will prioritize working on a simple runner where you specify the folder with the images and can run SfM on it.

We will pick up this task as top priority and will provide a solution within a couple of days.

[ayushbaid]

Resolution tracked in #352

[Padarn]

Thanks a lot. Happy to help out if there is some documentation on the format I can follow.

[johnwlambert]

Hi @Padarn, thanks for your interest in our work. Suppose you have a folder of images, all you need to do is create a structure like

└── DATASET_ROOT
       ├── images
               ├── image1.jpg
               ├── image2.jpg
               ├── image3.jpg

and run

python gtsfm/runner/run_scene_optimizer_olssonloader.py --dataset_root /path/to/DATASET_ROOT --image_extension jpg --config_name deep_front_end.yaml --num_workers 4

(or however many workers you desire).

Currently we require EXIF data embedded into your images (or you can provide ground truth intrinsics in the expected format for an Olsson dataset, or COLMAP-exported text data, etc)

[johnwlambert]

Can you double check that your data has EXIF data embedded?