chris wrote:I was working on another bug and using Alpha Auriga (Capella) as my test system, when I noticed that the magnitudes of the B component seems wrong. SIMBAD gives it's Vmag as 0.96, but the value in spectbins.ssc is 5.0. Also, the magnitude of ALF Aur A is given as 0.08, which I think is the combined magnitude of both components.
--Chris
This I have documented in spectbins.pl ... and that's why it is so crucial to include these PERL files into the Celestia distribution!
The magnitude of the second component of alpha AUR is missing in Pourbaix' paper. Since I will NOT start to /hand-insert/ numbers from other unnamed sources, and since /we do need a definite value here/, I
arbitrarily have assigned to all these cases mv=5.0.
via this PERL statement:
$mvB=$mvB eq ""?"5.0":"$mvB";
There must have been a good reason why Pourbaix did not use that value which you found in SIMBAD. He certainly knows as well how to exploit this data base
. Lets look a little closer why:
SIMBAD gives
only 2 external sources for Capella B = HD 34029 -----------------------------------------------------------------
CCDM J05168+4559P:
http://vizier.u-strasbg.fr/viz-bin/Vizi ... 68%2b4559P
here
m_V = 2.1 [Edit:] actually m_V=? for the P component
GJ 194B:
http://vizier.u-strasbg.fr/viz-bin/Vizi ... 194%20BBye
here
m_V=0.71
So how did you convince yourself in person that -- in view of this LARGE spread of m_V for just TWO estimates --, there is ANY credibility of the quoted SIMBAD value m_V=0.96??
One day, one might consider merging Pourbaix' catalog with a batch readout of SIMBAD, which is at least an acceptable, quotable algorithm. However, SIMBAD just lists/collects values that have been obtained
somehow without providing an evaluation of their credibility!
I could additionally print a warning in the *.stc data files, whenever some lacking data were encountered...that's easy, but I did not want to vast file space after it's all in the PERL scripts anyway.
Fridger