If AeRes is run with an input catalogue that doesn't have a peak_flux column, then the resulting model sources all have a peak flux that is set to nan. No error/warning is given. The output image is valid, but will contain large regions of nan pixels around the given sources.
It would be preferable if AeRes were able to inspect the input catalogue, decide which columns are required and present and report to the user if columns are missing.
Additionally it would be nice to be able to instruct AeRes which column names should be used for which parameters. eg: using "RAJ2000" instead of "ra", or using "S_200" instead of "peak_flux". This would mean that people wouldn't need to rename columns in order to use AeRes.
If AeRes is run with an input catalogue that doesn't have a
peak_fluxcolumn, then the resulting model sources all have a peak flux that is set to nan. No error/warning is given. The output image is valid, but will contain large regions of nan pixels around the given sources.It would be preferable if AeRes were able to inspect the input catalogue, decide which columns are required and present and report to the user if columns are missing.
Additionally it would be nice to be able to instruct AeRes which column names should be used for which parameters. eg: using "RAJ2000" instead of "ra", or using "S_200" instead of "peak_flux". This would mean that people wouldn't need to rename columns in order to use AeRes.