X-ray: Generate and Analyse is a module designed to make the analysis of XMM observations simple and efficient. It provides an interface with SAS for the creation of XMM data products, as well as a way to easily perform fits (scalable for multiple observations) and retrieve information about an object, all within a Python package.
BSD 3-Clause "New" or "Revised" License
30
stars
3
forks
source link
Alter RateMap product class so that it can read a count rate map from file as well as make them out of an image and exposure map #1251
Count-rate maps are widely used by XGA - some of those uses will be phased out and replaced by using flux maps at some point but we won't make big structural changes yet.
As you know the flux_image CIAO tool can make count-rate map files - those files wouldn't currently be of any use to XGA, as the 'RateMap' product class is always set up from an existing XGA image and exposure map instance, then it takes those data arrays (read from the image and exposure map files) and divides one by the other to make a ratemap.
We should alter the RateMap class so that it can either be setup in the original XGA way, or simply read in from a file.
I don't actually know if we'll add the ratemap paths to the configuration file, as it already works fine - but this would give people the option of using an XGA ratemap instance to interact with their 'flux_image' generated file if they wanted.
We should also check that the XGA made and flux_image made ratemaps are the same.
Count-rate maps are widely used by XGA - some of those uses will be phased out and replaced by using flux maps at some point but we won't make big structural changes yet.
As you know the flux_image CIAO tool can make count-rate map files - those files wouldn't currently be of any use to XGA, as the 'RateMap' product class is always set up from an existing XGA image and exposure map instance, then it takes those data arrays (read from the image and exposure map files) and divides one by the other to make a ratemap.
We should alter the RateMap class so that it can either be setup in the original XGA way, or simply read in from a file.
I don't actually know if we'll add the ratemap paths to the configuration file, as it already works fine - but this would give people the option of using an XGA ratemap instance to interact with their 'flux_image' generated file if they wanted.
We should also check that the XGA made and flux_image made ratemaps are the same.