Opened 18 years ago
Closed 18 years ago
#1106 closed enhancement (fixed)
mask names and values must be saved and used in images
| Reported by: | eugene | Owned by: | Paul Price |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | config | Version: | unspecified |
| Severity: | minor | Keywords: | |
| Cc: |
Description
We currently define the value for named mask bit fields only in the recipe file 'masks.config'. This recipe should be used when assigning new mask values (eg, in ppMerge, or in ppImage for bits set by pmReadoutSetMask and related functions in pmFPAMaskWeight.c. However, if we load in a mask image, we need to be sure we will respect the values set in that image. Thus, we should (a) save the relationship between the named mask bits and their values in the output mask images and (b) read those values when we load the mask image, over-ridding the existing names in the masks.config recipe file.
In a related vein, the ppImage.config values for MASK.VALUE (ie, what bits to respect) needs to be thought through and made consistent and complete. We also need to define the DARKMASK and FLATMASK recipes for ppMerge to set the correct bits -- currently, both seem to yield a value of 68 (0x44)
I think you addressed this bug in your recent mask fix.