[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]
[vsnet-chat 4411] (fwd) Re: constellation-preceded names
- Date: Sun, 6 May 2001 10:26:10 +0900 (JST)
- To: vsnet-chat, vsnet-gcvs
- From: Taichi Kato <tkato>
- Subject: [vsnet-chat 4411] (fwd) Re: constellation-preceded names
- Sender: owner-vsnet-chat@kusastro.kyoto-u.ac.jp
(fwd) Re: [vsnet-chat 4391] Re: constellation-preceded names
Date: Sat, 05 May 2001 07:23:31 -0700
From: Thom Gandet <tgandet@mindspring.com>
Dear Taichi,
> Again, it is not a problem if this is used as metacodes, or personally.
> However, it looks the usage (I think it improper) of constellation names
> prceding other catalog names is becoming more and more prevalent.
> Who, or what is system, is responsible for that??
I agree with you - constellation names should not preceed other
designators, especially the designators that contain coordinates.
This practice is now being carried over to variable stars, where the
constellation name comes first. This makes sorting by computer
easier, but reading them in a list of observations of several stars is
very difficult I think.
> But, a simple question - why the CDS system requires constellation
> names for already cataloged objects? People may wish to look for
> the data of 3C273, but in order to get them, they must know that
> the object is in Virgo constellation.
If you're referring to the SIMBAD query page, then you can enter
the object's name without the constellation. Entering just 3C273
worked when I tried it.
Hope this helps.
Cordiallly,
Thom Gandet
--
************************************************************************
Lizard Hollow Observatory
Thomas L. Gandet, Director
PO Box 77021
Tucson, AZ 85703-7021 USA
************************************************************************
Return to Daisaku Nogami
vsnet-adm@kusastro.kyoto-u.ac.jp