David Turner

Tracked it down to one source 'ILTJ110447.73+381733.6' I think. Though I still don't understand _why_ this happening.

When I took a look at the spectrum command being generated for one of the failed spectra that give the error, it seems pretty obvious: cd /mnt/lustre/projects/astro/general/dt237/judith_agn_explore/xga_output/0136541101/mos1_ILTJ110447.73x381733.6_temp_51999263/; cp ../ccf.cif .;...

For context, these show the masks for contaminating regions:  And the R500 region: 

I guess one solution that might help a lot is to round the detector coordinate region positions/sizes??

I have started on this now - first step was essentially just copying the [overdensity_radius method of HydrostaticMass profile](https://github.com/DavidT3/XGA/blob/987afe8106294e11631ce5b8b39876c06f63284a/xga/products/profile.py#L1626). This measures a set of masses within user-specified radius brackets, in...

Looking at a few of the radii coming out, they are making some sort of sense, so that's good

The first-pass-pipeline (say that five times fast) ran through okay, handling some sources dropping out and producing sensible-ish looking radii: {'LoVoCCS-4B': [1000.0], 'LoVoCCS-5': [1000.0, 1031.5, 1000.5, 1030.5, 1000.5], 'LoVoCCS-7': [1000.0,...

Must extend the question of how to include radius uncertainties to the 'overdensity_radius' method of the hydrostatic mass profile as well.

I will do two things for this - first AnnularSpectra will not require that each annulus has an entry for each ObsID inst combo associated with the AnnularSpectra. Honestly this...

I think I'm also going to add a try except to the reading in step - to ensure that redeclaring samples can actually go ahead in times like these