-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Throw exception when image.SetFramePtr() sets a frame without the image listed as its data. #3540
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
Conversation
…the corresponding frame.
ahojnnes
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, LGTM apart from turning this into an exception instead of a hard crash of the process.
Co-authored-by: Johannes Schönberger <[email protected]>
|
One thing that is still extremely unsafe for the reconstruction class is that, there is no guarantee that all images in |
…ciated rig. (#3543) As a follow up to #3540 for safety improvement, this PR includes the following fixes: * ``AddFrame`` should not add a frame with empty data as its never useful in the reconstruction. NumData() is added for the frame class. * ``Frame.SetRigPtr`` should set a rig that has all sensors in the frame data supported. * Conversely, when a rig pointer is available for the frame, ``Frame.AddDataId`` should add data that with the sensor available in the associated rig. Related tests are added. --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ame does not exist in the reconstruction. (#3546) Follow up to #3540 and #3543 --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ge listed as its data. (colmap#3540) Otherwise the reconstruction data structure is broken, and the round trip wont write out the images. Seems to catch issues in some of the test construction. --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ciated rig. (colmap#3543) As a follow up to colmap#3540 for safety improvement, this PR includes the following fixes: * ``AddFrame`` should not add a frame with empty data as its never useful in the reconstruction. NumData() is added for the frame class. * ``Frame.SetRigPtr`` should set a rig that has all sensors in the frame data supported. * Conversely, when a rig pointer is available for the frame, ``Frame.AddDataId`` should add data that with the sensor available in the associated rig. Related tests are added. --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ame does not exist in the reconstruction. (colmap#3546) Follow up to colmap#3540 and colmap#3543 --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ge listed as its data. (#3540) Otherwise the reconstruction data structure is broken, and the round trip wont write out the images. Seems to catch issues in some of the test construction. --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ciated rig. (#3543) As a follow up to #3540 for safety improvement, this PR includes the following fixes: * ``AddFrame`` should not add a frame with empty data as its never useful in the reconstruction. NumData() is added for the frame class. * ``Frame.SetRigPtr`` should set a rig that has all sensors in the frame data supported. * Conversely, when a rig pointer is available for the frame, ``Frame.AddDataId`` should add data that with the sensor available in the associated rig. Related tests are added. --------- Co-authored-by: Johannes Schönberger <[email protected]>
…ame does not exist in the reconstruction. (#3546) Follow up to #3540 and #3543 --------- Co-authored-by: Johannes Schönberger <[email protected]>
Otherwise the reconstruction data structure is broken, and the round trip wont write out the images.
Seems to catch issues in some of the test construction.