-
Notifications
You must be signed in to change notification settings - Fork 169
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
Findfeatures - PVL group [Results] Error #4375
Comments
This bug does not seem to have been fixed in ISIS 5.0.1. Test case: (Note that I've tried this on actual image data and gotten the same result, pun mostly intended)
I do seem to actually have ISIS 5.0.1, and the changelog claims this has been fixed:
|
Can confirm locally - the bug still exits under isis5.0.1 |
It looks like the fix for this (#4399) didn't get moved over to the 5.0.1 branch. We will need to pull a 5.0.2 that contains this fix and any other bug fixes we've merged since 5.0.2. I'm not sure of when we'll have time to get to that, but I'll make sure I update over here when we do. |
Any update on if this will be cherry picked back to 5.0.1 and if it will be included in 6.0? |
I see that it was included in 5.0.2. I assume this minor tick won't be available in conda until the next release. Is this correct? |
It does seem that this has been fixed in ISIS 5.0.2 and ISIS 6.0.0 RC1. My test case above runs correctly in both, with no error message and a successful return code. |
This is available in both 5.0.2 and 6.0.0-RC1 (will be in 6.0.0 upon full release). |
ISIS version(s) affected: 4.4.0
Description
Findfeatures runs and generates output files but produces the following errors when doing so:
This is the case for isis4.4.0 but not prior versions. I compared the output files from isis4.3.0 and isis4.4.0 and everything is essentially the same (processing times for steps vary) including the output networks which are identical.
Other then the error message I'm not sure if this negatively effects the output.
I'll run under isis4.3.0 in case I'm missing something.
How to reproduce
See test data under /work/users/lweller/Isis3Tests/FindFeatures/PVLResults/
The images N1590648465_1.sharp.dck.cub and N1604395063_1.sharp.dck.cub are input to the command found in run_ff.cmd.
Everything else in the directory is output from the program.
The subdirectory Isis4.3.0/ contains the input/output for a no error run under isis4.3.0.
The text was updated successfully, but these errors were encountered: