Skip to content
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

qview displaying local incidence/emission instead of global #5422

Open
rvwagner opened this issue Feb 20, 2024 · 2 comments
Open

qview displaying local incidence/emission instead of global #5422

rvwagner opened this issue Feb 20, 2024 · 2 comments
Labels
bug Something isn't working inactive Issue that has been inactive for at least 6 months

Comments

@rvwagner
Copy link

ISIS version(s) affected: 7.1.0 through present; bug was introduced between 7.0.0 and 7.1.0

Description
In the qview Advanced Tracking Tool, the Emission and Incidence columns are displaying the Local Emission and Local Incidence values (based on surface topography in the image's linked DTM). There is currently no way to display the emission and incidence values as calculated on a sphere in qview.

How to reproduce
This is a fairly extreme example using only the built-in DTM and a relatively small LROC NAC image:

curl "https://pds.lroc.asu.edu/data/LRO-L-LROC-2-EDR-V1.0/LROLRC_0003/DATA/MAP/2010108/NAC/M126271092LE.IMG" > M126271092LE.IMG
lronac2isis from=M126271092LE.IMG to=M126271092L.raw.cub
spiceinit from=M126271092L.raw.cub web=true
qview M126271092L.raw.cub

Then hit '/' to zoom to 1:1 at the center of the image (roughly line 5000, sample 1300), open the advanced tracking tool, and turn on the Incidence and Local Incidence columns. As you wave the cursor over the image, note that both columns remain perfectly in sync, even as the values range from ~60 to 80 degrees. Non-local incidence angles over this few-hundred-meter area should be effectively constant, not varying by 20 degrees.

@rvwagner rvwagner added the bug Something isn't working label Feb 20, 2024
@lwellerastro
Copy link
Contributor

I think it is related to PR #5345 and the post that helped surface the problem.

Copy link

Thank you for your contribution!

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.

Read more about our support processs here

@github-actions github-actions bot added the inactive Issue that has been inactive for at least 6 months label Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working inactive Issue that has been inactive for at least 6 months
Projects
None yet
Development

No branches or pull requests

2 participants