-
Notifications
You must be signed in to change notification settings - Fork 176
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
PHOTOMET Won't Accept Pre-Made Backplanes #5281
Comments
Hi @astrostu, could you share some of your processing steps so that we can try and duplicate the problem here? Folks might want to see an example command line for how you are creating backplanes, and how you are running photomet using that backplane (along with other parameter settings). If you are using a pvl with parameter names and values, please include the contents of that as well. 4.0.0 changelog notes: photomet now correctly reads array valued PvlKeywords. #3608 |
Just verified in v7.1.0 that it also doesn't work. I downloaded a random UV file to test it out:
For this test, I only went through the odd framelets, and then just UV1 band. I kept the default names from explode at this point. I renamed the band0001, 2, and 3 to phase, emission, incidence. |
I have also just verified that the above does work on an older v4.3 (I think?) install of ISIS. But, in at least v 7.1 and 7.2 it does not. I'll go ahead and check v 8.0 now just in case. But that said, I also tested it on a random Cassini image of Mimas I have, and it is also broken with the same error. With that said: If I omit anglesource=backplane and the backplanes, PHOTOMET does work and does not throw the error. So, this appears to just be an issue with calling pre-made backplanes. Perhaps that's why this hasn't come up yet: For most missions, it doesn't make much sense to make the backplanes ahead of time, but for MARCI it does because you can use the same backplanes for both even and odd framelet cubes but only have to calculate the backplanes once. Backplane calculation takes much longer than applying PHOTOMET, so it's a real time-saver. |
Thanks for all of the feedback @astrostu.
The program works as expected under 7.0.0. I didn't bother going back further than that version. Test data can be found under my user work area Isis3Tests/Photomet/AngleSourceFile. See proc.scr for command. The directory contains input and output for the successful run under isis7.0.0. I don't see anything obvious in the changelog that would suddenly break this functionality, but clearly something snuck in. Hopefully knowing which version the break first occurred will make it easier to identify the problem. @astrostu, at the risk of telling you something you already know, unless you are using the renamed phocube backplanes for reasons beyond ease of identification, you could save yourself some space by referencing the phocube output file band when specifying the angle source files, e.g.
|
@lwellerastro Thanks, and yes, I do know about that, but I had to do it that way for a workaround of a bug that has been fixed since I developed the work-around: #4810. It's often easier to stick with a workaround that doesn't cost anything (disk, very minor CPU, etc.) than to update it after a bug fix. But, next time I get under the hood of this code, I will probably update it to reflect that bugfix. |
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 |
This is still a pretty clear bug that breaks previous functionality. Still exists in 8.x |
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 |
This is still a bug as far as I can tell that breaks previous functionality and can significantly lengthen the processing of some images. I've subscribed to the sprint email list so I'll try to bring this up. |
I am WAY out of depth here... could this be related to the change from GetFileName to GetCubeName? That was the most recent commit for Photomet and the timing would be about right (the commit was made in 2022, so ISIS versions before 7.0.0 should be fine). I noticed that the 'Angle source = backplane' block still calls GetFileName. I honestly don't know if that's right or wrong. I'll emphasize that I don't speak C++, don't understand the ISIS code base, was digging into photomet for an unrelated reason, and had happened to trip on this bug earlier in the day. So, consider the source... |
This is still an existing issue and I just wanted to boost it up! |
I'm getting the same error on ISIS 8.0.3. I have a Juno SRU image with calculated photometric backplanes and I am running into this issue:
Group = NormalizationModelParametersUsed Group = AtmosphericModelParametersUsed Group = PhotometricModelParametersUsed |
ISIS version(s) affected: 7.2.0
Description
I am attempting to run PHOTOMET on some MARCI images with code that worked fine before in ISIS version 4.3.x and 4.4.0. I'm using 7.2.0 now (waiting for 8.0.1 to be available with the JIGSAW fix before upgrading) and have a very weird error with PHOTOMET. It's more efficient for MARCI processing to create the backplanes first, save them, and then use them as a reference for applying a photometric model. However, with version 7.2.0, when I give it the file names, it says "PROGRAMMER ERROR Parameters [PHASE_ANGLE_FILE] is not a filename.
I have tried to use both the command-line and the GUI version with the same results. I have also renamed the files to something more simple - and ensured they exist - and get the same results. I verified in QVIEW that the backplanes look good. It would appear as though somewhere between version 4 and 7, something in PHOTOMET got broken, which is weird because I do not see any changes to it in the overall ISIS changelog.
How to reproduce
See above. I have not attempted to do this with other mission data.
The text was updated successfully, but these errors were encountered: