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
Lots of things to think about with displaying and using object names; here's one thought (and maybe this should be a general bug for this issue):
I happened to come across 2001ApJ...549..554A which is Chandra, EUVE, HST, and VLA Multiwavelength Campaign on HR 1099: Instrumental Capabilities, Data Reduction, and Initial Results and has two objects associated with it
Now, for the CCDM ... name, I would think that we could say 'aha; SIMBAD returns a version with "NAME xxx" so let's pick that one as our canonical name', assuming of course you only get one NAME version and dropping the NAME prefix.
The text was updated successfully, but these errors were encountered:
Lots of things to think about with displaying and using object names; here's one thought (and maybe this should be a general bug for this issue):
I happened to come across 2001ApJ...549..554A which is
Chandra, EUVE, HST, and VLA Multiwavelength Campaign on HR 1099: Instrumental Capabilities, Data Reduction, and Initial Results
and has two objects associated with itCCDM J05168+4559AP
which is aka Capella; you notice there's a
NAME Capella
result from SIMBADV* V711 Tau
which is the eponymous
HR 1099
Now, for the
CCDM ...
name, I would think that we could say 'aha; SIMBAD returns a version with "NAME xxx" so let's pick that one as our canonical name', assuming of course you only get one NAME version and dropping theNAME
prefix.The text was updated successfully, but these errors were encountered: