-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plotting "line number" rather than "frame index" in optimization plots #44
Comments
I added to orbit_plot.py logic to go from time to image line and vice versa, and for how to go from the index in the list of orientations to time for that orientation. The implementation can be seen in this diff: oleg-alexandrov/StereoPipeline@cb84a97 It is likely better to just copy the needed functions over as they are small. It is a bit unclear from that code how to go from pose index to time at that pose. The formula is time = t0 + index * dt, where t0 and dt are read from the json file fields m_t0Quat and m_dtQuat. |
🙌 Nice! I'll work on porting that logic over in the next days. |
For the record, I found a bug in my logic for going from line number to quaternion index. I put a fix here: oleg-alexandrov/StereoPipeline@c4c8ff6 |
The tool should be able to handle the two linescan cameras having different sampling rates, because the jitter solver can resample the positions and orientations. I put a fix for this (for orientations only) in orbit_plot at: NeoGeographyToolkit/StereoPipeline@f61c085 |
Nice, I already handled that case in the code I wrote previously. On a quick read, it looks like both overall approaches are comparable and come down to a conditional linear interpolation. So I won't port over the same change to my version. Here are those calculations in my code: asp_plot/asp_plot/csm_camera.py Lines 82 to 93 in e6b9fb0
and: asp_plot/asp_plot/csm_camera.py Lines 105 to 121 in e6b9fb0
|
Related to #35 and #42
Below taken from email thread:
Currently, for camera optimization plots our x-axis is "Frame Index" (or "Linescan Sample"), which is just the position / rotation sampling index taken from the CSM JSON file. In theory, is there a way that we could, perhaps with some known sampling interval, retrieve the approximate Line Number for the x-axis in my updated summary plots, instead of the “Frame Index” (which is really some CSM sampling interval)? Perhaps the answer lies in the original XML camera file (for the original, pre-CSM conversion)?
The text was updated successfully, but these errors were encountered: