It would be use to propagate SATURATION flags to IFU data cubes where relevant. I.e., if a spaxel in the output data cube has NaN science value and DQ=DO_NOT_USE, but WOULD have had values if relevant pixels in the input cal files were not saturated, then set the SATURATION flag in the cube. Aim of this change is to make clear in cubes where there is no data because of saturation vs bad pixels, falling outside the FOV, etc.
I've confirmed that the relevant SATURATION flag is set in the input cal files, so it may be possible to do this as an afterburner to the cube building step. Look for all input cal file pixels in which SATURATION and DO_NOT_USE are set, see where they would map to in the output cube. And for any spaxels with no inputs other than from these pixels, set the SATURATION flag for the spaxel.
This ticket is low priority, and only 'nice-to-have' if it's easy to implement and doesn't negatively impact normal cube building runtimes.
Issue JP-3774 was created on JIRA by David Law:
It would be use to propagate SATURATION flags to IFU data cubes where relevant. I.e., if a spaxel in the output data cube has NaN science value and DQ=DO_NOT_USE, but WOULD have had values if relevant pixels in the input cal files were not saturated, then set the SATURATION flag in the cube. Aim of this change is to make clear in cubes where there is no data because of saturation vs bad pixels, falling outside the FOV, etc.
I've confirmed that the relevant SATURATION flag is set in the input cal files, so it may be possible to do this as an afterburner to the cube building step. Look for all input cal file pixels in which SATURATION and DO_NOT_USE are set, see where they would map to in the output cube. And for any spaxels with no inputs other than from these pixels, set the SATURATION flag for the spaxel.
This ticket is low priority, and only 'nice-to-have' if it's easy to implement and doesn't negatively impact normal cube building runtimes.