ciss2isis - dealing with input saturated pixels
High saturation pixels are now ingested as HRS instead of HIS in ciss2isis
Upon conversion to ISIS3 from PDS, should an input (high) saturated pixel be assigned "HIS" at ingestion and not "HRS"? or low saturated pixel be assigned LIS?
ciss2isis from=/pds_san/PDS_Archive/Cassini/ISS/coiss_2014/data/1500060254_1500210689//W1500063766_2.LBL to=W1500063766_2.cub
#1 Updated by Tammy Becker 7 months ago
I'm referring to the ISIS3 definition of special pixel values:
HIS/LIS are instrument saturated pixel...they are not introduced by any ISIS application
HRS/LRS are saturated pixel values introduced by an ISIS application
#4 Updated by Summer Stapleton 3 months ago
Hi Tammy, unfortunately there is no way to decipher between a null value and an LIS value at ingestion due to the image file being treated as an 8-bit, but it looks like you might be right about HIS needing to be assigned instead of the HRS, so that will be corrected.
You have a relative path to an image file that can be used to test this; is it possible to get the full path? Thank you!
#5 Updated by Tammy Becker 3 months ago
Thank you for looking into the low range values. It will have to remain NULL then.
I'm glad that HIS is possible, it is the most likely value tracked.
I've copied the mentioned PDS input image to:
Just an FYI, the /pds_san path can be seen from a user machine, like astrovm4.