Open ddobie opened 4 months ago
Origin of this is that for whatever reason, some selavy sources have zero astrometric uncertainty. These should probably be padded in some way (e.g. at post-processing we should set a minimum astrometric uncertainty) but in the meantime it's possible to get around this by just setting the ra_uncertainty and dec_uncertainty to some small number.
The latest post-processing code will account for the systematic uncertainty in the ASKAP positions, so we can now set ra_uncertainty and dec_uncertainty to zero.
However, this breaks the pipeline:
I have tested the same data with ra_uncertainty and dec_uncertainty set to 1.0 (the default) and 0.0, and the error only seems to occur with 0.0.
My assumption is that these values are converted to weights somewhere (i.e. 1/uncertainty) which then results in NaN values. Maybe here: https://github.com/askap-vast/vast-pipeline/blob/6209e0d7b1431068869cb917ed6c4e8501aa0c52/vast_pipeline/image/main.py#L435-L456