You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How did you install ODM? (Docker, installer, natively, ...)?
Docker
What is the problem?
Wrong rolling shutter applied for 4:3 image
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
Assuming that the rolling shutter varies with the height of the image, the code for mavic 2 pro is only applied for 3:2 and not 4:3 as specified in the code comment.
[Mavic 2 Pro], 20MP, 5472×3648 = native ratio of 3:2.
$ python -c "print(4864*3648/1000000)"
17.743872
So in 4:3 ratio 16:9 readout will be applied. 4:3 and 3:2 have same height so theoretically same sensor readout
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
Just check the code ...
The text was updated successfully, but these errors were encountered:
kikislater
added a commit
to kikislater/OpenDroneMap
that referenced
this issue
Sep 28, 2022
How did you install ODM? (Docker, installer, natively, ...)?
Docker
What is the problem?
Wrong rolling shutter applied for 4:3 image
What should be the expected behavior? If this is a feature request, please describe in detail the changes you think should be made to the code, citing files and lines where changes should be made, if possible.
Assuming that the rolling shutter varies with the height of the image, the code for mavic 2 pro is only applied for 3:2 and not 4:3 as specified in the code comment.
[Mavic 2 Pro], 20MP, 5472×3648 = native ratio of 3:2.
So in 4:3 ratio 16:9 readout will be applied. 4:3 and 3:2 have same height so theoretically same sensor readout
How can we reproduce this? What steps did you do to trigger the problem? If this is an issue with processing a dataset, YOU MUST include a copy of your dataset uploaded on Google Drive or Dropbox (otherwise we cannot reproduce this).
Just check the code ...
The text was updated successfully, but these errors were encountered: