https://github.com/bytedance/particle-sfm

ParticleSfM: Exploiting Dense Point Trajectories for Localizing Moving Cameras in the Wild. ECCV 2022.

https://github.com/bytedance/particle-sfm

Science Score: 33.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
  • DOI references
  • Academic publication links
    Links to: arxiv.org
  • Committers with academic emails
    2 of 6 committers (33.3%) from academic institutions
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (12.2%) to scientific vocabulary

Keywords

dynamic-scenes motion-segmentation research structure-from-motion video-correspondence
Last synced: 9 months ago · JSON representation

Repository

ParticleSfM: Exploiting Dense Point Trajectories for Localizing Moving Cameras in the Wild. ECCV 2022.

Basic Info
Statistics
  • Stars: 320
  • Watchers: 13
  • Forks: 26
  • Open Issues: 5
  • Releases: 2
Topics
dynamic-scenes motion-segmentation research structure-from-motion video-correspondence
Created almost 4 years ago · Last pushed over 1 year ago
Metadata Files
Readme License

README.md

ParticleSfM

Paper | Video | Project Page

Code release for our ECCV 2022 paper "ParticleSfM: Exploiting Dense Point Trajectories for Localizing Moving Cameras in the Wild." by Wang Zhao, Shaohui Liu, Hengkai Guo, Wenping Wang and Yong-Jin Liu.

[Introduction] ParticleSfM is an offline structure-from-motion system for videos (image sequences). Inspired by Particle video, our method connects pairwise optical flows and optimizes dense point trajectories as long-range video correpondences, which are used in a customized global structure-from-motion framework with similarity averaging and global bundle adjustment. In particular, for dynamic scenes, the acquired dense point trajectories can be fed into a specially designed trajectory-based motion segmentation module to select static point tracks, enabling the system to produce reliable camera trajectories on in-the-wild sequences with complex foreground motion.

Teaser

Contact Wang Zhao (thuzhaowang@163.com), Shaohui Liu (b1ueber2y@gmail.com) and Hengkai Guo (guohengkai@bytedance.com) for questions, comments and reporting bugs.

If you are interested in potential collaboration or internship at ByteDance, please feel free to contact Hengkai Guo (guohengkai@bytedance.com).

Update by 2025.02.05

We support GLOMAP in our pipeline, which achieves more accurate results on 13 sequences of the Sintel dataset:

| Method | ATE (m) | RPE trans (m) | RPE rot (deg) | SfM runtime (min) | #Frames | |:-:|:-:|:-:|:-:|:-:|:-:| | Global SfM - Ours w/ gcolmap(Theia) | 0.104 | 0.054 | 0.414 | 3.35 | 45.6 | | Global SfM - Ours w/ GLOMAP | 0.057 | 0.031 | 0.201 | 6.97 | 45.6 |

Test it by simply changing the sfm_type to global_glomap: python run_particlesfm.py --image_dir /path/to/the/image/folder/ \ --output_dir /path/to/output/workspace/ \ --sfm_type global_glomap # "global_theia" for the paper version

Installation

  1. Install dependencies:
  • Ceres >= 2.0.0

For using gcolmap (Theia) as in the original ParticleSfM paper: * COLMAP <= 3.8 [Guide] * Theia SfM (customized version) [Guide]

Alternatively, if you want to use our latest GLOMAP support: * GLOMAP

  1. Set up Python environment with Conda: conda env create -f particlesfm_env.yaml conda activate particlesfm

  2. Build our point trajectory optimizer and global structure-from-motion module.

  3. The path to your customized python executable should be set here.

  4. (Optional) Add another gcc search path (e.g. gcc 9) here to compile gmapper correctly. git submodule update --init --recursive sudo apt-get install libhdf5-dev bash scripts/build_all.sh

  5. Download pretrained models for MiDaS, RAFT and our motion segmentation module (download script). bash scripts/download_all_models.sh

Quickstart Demo

  1. Download two example in-the-wild sequences [Google Drive] from DAVIS: snowboard and train: bash ./scripts/download_examples.sh
  2. Example command to run the reconstruction (e.g. on snowboard): python run_particlesfm.py --image_dir ./example/snowboard/images --output_dir ./outputs/snowboard/ You can also alternatively use the command for the workspace with the images folder inside below. This option will write all the output in the same workspace. python run_particlesfm.py --workspace_dir ./example/snowboard/
  3. Visualize the outputs with either the COLMAP GUI or your customized visualizer. We also provide a visualization script: python -m pip install open3d pycolmap python visualize.py --input_dir ./outputs/snowboard/sfm/model --visualize The results below are expected (left: snowboard; right: train): Example

Usage

  1. Given an image sequence, put all the images in the same folder. The sorted ordering of the names should be consistent with its ordering in the sequence.

  2. Use the following command to run our whole pipeline: python run_particlesfm.py --image_dir /path/to/the/image/folder/ \ --output_dir /path/to/output/workspace/ This will sequentially run optical flow -> point trajectory -> motion seg -> sfm. The final results will be saved inside the image data folder with COLMAP output format.

    If you have the prior information that the scene to be reconstructed is fully static, you can skip the motion segmentation module with --assume_static. Conversely, if you only want to run the motion segmentation, attach --skip_sfm to the command.

    To speed up - Use "--skippathconsistency" to skip the path consistency optimization of point trajectories - Try higher down-sampling ratio for optimizing point trajectories: e.g. "--sample_ratio 4"

  3. Visualize the outputs using COLMAP GUI (Download the COLMAP Binary and import the data sequence directory) or just your customized visualizer.

Evaluation

MPI Sintel dataset

  1. Download the Sintel dataset. You also need to download the groundtruth camera motion data and the generated motion mask to evaluate the pose and motion segmentation.
  2. Prepare the sequences: python scripts/prepare_sintel.py --src_dir /path/to/your/sintel/training/final/ \ --tgt_dir /path/to/the/data/root/dir/want/to/save/
  3. Run ParticleSfM reconstructions: python run_particlesfm.py --root_dir /path/to/the/data/root/dir/

  4. To evaluate the camera poses: python ./evaluation_evo/eval_sintel.py --input_dir /path/to/the/data/root/dir/ \ --gt_dir /path/to/the/sintel/training/data/camdata_left/ \ --dataset sintel This will output a txt file with detailed error metrics. Also, the camera trajectories are plotted and saved inside each data sequence folder.

  5. To evaluate the motion segmentation: python ./motion_seg/eval_traj_iou.py --root_dir /path/to/the/data/root/dir/ \ --gt_dir /path/to/the/sintel/rigidity/

ScanNet dataset

  1. Download the test split of ScanNet dataset, extract the data from .sens data using the official script.

  2. Prepare the sequences: python scripts/prepare_scannet.py --src_dir /path/to/your/scannet/test/scans_test/ \ --tgt_dir /path/to/the/data/root/dir/want/to/save/ We use the first 20 sequences of test split and perform downsampling with stride 3, resize the image to 640x480.

  3. Run ParticleSfM reconstructions: python run_particlesfm.py --root_dir /path/to/the/data/root/dir/ \ --flow_check_thres 3.0 --assume_static

  4. To evaluate the camera poses: python ./evaluation_evo/eval_scannet.py --input_dir /path/to/the/data/root/dir/ \ --gt_dir /path/to/the/scannet/test/scans_test/ \ --dataset scannet

This will output a txt file with detailed error metrics. Also, the camera trajectories are plotted and saved inside each data sequence folder.

Training

  1. Download the Flyingthings3D dataset from the official website. We need the RGB images (finalpass) and optical flow data.

  2. Download the generated binary motion labels from here or GoogleDrive, and unpack this archive into the root directory of the FlyingThings3D dataset. We thank the authors of MPNet for kindly sharing it.

  3. Prepare the training data: python ./scripts/prepare_flyingthings3d.py --src_dir /path/to/your/flyingthings3d/data/root/

  4. To launch the training, configure your config file inside ./motion_seg/configs/ and then run: cd ./motion_seg/ python train_seq.py ./configs/your-config-file cd ..

