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
Description
While working with MSL data (landed data) and a small local DEM in cam2map or campt I get the following:
Group = Error
Program = campt
Code = 1
Message = "Requested position does not project in camera model; no surface
intersection"
File = CameraPointInfo.cpp
Line = 343
End_Group
End
It seems this issue arises with a very small DEM, basically 0.001 degree by 0.001 degree along with very oblique angles (as we are looking toward the horizon from the surface).
Rather than intersect a mesh or other surface simulation, the algorithm starts by intersecting the sphere/ellipsoid, gets the lat lon from the intersection, then tries to get the radii value in the DEM at the intersection lat lon. If pixel value in the DEM at that point is NULL, we fail to intersect and thus end the traverse to our DEM intersection. See intersectSurface in DemShape.cpp
With the above conditions, it seems like the DemShape intersectSurface algorithm falls apart and cannot accurately walk the intersection back towards the rover/point of origin like one would expect. Instead, failing to get the local radius of the DEM since the initial point of intersection lands outside of the small DEM.
This is tagged as a bug, but may be a fundamental limitation in the DemShape model.
How to reproduce
I have attached a zip file that contains the necessary files to produce the error. Inside of the zip is a README with further details min_example.zip
Possible Solution
If this is a fundamental limitation of the DemShape intersection code, then using a different method may be necessary. Other shape models exist in ISIS such as embree and bullet, both with more robust/accurate intersection algorithms. So a solution may be to convert the DEM into a different file format for those other shape models to use.
Another alternative would be to rewrite the DEM intersection algorithm to be more robust, potentially using point clouds. EmbreeShapeModel seems to already use point clouds and can read in generic point cloud files so rewriting the DEM intersection seems redundant if converting the DEM to a point cloud file is possible.
The text was updated successfully, but these errors were encountered:
Unfortunately, this issue hasn't received much attention lately, so it is labeled as 'stale.'
If no additional action is taken, this issue will be automatically closed in 180 days.
If you want to participate in our support prioritization meetings or be notified when support sprints are happening, you can sign up the support sprint notification emails here.
ISIS version(s) affected: 3.7.0+
Description
While working with MSL data (landed data) and a small local DEM in cam2map or campt I get the following:
Here is the mapping group from the DEM:
It seems this issue arises with a very small DEM, basically 0.001 degree by 0.001 degree along with very oblique angles (as we are looking toward the horizon from the surface).
Rather than intersect a mesh or other surface simulation, the algorithm starts by intersecting the sphere/ellipsoid, gets the lat lon from the intersection, then tries to get the radii value in the DEM at the intersection lat lon. If pixel value in the DEM at that point is NULL, we fail to intersect and thus end the traverse to our DEM intersection. See
intersectSurface
in DemShape.cppWith the above conditions, it seems like the DemShape
intersectSurface
algorithm falls apart and cannot accurately walk the intersection back towards the rover/point of origin like one would expect. Instead, failing to get the local radius of the DEM since the initial point of intersection lands outside of the small DEM.This is tagged as a bug, but may be a fundamental limitation in the DemShape model.
How to reproduce
I have attached a zip file that contains the necessary files to produce the error. Inside of the zip is a README with further details
min_example.zip
Possible Solution
If this is a fundamental limitation of the DemShape intersection code, then using a different method may be necessary. Other shape models exist in ISIS such as embree and bullet, both with more robust/accurate intersection algorithms. So a solution may be to convert the DEM into a different file format for those other shape models to use.
Another alternative would be to rewrite the DEM intersection algorithm to be more robust, potentially using point clouds.
EmbreeShapeModel
seems to already use point clouds and can read in generic point cloud files so rewriting the DEM intersection seems redundant if converting the DEM to a point cloud file is possible.The text was updated successfully, but these errors were encountered: