Saw this with ASASSN-17hx in which an observation had an uncertainty value of "Y".
e.g. https://www.aavso.org/vsx/index.php?view=api.object&ident=000-BMJ-092&data=1000&fromjd=2457240.5&tojd=2457971.5&att&where=mtype%3D0+or+mtype+is+null&page=1, around row 15.
Making VSX web service more robust in the presence of such uncertainty values by not including observations containing such errors.
Actually, defaulting to zero uncertainty to distinguish between zero and no valid uncertainty read.
Sara recently reported another star for which this happens:
SN 2017eaw (i.e. 000-BMH-324)
It works with this now but fails for 2.19.0 with the same error.
Fixed in 2.20.0
Log in to post a comment.
e.g. https://www.aavso.org/vsx/index.php?view=api.object&ident=000-BMJ-092&data=1000&fromjd=2457240.5&tojd=2457971.5&att&where=mtype%3D0+or+mtype+is+null&page=1, around row 15.
Making VSX web service more robust in the presence of such uncertainty values by not including observations containing such errors.
Actually, defaulting to zero uncertainty to distinguish between zero and no valid uncertainty read.
Sara recently reported another star for which this happens:
SN 2017eaw (i.e. 000-BMH-324)
It works with this now but fails for 2.19.0 with the same error.
Fixed in 2.20.0