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.

Sign up for GitHub

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

Jump to bottom

qnet will not open a .lis #4341

Closed
shawn-brueshaber opened this issue Mar 5, 2021 · 18 comments · Fixed by #4361
Closed

qnet will not open a .lis #4341

shawn-brueshaber opened this issue Mar 5, 2021 · 18 comments · Fixed by #4361
Assignees
@jessemapel
Labels
bug Something isn't working Missions Issues which are a priority for missions

Comments

@shawn-brueshaber
Copy link

ISIS version(s) affected 3.6. MacOS

Description
Attempting to use qnet and it keeps throwing an error about the list:

Error processing cube list.
USER ERROR Can't open or invalid file list [/Users/shawnrb/Desktop/Red_list.lis].
USER ERROR FileName [RED_A09.cub] can not be added to serial number list.
USER ERROR Invalid serial number [Unknown] from file [RED_A09.cub].

I have tried copying and pasting the location of the .lis and .cub files to the Desktop from their original location (Desktop/users/shawnrb/Juno_Orbit27/7/file.cub. I've tried changing the names of the .lis and .cub files thinking maybe their original names were too long. I've tried adding their complete file path to the list of cubs as well. Nothing works so far. These cubs open just fine with qview no matter what so I'm very perplexed as to why qnet barfs and I'm dead in the water until I get this figured out.

list name: Red_list.lis.
lis contents:
RED_A09.cub
RED_B10.cub
RED_C11.cub
@rbeyer
Copy link
Contributor

rbeyer commented Mar 5, 2021

I think I've run into something like this. Does your Red_list.lis file end with the "b" in RED_C11.cub, or is there a "carriage return/linefeed" character after it? If not, trying putting one there. If you're creating this file programmatically, you might be putting and end-of-line characters between the elements, but not after the last one.

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@lwellerastro
Copy link
Contributor

USER ERROR FileName [RED_A09.cub] can not be added to serial number list.
USER ERROR Invalid serial number [Unknown] from file [RED_A09.cub].

Hi @shawn-brueshaber, qnet is specifically complaining about not being able to access/construct a serial number for your image. Qview does not require this information but control network programs do. This sounds like a problem with the data area. Could you run the program getsn and let's us know what your results are. If it is "Unknown" then key files are missing. I won't be able to help you with data area setup issues, but when available one of the developers can. You might poke around other similar posts in the meantime to do some trouble-shooting on your own.

@jessemapel
Copy link
Contributor

jessemapel commented Mar 5, 2021 •
edited
Loading

It looks like it cannot create a serial number for the image, do you have your data area downloaded properly? Check that $ISISDATA/juno/translations/junoSerialNumber0001.trn exists. It could be that you downloaded the ISIS 4 data area which does not contain these translation files, they were moved into the distribution.

See the Readme for more information

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@jessemapel
Copy link
Contributor

@shawn-brueshaber Can you post the label from the first image?

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@jessemapel
Copy link
Contributor

jessemapel commented Mar 5, 2021 •
edited
Loading

Can you post the cube label from RED_A09.cub?

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@jessemapel
Copy link
Contributor

Run the catlab program on the Cube file to get the Cube label, we don't use the original PDS labels, we transfer most of keywords to a new label that we also add some extra data to.

@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 5, 2021 via email

@jessemapel
Copy link
Contributor

jessemapel commented Mar 8, 2021 •
edited
Loading

@shawn-brueshaber I can't see the attachments. You may need to respond on Github directly.

@shawn-brueshaber
Copy link
Author

@shawn-brueshaber Do I can't see the attachments. You may need to respond on Github directly.

catlab_RED_0012.txt
catlab_RED_0007.txt

@jessemapel
Copy link
Contributor

Here's the issue:

Group = Keyword4
  Auto
  InputKey       = FrameletNumber
  InputGroup     = "IsisCube,Instrument"
  InputPosition  = (IsisCube, Instrument)
  OutputName     = Keyword4
  OutputPosition = (Group, SerialNumberKeywords)
  Translation    = (*, *)
End_Group

Is looking for the keyword FrameletNumber on the cubes, but they have FrameNumber. It looks like this was changed in 556ca19 but the serialnumber translation didn't get changed.

@shawn-brueshaber For right now, replace

  InputKey       = FrameletNumber

with

  InputKey       = FrameNumber

in $ISISDATA/juno/translations/junoSerialNumber0001.trn

This is still present in dev, even though the bug was reported on 3.6.

@jessemapel jessemapel added bug Something isn't working Missions Issues which are a priority for missions labels Mar 8, 2021
@shawn-brueshaber
Copy link
Author

shawn-brueshaber commented Mar 8, 2021 via email

@jessemapel
Copy link
Contributor

That was all I needed to do for getsn to work with your cube labels in 4.4.0. Can you double check that your translation file looks like the attached translation file (except with .trn as the extension). You can also try installing ISIS 4.4.0 and then modifying the same file at $ISISROOT/appdata/translations/JunoJunoCamSerialNumber.trn.
JunoJunoCamSerialNumber.txt

@shawn-brueshaber
Copy link
Author

The file name was the problem. I took JunoJunoCamSerialNumber.trn and dropped it into the appropriate directory. There was no such file name there, only JunoSerinalNumber0001.trn. Qnet now allows me to select the list I want.

@jessemapel jessemapel self-assigned this Mar 15, 2021
@jessemapel jessemapel mentioned this issue Mar 15, 2021
Merged
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jessemapel jessemapel

Labels
bug Something isn't working Missions Issues which are a priority for missions
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Updated Juno serial number translation jessemapel/ISIS3
4 participants
@rbeyer @jessemapel @lwellerastro @shawn-brueshaber