David Turner
David Turner
They just retrieve the combined ratemap, no matter what the input to the temperature profile generation function might have said. This is one of the functions I mean: https://github.com/DavidT3/XGA/blob/69546155c88aa297fcf5b4e1ee760a6d6559ef50/xga/sourcetools/temperature.py#L198
Take the peak finding for instance - particularly with Chandra and eRASS data, it is pretty likely that there _won't_ be a combined ratemap to access, because there is only...
This has never really been necessary because we're just running a script, but I've noticed (as we've worked on Chandra support) that installing CIAO through a conda environment ends up...
Once spectra can be generated, in theory the fitting of models to spectra using XGA's XSPEC interface should just work, and in turn things like being able to measure density...
This part of the project deals with the implementation of XGA wrappers for the CIAO routine(s?) required to make 'photometric' data products - note that 'photometric' isn't really a term...
This won't be possible until I can get DAXA to make region files from Chandra images, but when it is you'll need to alter your configuration file to point at...
This is obviously a bad thing, but was an oversight on my part - the gas mass and mass calculations can both already account for radius uncertainty - just need...
This function (on_detector_match) is a way of finding out which (if any) of a large set of source coordinates fall on a detector for any of the observations in the...
The docstrings of property setters are ignored by sphinx autodoc, only possible 'solution' I've found is: https://stackoverflow.com/questions/71713284/types-of-setter-arguments-not-showing-in-sphinx-documentation Don't know how I missed this over the last 2 years!
Explain the use of abstract base classes, how you would define your own model, how you would fit your own custom model