You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This looks like the other way around, the association is good between those points, but somehow the forced fits has been done in the wrong location and attached to that source.
My guess is a bug in the ideal source coverage calculation, or a bug in the forced fits process that has got ID's crossed.
Edit: Suspicious that it's around RA 0, RA wrapping handling maybe?
It seems to only occur for 3 sources out of the ~2M in the run: 43885418, 43891486,44717001.
All three are close to RA 0 for their detections, but all have forced fits measurements that are nowhere near where the detections are (74deg, 335deg and 164deg).
https://dev.pipeline.vast-survey.org/sources/44717001/
This source has two measurements from a completely unrelated source included. The declination is roughly consistent, but the RA is off by >160 deg.
I have no idea what would cause this, especially since there's two other measurements of the same coordinates associated with a different (correct) source: https://dev.pipeline.vast-survey.org/sources/44332471/
The text was updated successfully, but these errors were encountered: