Axel Barroso-Laguna · Sowmya Munukutla · Victor Adrian Prisacariu · Eric Brachmann
Project Page | Paper | arXiv | Supplemental
This is the reference implementation of the paper "Matching 2D Images in 3D: Metric Relative Pose from Metric Correspondences" presented at CVPR 2024.
The paper introduces Metric Keypoints (MicKey), a feature detection pipeline that regresses keypoint positions in camera space. MicKey presents a differentiable approach to establish metric correspondences via descriptor matching. From the metric correspondences, MicKey recovers metric relative poses. MicKey is trained in an end-to-end fashion using differentiable pose optimization and requires only image pairs and their ground truth relative poses for supervision.
Assuming a fresh Anaconda distribution, you can install dependencies with:
conda env create -f resources/environment.yml
conda activate mickeyWe ran our experiments with PyTorch 2.0.1, CUDA 11.6, Python 3.8.17 and Debian GNU/Linux 11.
MicKey aims at addressing the problem of instant Augmented Reality (AR) introduced in the Map-free benchmark. In the Map-free set up, instead of building 3D maps from hundreds of images and scale calibrations, they propose to use only one photo of a scene as the map. The Map-free benchmark then evaluates how accurate is the estimated metric relative pose between the reference image (the map) and the query image (the user).
You can find the Map-free dataset in their project page.
Extract the test.zip file into data/mapfree. Optionally, if you want to train MicKey, also download train and val zip files.
We provide two MicKey models.
- mickey.ckpt: These are the default weights for MicKey, without using the overlapping scores provides in Map-free dataset and following the curriculum learning strategy described in the paper.
- mickey_sc.ckpt: These are the weights when training MicKey using the min and max overlapping scores defined in Map-free.
Extract mickey_weights.zip into weights/. In the zip file, we also provide the default configuration needed to run the evaluation.
Similar to Map-free code base, we provide a submission script to generate submission files:
python submission.py --config path/to/config --checkpoint path/to/checkpoint --o results/your_methodThe resulting file results/your_method/submission.zip can be uploaded to the Map-free online benchmark website and compared against existing methods in the leaderboard.
The Map-free benchmark does not provide ground-truth poses for the test set. But we can still evaluate our method locally on the validation set.
python submission.py --config path/to/config --checkpoint path/to/checkpoint --o results/your_method --split valand evaluate it as:
python -m benchmark.mapfree --submission_path results/your_method/submission.zip --split valWe provide the depth maps and correspondences computed by MicKey.
- Download MicKey depth maps.
- Download MicKey correspondences.
- Extract the contents of both files to
data/mapfree
Refer to the Map-free benchmark to learn how to load precomputed correspondes and depth maps in their feature matching pipeline.
We provide a demo script to run the relative pose estimation pipeline on custom image pairs.
As an example, we store in data/toy_example two images with their respective intrinsics.
The script computes their metric relative pose and saves the corresponding depth and keypoint score maps in the image folder.
Run the demo script as:
python demo_inference.py --im_path_ref data/toy_example/im0.jpg \
--im_path_dst data/toy_example/im1.jpg \
--intrinsics data/toy_example/intrinsics.txt \
--checkpoint path/to/checkpoint \
--config path/to/configTo generate the 3D assets as in MicKey's webpage, you can turn on the
--generate_3D_vis flag. This will generate a rendered image with the input images, their computed 3D camera positions,
and the set of 3D point inliers.
Besides the test scripts, we also provide the training code to train MicKey.
We provide two default configurations in config/MicKey/:
- curriculum_learning.yaml: This configuration follows the curriculum learning approach detailed in the paper. It hence does not use any image overlapping information but only relative ground truth poses during training.
- overlap_score.yaml: This configuration relies on the image overlapping information to only choose solvable image pairs during training.
Besides the two default configurations, we also provide a configuration to speed up their training.
These configurations use low-resolution images and do not add the null hypothesis (refer to Section 3.1.4 for details).
We recommend initializing MicKey with these configurations and then
fine-tuning the network with the default ones (which use high-resolution images and the null hypothesis).
They can be found under config/MicKey/:
- curriculum_learning_warm_up.yaml
- overlap_score_warm_up.yaml
To train MicKey default model, use:
python train.py --config config/MicKey/curriculum_learning.yaml \
--dataset_config config/datasets/mapfree.yaml \
--experiment experiment_name \
--path_weights path/to/checkpoint/folderResume training from a checkpoint by adding --resume {path_to_checkpoint}.
The top models, according to the validation loss, the VCRE metric, and the pose AUC score, are saved during training.
Tensorboard results and checkpoints are saved into the folder dir/to/weights/experiment_name.
Note that by default, the configuration is set to use 4 GPUs. You can reduce the expected number of GPUs in the config file (e.g., NUM_GPUS: 1).
- 19 September 2024: Added vectorized RANSAC and warm up configurations.
- 13 August 2024: Added visualization code.
- 7 June 2024: Added precomputed depth maps and keypoint correspondences.
If you use this code in your research, please consider citing our paper:
@inproceedings{barroso2024mickey,
title={Matching 2D Images in 3D: Metric Relative Pose from Metric Correspondences},
author={Barroso-Laguna, Axel and Munukutla, Sowmya and Prisacariu, Victor and Brachmann, Eric},
booktitle={CVPR},
year={2024}
}Copyright © Niantic, Inc. 2024. Patent Pending. All rights reserved. This code is for non-commercial use. Please see the license file for terms.
We use parts of code from different repositories. We thank the authors and maintainers of the following repositories.