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 - Throws warning for mosaics containing tracking table #3685

Closed
lwellerastro opened this issue Feb 18, 2020 · 5 comments · Fixed by #3891
Closed

Qview - Throws warning for mosaics containing tracking table #3685

lwellerastro opened this issue Feb 18, 2020 · 5 comments · Fixed by #3891
Assignees
Labels
bug Something isn't working Products Issues which are impacting the products group

Comments

@lwellerastro
Copy link
Contributor

lwellerastro commented Feb 18, 2020

ISIS version(s) affected: isis3.10.0

Description
Qview throws warning (and never stops) for a 10+ year old mosaic that used to have a tracking band that was removed sometime in the past, but still contains the table associated with it (InputImages).

See attached error message.
QviewError_TrackingTable

Every time I click OK to make the warning go away, a new one pops up. Sometimes the only way to get out of qview is to kill it.

How to reproduce
qview /archive/projects/lmmp/rdr/SAB/Mosaic/LRO_NAC_Mosaic_60S200E_50cmp.cub
Click anywhere in the qview window (not even the image) and the warning will pop up.

Possible Solution

Additional context
The program cubeatt (from=mosaic+1) does not work as the tracking band is not present. I also tried to run the program trackextract to help remove the table but that program does not work on 16 bit files.

There have been some other suggestions made via an astrodiscuss post I put up in regard to this problem ([https://astrodiscuss.usgs.gov/t/how-to-remove-a-table-from-an-isis-cube-and-its-label/372]) that I might try at another time.

@lwellerastro lwellerastro added bug Something isn't working Products Issues which are impacting the products group labels Feb 18, 2020
@lwellerastro
Copy link
Contributor Author

A work around for this problem is to run cubeatt in the following manner:

cubeatt from=old.cub to=new.cub proptables=false

Qview should still probably ignore the table though if it exists, or just provide a more meaningful warning and only once, not repeatedly as it is doing now.

@jessemapel jessemapel self-assigned this Feb 27, 2020
@jessemapel
Copy link
Contributor

So it looks like qview thinks that the mosaic is the tracking cube itself and is trying to convert the pixels from the mosaic to filenames and fails repeatedly. I think the fix here is to have qview not raise warnings on failure in AdvancedTrackTool::TrackMosaicOrigin and instead just pass. This will cause mosaics like this to just ignore the tracking table. This will also cause qview to silently fail when other issues with the tracking table or cube arise.

Another option would be to have AdvancedTrackTool::TrackMosaicOrigin instead raise a fatal error and die. This would help avoid silent failures, but would be more intrusive to users.

@jessemapel jessemapel removed their assignment Feb 28, 2020
@jessemapel jessemapel self-assigned this Jun 1, 2020
@lwellerastro lwellerastro reopened this Dec 10, 2020
@lwellerastro
Copy link
Contributor Author

Hi, I was just revisiting the data in my original post and it appears to still have the problem I posted.

I'm working in 3.10.2. It's been so long I can't remember testing this, but I assumed it worked when this post was closed. Should I expect it work under 3.10.2 or only under a version of isis4?

How to reproduce
qview /archive/projects/lmmp/rdr/SAB/Mosaic/LRO_NAC_Mosaic_60S200E_50cmp.cub
Click anywhere in the qview window (not even the image) and the warning will pop up.

@jessemapel
Copy link
Contributor

Last 3.X release was in April, this was fixed in June so it is only available in 4.1.1 and later

@jessemapel
Copy link
Contributor

It's not reproducing in ISIS4.2.0 as expected, gonna close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Products Issues which are impacting the products group
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants