Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#16 Rejection of CMag values

Defect
closed-fixed
Adam
Tables (18)
9
2010-05-26
2009-08-03
David Benn
No

VStar currently rejects CMag field values of the form 0.ensemb Elizabeth Waagen said via email: "In the Cmag field (magnitude of comparison star) 0.ensemb means that ensemble photometry was done - that is, many comparison stars were used to determine the value of the variable, so a single magnitude cannot be put into the Cmag field. This type of Cmag value will only appear on CCD data, and then not that often."

So I'll fix that.

Discussion

  • David Benn
    David Benn
    2009-09-11

    • milestone: --> Defect
     
  • David Benn
    David Benn
    2010-02-15

    • priority: 7 --> 3
     
  • David Benn
    David Benn
    2010-02-15

    A query shows that only a few obs use this value. Lowering priority. This is not hard to fix though. The field validation would have to permit "0.ensemb" and return the value "Ensemble" for display purposes.

     
  • David Benn
    David Benn
    2010-03-05

    • priority: 3 --> 9
     
  • Adam
    Adam
    2010-03-05

    Do we know of an observation point where this could be replicated?

     
  • David Benn
    David Benn
    2010-03-06

    I'll find one. I should have documented one initially.

     
  • David Benn
    David Benn
    2010-03-06

    I should've added this before.

    Try Epsilon Aurigae between JD: 2454668.94979 and 2454668.95019. I see these in the database, i.e.

    2454668.94979 000-BCT-905 EPS AUR 2.374 0.ensemb
    2454668.95061 000-BCT-905 EPS AUR 3.319 0.ensemb
    2454668.95019 000-BCT-905 EPS AUR 3.134 0.ensemb

    but not all in VStar, presumably since they are being rejected. I would suggest writing a UT to download these and see what you get.

    Thanks.

     
  • David Benn
    David Benn
    2010-03-06

    You could also get an equivalent data file from here: http://www.aavso.org/data/download/ but may not get what you want easily.

    Put these obs into a file and see what VStar does with these.

    2454594.33333,3.0,,,Vis.,SSW,,32,,,,No,,G,,,0.0,EPS AUR,,STD,,
    2454595.32569,3.0,,,Vis.,RZM,,27,32,AAVSO Atlas,,No,,G,,,,EPS AUR,,STD,,
    2454604.57847,3.0,,,Vis.,MDP,S,32,43,sa080329,29 COMP LOST IN OBSTRUCTIONS;BRIGHTER THAN 32,No,,G,,,,EPS AUR,,STD,,
    2454653.84167,3.0,,,Vis.,MDP,LB,29,32,080329,29 COMP FROM AAVSO ATLAS,No,,G,,,,EPS AUR,,STD,,
    2454656.52083,3.0,,,Vis.,SSW,,32,,080330,,No,,G,,,,EPS AUR,,STD,,
    2454657.83819,3.1,,,Vis.,MDP,S,32,29,080329,29 FROM AAVSO ATLAS,No,,G,,,,EPS AUR,,STD,,
    2454668.94979,2.374,,,R,TDW,LK,,,,Observation is average using 5 comp stars: Eta, Zeta, 1 Aur, 2 Aur, Omega,Yes,2.217,G,0.ensemb,,,EPS AUR,,STD,,
    2454668.95019,3.134,,,V,TDW,LK,,,HPO,Observation is average using 5 comp stars: Eta, Zeta, 1 Aur, 2 Aur, Omega,Yes,2.217,G,0.ensemb,,,EPS AUR,,STD,,
    2454668.95061,3.319,,,B,TDW,LK,,,,Observation is average using 5 comp stars: Eta, Zeta, 1 Aur, 2 Aur, Omega,Yes,2.217,G,0.ensemb,,,EPS AUR,,STD,,
    2454668.95104,2.062,,,I,TDW,LK,,,,Observation is average using 5 comp stars: Eta, Zeta, 1 Aur, 2 Aur, Omega,Yes,2.167,G,0.ensemb,,,EPS AUR,,STD,,
    2454674.00694,3.0,,,Vis.,HTN,B,32,29 from atlas,1009gjy,MOON,No,,G,,,,EPS AUR,,STD,,
    2454674.52431,3.05,,,Vis.,SSW,,32,,080330,,No,,G,,,,EPS AUR,,STD,,
    2454675.53611,3.0,,,Vis.,RZM,,27,32,AAVSO Atlas,,No,,G,,,,EPS AUR,,STD,,
    2454675.5563,3.1,,,Vis.,SYI,TO,27,32,,,EPS AUR = 3.05 MAG,No,,G,,,,EPS AUR,,STD,,
    2454675.8,3.1,,,Vis.,MDP,LUB,29,32,080329,MOON UP. HAZY; 29 FROM AAVSO ATLAS,No,,G,,,,EPS AUR,,STD,,

    Right now file obs and database source obs are validated differently, namely file obs are more heavily validated. I intend for that to change in future though.

     
  • David Benn
    David Benn
    2010-03-06

    • assigned_to: david_benn --> adamweber
     
  • Adam
    Adam
    2010-03-25

    Actual display issue is fixed in 445, but there is another issue that all points aren't being displayed.

     
  • Adam
    Adam
    2010-04-13

    • priority: 9 --> 5
     
  • Adam
    Adam
    2010-04-13

    • priority: 5 --> 9
     
  • Adam
    Adam
    2010-04-13

    Prelim marking as fixed. Label change seems complete, awaiting validation and close. New tracker for graph problem.

     
  • Adam
    Adam
    2010-04-13

    • status: open --> open-fixed
     
  • Sara Beck
    Sara Beck
    2010-05-26

    • status: open-fixed --> closed-fixed
     
  • Sara Beck
    Sara Beck
    2010-05-26

    Actually, a value of "0.ensemb" or even "ensemble" for the cmag field is not correct for our database (although I'm not sure what checks are in place to prevent such things). If an observation is done using Ensemble photometry, the word "ENSEMBLE" should be in the comp1_c field and the cmag field should be null. I have fixed the erroneous observations in the database. Sorry to put you to the trouble of changing VStar, David.