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
The frame camera model code throws an exception when it is asked to find the sensor position and velocity when the input pixel is a bit outside of the image domain. This is for functions UsgsAstroFrameSensorModel::getSensorPosition() and getSensorVelocity().
This is not desirable behavior. It is possible for a ground point to project into the camera at a pixel outside of the image box. The software should be able to return the sensor position and velocity for such a pixel, which is the same for all pixels anyway, for a frame camera.
This check is not present for linescan cameras, which graciously does the best it can. It clamps the input pixel line to the range of lines it can handle.
Such behavior as for the frame camera is problematic as it requires fixes in software that functions perfectly fine with other camera implementations, including outside of usgscsm.
The text was updated successfully, but these errors were encountered:
The frame camera model code throws an exception when it is asked to find the sensor position and velocity when the input pixel is a bit outside of the image domain. This is for functions UsgsAstroFrameSensorModel::getSensorPosition() and getSensorVelocity().
This is not desirable behavior. It is possible for a ground point to project into the camera at a pixel outside of the image box. The software should be able to return the sensor position and velocity for such a pixel, which is the same for all pixels anyway, for a frame camera.
This check is not present for linescan cameras, which graciously does the best it can. It clamps the input pixel line to the range of lines it can handle.
Such behavior as for the frame camera is problematic as it requires fixes in software that functions perfectly fine with other camera implementations, including outside of usgscsm.
The text was updated successfully, but these errors were encountered: