[vsnet-newvar 809] re HadV81 &/or NSV 11337

[crawl@zoom.co.uk]

Some time ago I came across a situation where a 2000.0 NSV position was an
updated one from the original catalogue's "1950" position, but in fact when
the literature was checked, the original position was quoted for equinox
and epoch of 1909 when the paper was published.  Using the proper epoch it
turned out that a "new" variable found near this nsv object was actually
the nsv.  Unfortunately, I can't remember the example.

However, it can be reasonably assumed that the original NSV position will
have been quoted as a 1950 one.  If there was an error of transcription,
and someone forgot to precess the original published position to 1950
before placing it in the catalogue, then it might be a thought to reverse
calculate what epoch & equinox these two positions would be coincide...
...if you follow what I'm trying to say.

Though not a common occurrence, as I say, I've seen an instance or two, so
I'd suggest this as an automatic test for all "new" variables that are
found mostly due east of an NSV object, especially if that value is near 50
or 75 years worth of RA precession [ie, the original position was quoted as
1900 or 1875 respectively, but was unfortunately catalogued as 1950 in the
original CVS or wherever, whilst not having actually being converted to said].

Cheers

John

VSNET Home Page

Return to Daisaku Nogami

---

vsnet-adm@kusastro.kyoto-u.ac.jp