WebObs Y2018 bug!

Announcement: New Forums

We are excited to announce the launch of our new forums! You can access it forums.aavso.org. For questions, please see our blog post. The forums at aavso.org/forum have become read-only.

Announcement: New Applications

We are excited to announce the launch of our new applications! We're opening up early access to our new applications for searching, downloading, and submitting photometric observations. You can now access these applications through these links:

• Global Data Search (new) – Search across all of AAVSO’s databases

• Search and Download Photometric Observations – Search and export results in CSV, JSON, or XLSX

• Submit Photometric Observations – Review your observations on a light curve with historical data

We ask for your feedback in order to help us improve these applications. Please send feedback for the applications above to feedback@aavso.org. Note: please avoid duplicating submissions across the two submit applications.

Affiliation

American Association of Variable Star Observers (AAVSO)

Mon, 01/01/2018 - 05:47

Deja vu tonite, I tried my usual method of calender date format entry for my obs as 2018/01/01/hh/mm and it bombed out with a date error! I was able to get it to work if I convert to JD, but still there is a problem.

Happy New Years...

Mike

pukemaru

Affiliation

Royal Astronomical Society of New Zealand, Variable Star Section (RASNZ-VSS)

Mon, 01/01/2018 - 11:03

WebObs Y2018 bug

Mike, it must be fixed. I just tried entering an observation in that format and it worked.

Cheers

Stephen [HSP]

SGEO

Affiliation

American Association of Variable Star Observers (AAVSO)

Tue, 01/02/2018 - 03:48

Y2018 webobs error

Mike,

Please send me the file that faulted in webobs so I can track down this error.

Thanks,
George
SGEO@gasilvis.net

lmk

Affiliation

American Association of Variable Star Observers (AAVSO)

Tue, 01/02/2018 - 03:55

It wasn't a file, it was an

It wasn't a file, it was an individual visual observationon Q Cyg, I entered the date/time as 2018/01/01/05/25 and it said "date must be after 1913" or something like that, but when I converted to JD it worked. I just tried the calendar date again right now and it works! So, whatever it was it was a transient problem...

Mike