Return to Home Page
Very well, then, I will assign my own designation to this variable pending GCVS: LinV2312 (for Linnolt Variable 23h +12) Any objections? Mike On Thu, 25 Sep 2003, Seiichi Yoshida wrote: > Dear Michael Linnolt, > > [vsnet-newvar 2222]: > > Has there been a designator assigned yet to this new variable? > > Mike, please show us the proper designation, because this is your > variable star :-) > > I do not know about AAVSO. But the VSNET does not show us the > "official" designation. So if the discoverers of new variable stars > want to collect observations from people, it is the discoverers' > responsibility to provide the designation, I believe. > > In the case of the MISAO Project, we assign our own designation like > MisV0001. > > In the case of the TASS Project, they report their stars with GSC > numbers or HD numbers, so the other people should report the > observations using those numbers. > > In your own case, the USNO-B1.0 number can be one of the > designations. > > Of course it is a temporary designation, until the GCVS number is > assigned. But it takes some time, of course. > > Only in the case of a new nova, Kato-san leads us to use a common > temporary designation, like OPHnova2003, soon after the discovery. But > it is an exceptional case. The principle seems as same as the CBAT to > me. I mean, only a nova is deal well. > > I know everyone does not want to pay attention for > designation. Sometimes a new star is remained without any proper > common designation, like in this case. In such cases, I think the > VSNET administrators should take a leadership role in assigning the > designation. But actually, they do not. Maybe that means the VSNET > does not want us to observe the star and report them to VSNET to be > collected into the VSNET database... > > Best regards, > > -- > Seiichi Yoshida > comet@aerith.net > http://vsnet.aerith.net/ >
Return to the Powerful Daisaku
vsnet-adm@kusastro.kyoto-u.ac.jp