Applications

Citation

@inproceedings{zhao2022particlesfm, author = {Zhao, Wang and Liu, Shaohui and Guo, Hengkai and Wang, Wenping and Liu, Yong-Jin}, title = {ParticleSfM: Exploiting Dense Point Trajectories for Localizing Moving Cameras in the Wild}, booktitle = {European conference on computer vision (ECCV)}, year = {2022} }

More related projects

  • DynaSLAM. Bescos et al. DynaSLAM: Tracking, Mapping and Inpainting in Dynamic Scenes. IROS 2018.
  • TrianFlow. Zhao et al. Towards Better Generalization: Joint Depth-Pose Learning without PoseNet. CVPR 2020.
  • VOLDOR. Min et al. VOLDOR-SLAM: For the times when feature-based or direct methods are not good enough. ICRA 2021.
  • DROID-SLAM. Teed et al. DROID-SLAM: Deep Visual SLAM for Monocular, Stereo, and RGB-D Cameras. NeurIPS 2021.

Acknowledgements

This project could not be possible without the great open-source works from COLMAP, Theia, hloc, RAFT, MiDaS and OANet. We sincerely thank them all.

Owner

  • Name: Bytedance Inc.
  • Login: bytedance
  • Kind: organization
  • Location: Singapore

GitHub Events

Total
  • Create event: 3
  • Release event: 2
  • Issues event: 3
  • Watch event: 48
  • Delete event: 1
  • Issue comment event: 6
  • Push event: 3
  • Pull request review comment event: 3
  • Pull request review event: 4
  • Pull request event: 7
  • Fork event: 3
Last Year
  • Create event: 3
  • Release event: 2
  • Issues event: 3
  • Watch event: 48
  • Delete event: 1
  • Issue comment event: 6
  • Push event: 3
  • Pull request review comment event: 3
  • Pull request review event: 4
  • Pull request event: 7
  • Fork event: 3

Committers

Last synced: about 1 year ago

All Time
  • Total Commits: 26
  • Total Committers: 6
  • Avg Commits per committer: 4.333
  • Development Distribution Score (DDS): 0.692
Past Year
  • Commits: 6
  • Committers: 2
  • Avg Commits per committer: 3.0
  • Development Distribution Score (DDS): 0.333
Top Committers
Name Email Commits
B1ueber2y b****y@g****m 8
Hengkai Guo g****k@g****m 8
thuzhaowang t****g@1****m 4
yanzhang25 y****g@i****h 3
mkocabas m****s@o****m 2
JonathanLehner l****j@s****h 1
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 22
  • Total pull requests: 15
  • Average time to close issues: about 2 months
  • Average time to close pull requests: about 10 hours
  • Total issue authors: 20
  • Total pull request authors: 6
  • Average comments per issue: 2.18
  • Average comments per pull request: 0.33
  • Merged pull requests: 11
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 3
  • Pull requests: 7
  • Average time to close issues: about 1 hour
  • Average time to close pull requests: about 10 hours
  • Issue authors: 2
  • Pull request authors: 2
  • Average comments per issue: 1.33
  • Average comments per pull request: 0.0
  • Merged pull requests: 5
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • fangli333 (2)
  • EarltShirt (2)
  • fzhiheng (1)
  • galalalala (1)
  • student-petercai (1)
  • jaymefosa (1)
  • iahmedmaher (1)
  • Lifedecoder (1)
  • cwoydyparksI (1)
  • cho-wang001 (1)
  • yangjidong06 (1)
  • zhuangqirong (1)
  • UEawoKod (1)
  • CH-901 (1)
  • umariqb (1)
Pull Request Authors
  • B1ueber2y (7)
  • guohengkai (4)
  • priyadarsimishra (2)
  • yz-cnsdqz (1)
  • JonathanLehner (1)
  • mkocabas (1)
Top Labels
Issue Labels
Pull Request Labels