If there is a shear catalog calculated with a particular method - it is useful to be able to see in the generated products that use this catalog, what the details of the catalog were. As there is no guarantee of the form of the fits header of the she catalog, we should allow the user to add any metadata key to the catalog object and then allow this to be propagated when mapping, transforming, calculating spectra and ensure the heracles write methods contain this data in the fits header.
More generally, in the case where there particular information about our catalog we want to
- Be able to add that data to the catalog and
- Ensure the data is within the downstream products (maps, alms, cls, mms and covariances)
- Ensure when writing these products the data is in the fits header
This will require:
- Adding a data object to the catalog that can be added to, possibly in the constructor or another method.
- Updating the mixing matrices (and possibly covariance) methods to use this data (currently meta data from maps is added to alms and spectra but not mms)
- Double checking the files written contain the required information, but only for the catalog keys (i.e. SHE) where it is used.
If there is a shear catalog calculated with a particular method - it is useful to be able to see in the generated products that use this catalog, what the details of the catalog were. As there is no guarantee of the form of the fits header of the she catalog, we should allow the user to add any metadata key to the catalog object and then allow this to be propagated when mapping, transforming, calculating spectra and ensure the heracles write methods contain this data in the fits header.
More generally, in the case where there particular information about our catalog we want to
This will require: