Previously gtexpcube would fill unused pixels in the square exposure map image with nulls, which indicated that those pixels had no value. gtexpcube2 by default fills them with zeros, so it is difficult to differentiate between a valid pixel with a value of 0 and a pixel which is outside the sky ellipse.
Could gtexpcube2 be updated to use the old default of filling unused pixels as nulls instead of zeros? This would be preferable since it is easy to change nulls to zeros if needed but it is much harder to decipher which zeros should be ignored or made null.
As reported by Julie McEnery:
Previously gtexpcube would fill unused pixels in the square exposure map image with nulls, which indicated that those pixels had no value. gtexpcube2 by default fills them with zeros, so it is difficult to differentiate between a valid pixel with a value of 0 and a pixel which is outside the sky ellipse.
Could gtexpcube2 be updated to use the old default of filling unused pixels as nulls instead of zeros? This would be preferable since it is easy to change nulls to zeros if needed but it is much harder to decipher which zeros should be ignored or made null.