We could do a zoom in the future (I'll have to allocate time in advance so it won't be on some wacky time). Additionally, I'll be adding some examples on my off-days along with working on the rest of the calibration utilities.

On calibration utilities, these are still mostly in the draft phase. It is just the camera models that are mostly finished after lots of planning and drawings by hand. However, the calibration utilities and models are still enough to successfully perform MLOS-based Tomo-PIV and other TOMO-PIV reconstruction algorithms that do not utilize optical transfer functions (OTF). This is mostly because OTFs require a basic PTV implementation (segmentation and particle matching), which I'll be using either an advanced iterative particle reconstruction algorithm or epipolar matching for locating particles for the volume self calibrations (VSC) and OTF calibrations. For VSC, it is broken down into two parts, a course and a fine VSC algorithm. The course VSC algorithm uses a correlation-based algorithm to minimize large camera drifts (literature reports up to 18 pixels) and the fine VSC uses a PTV-based algorithm with ghost particle suppression to refine the calibration as much as possible. Ideally, this would allow a camera system to be calibrated with a greater tolerance towards camera malignment (something I desperately need in my attic and backyard shed lab).

Oh, on a final note, I plan on incorporating wand-based calibration utilities and possibly refraction interfaces for the pinhole camera based on OpenPTV. This is mostly for the extrinsic parameters as the algorithm by Zang handles the calibration of the intrinsic parameters (except for distortion which is something I just realized I forgot).

@alexlib
Do we know how the AI source code reviewer may handle a 10k+ line (should be no more than 15k lines of code by completion) pull request for the camera calibration module and an expected 4k+ line pull request for a tomo-PIV module? The diff shouldn't be too terrible since most lines of code (>99.996) would be new and the only existing file that should be modified is a few lines of code in windef.py that allows a pre-computed mapping array to be utilized in the image deformation process. If possible, I would like it in this draft pull request, but it appears that it may not support drafts since I do not see an option for it in the reviewers tab (although, this is contradicting the few articles I read on the internet)..

Never mind, it looks like it only applies for pull requests that are capable of being merged.

I have no idea. I suggest you try it in a separate branch, not in master.

What is really needed here @ErichZimmer are tutorials - what are the use cases for calibration, how to use it, how to choose different models, what the user gets at the end of the story? calibrated stereo? how to use it with OpenPIV, etc.
I'm here to help - we can discuss various tasks and distribute it among us.

Indeed, documentation and notebooks are really important. In fact, I am currently working on a few notebooks at the moment which mainly covers the following:

• Basics of camera calibration
• How to image a calibration target
• Calibrating a single camera
• Calibrating multiple cameras
• A very simple stereo camera setup as an example (not to confuse with stereo-PIV)

As I do the notebooks, I am constantly refactoring the calibration module, though, since the only way to improve such a module is to physically use it. For instance, using Zhang's calibration method on a free-form calibration target allowed for a simple stereo-vision system to be setup where I can calculate the distance of an object in my room via triangulation. However, things have been slow for the past month or so since I unfortunately did catch a weird strain of SARS-COV-2 in addition to participating in some rather time consuming university courses.

wish you a quick and full recovery. if I can help, please share with me the details.

What happens on this branch? No pressure, just curiosity @ErichZimmer

@ErichZimmer - have you tried to push this pull request? is it ready ?

@alexlib I re-evaluated the camera and calibration module and I think it still needs some work. I can perform MENT or MLOS TOMO-PIV with it, but it needs a lot of work still. I still have weekends to work on projects. I can't get it to perform stereo PIV due to some mapping issue on the dewarp image function, so that would require some further analysis on why (especially once I find my physical notebook on implementation details and edge cases).