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
Sherlock punts for a SN classification as there's a small chance it is truly associated with the nearby galaxy, however, the flux is much more likely to be associated with the underlying stellar source (as in this specific case). I would like to make this information more readily available to human users without changing the top-level 'SN' classification. Lasair, ATLAS and PanSTARRS only report the top-rank classification but they all present the human-readable annotation. This is where I can add some nuanced info.
This is the current annotation for the object above:
The transient is possibly associated with NGC6673; a 12.57 mag galaxy found in the NED_D catalogue. It's located 274.13" S, 78.48" E (14.9 Kpc) from the galaxy centre. A host distance of 10.8 Mpc implies a m - M = 30.17.
But this could instead read:
The transient is most likely associated with 18451763-6222241; a J=14.43 mag stellar source found in the 2MASS/GAIA catalogues. It's located 0.44" N, 0.19" W from the stellar source centre. However, it may possibly be associated with NGC6673; a 12.57 mag galaxy found in the NED_D catalogue. It's located 274.13" S, 78.48" E (14.9 Kpc) from the galaxy centre. A host distance of 10.8 Mpc implies a m - M = 30.17.
The text was updated successfully, but these errors were encountered:
For sources like this one:
https://star.pst.qub.ac.uk/sne/atlas4/candidate/1184517780622221300/
Sherlock punts for a SN classification as there's a small chance it is truly associated with the nearby galaxy, however, the flux is much more likely to be associated with the underlying stellar source (as in this specific case). I would like to make this information more readily available to human users without changing the top-level 'SN' classification. Lasair, ATLAS and PanSTARRS only report the top-rank classification but they all present the human-readable annotation. This is where I can add some nuanced info.
This is the current annotation for the object above:
But this could instead read:
The text was updated successfully, but these errors were encountered: