- A library for processing equirectangular image that runs on Python.
- Developed using Python>=3.6 (
c++is WIP). - Compatible with
cudatensors for faster processing. - No need for other dependencies except for
numpyandtorch. - Added functionality like creating rotation matrices, batched processing, and automatic type detection.
- Highly modular
If you found this module helpful to your project, please site this repository:
@software{pyequilib2021github,
author = {Haruya Ishikawa},
title = {PyEquilib: Processing Equirectangular Images with Python},
url = {http://github.com/haruishi43/equilib},
version = {0.5.0},
year = {2021},
}
Prerequisites:
- Python (>=3.6)
- Pytorch (tested on 1.12)
pip install pyequilibFor developing, use:
git clone --recursive https://github.com/haruishi43/equilib.git
cd equilib
pip install -r requirements.txt
pip install -e .
# or
python setup.py developNOTE: might not work for PyTorch>=2.0. If you have any issues, please open an issue.
equilib has different transforms of equirectangular (or cubemap) images (note each transform has class and func APIs):
Cube2Equi/cube2equi: cubemap to equirectangular transformEqui2Cube/equi2cube: equirectangular to cubemap transformEqui2Equi/equi2equi: equirectangular transformEqui2Pers/equi2pers: equirectangular to perspective transform
There are no real differences in class or func APIs:
classAPIs will allow instantiating a class which you can call many times without having to specify configurations (classAPIs call thefuncAPI)funcAPIs are useful when there are no repetitive calls- both
classandfuncAPIs are extensible, so you can extend them to your use-cases or create a method that's more optimized (pull requests are welcome btw)
Each API automatically detects the input type (numpy.ndarray or torch.Tensor), and outputs are the same type.
An example for Equi2Pers/equi2pers:
Equi2Pers |
equi2pers |
|
|
For more information about how each APIs work, take a look in .readme or go through example codes in the tests or scripts.
Right-handed rule XYZ global coordinate system. x-axis faces forward and z-axis faces up.
roll: counter-clockwise rotation about thex-axispitch: counter-clockwise rotation about they-axisyaw: counter-clockwise rotation about thez-axis
You can chnage the right-handed coordinate system so that the z-axis faces down by adding z_down=True as a parameter.
See demo scripts under scripts.
To process equirectangular images fast, whether to crop perspective images from the equirectangular image, the library takes advantage of grid sampling techniques.
Some sampling techniques are already implemented, such as scipy.ndimage.map_coordiantes and cv2.remap.
This project's goal was to reduce these dependencies and use cuda and batch processing with torch and c++ for a faster processing of equirectangular images.
There were not many projects online for these purposes.
In this library, we implement varieties of methods using c++, numpy, and torch.
This part of the code needs cuda acceleration because grid sampling is parallelizable.
For torch, the built-in torch.nn.functional.grid_sample function is very fast and reliable.
I have implemented a pure torch implementation of grid_sample which is very customizable (might not be fast as the native function).
For numpy, I have implemented grid sampling methods that are faster than scipy and more robust than cv2.remap.
Just like with this implementation of torch, numpy implementation is just as customizable.
It is also possible to pass the scipy and cv2's grid sampling function through the use of override_func argument in grid_sample.
Developing faster approaches and c++ methods are WIP.
See here for more info on implementations.
Some notes:
- By default,
numpy'sgrid_samplewill use purenumpyimplementation. It is possible to override this implementation withscipyandcv2's implementation usingoverride_func. - By default,
torch'sgrid_samplewill use the official implementation. - Benchmarking codes are stored in
tests/. For example, benchmarking codes fornumpy'sequi2persis located intests/equi2pers/numpy_run_baselines.pyand you can benchmark the runtime performance using different parameters againstscipyandcv2.
Test files for equilib are included under tests.
Running tests:
pytest testsNote that I have added codes to benchmark every step of the process so that it is possible to optimize the code. If you find there are optimal ways of the implementation or bugs, all pull requests and issues are welcome.
Check CONTRIBUTING.md for more information
- Documentations for each transform
- Add table and statistics for speed improvements
- Batch processing for
numpy - Mixed precision for
torch -
c++version of grid sampling - More accurate intrinsic matrix formulation using vertial FOV for
equi2pers - Multiprocessing support (slow when running on
torch.distributed)
