Closed mgalloy closed 11 months ago
Level 1 data are totally unmasked.
The geometric mask (occulter & post) will be applied to all level2 data. How much shall we over-mask the occulter? If we mask the outer fov, at what radius shall we start masking?
We need to decide if and how to mask the levels 2 data for noise in the commissioning reprocessing.
Users asked for less masking. We can mask the fit extensions for noise or leave all pixels unmasked and add an extension with a noise mask. The mask can be a binary mask(s) or a quality mask, i.e. the photon noise at each pixel. We do not need to have the final mask ready for commissioning (we can do the noise computation later) but need to decide on the format so Mike can set this up.
The mask extension present if l2/mask_noise
is not set:
level2$ ucomp cat 20220915.180903.ucomp.1074.l2.fts
1 Center wavelength intensity science ----- 1074.70 -----
2 Enhanced intensity science ----- 1074.70 -----
3 Peak intensity science ----- ----- -----
4 LOS velocity science ----- ----- -----
5 Line width (FWHM) science ----- ----- -----
6 Noise mask science ----- ----- -----
7 Weighted average I science ----- ----- -----
8 Weighted average Q science ----- ----- -----
9 Weighted average U science ----- ----- -----
10 Weighted average L science ----- ----- -----
11 Azimuth science ----- ----- -----
12 Radial azimuth science ----- ----- --—-
Added extension place and name to documentation for #154.
Instead of masking, add a mask extensions to the FITS files.
l2/mask_noise
should be set to "NO" to add "Noise mask" extension