Closed DanielAndreasen closed 7 years ago
Hi Daniel,
great to hear from you and thanks for reporting.
Honestly, I have been aware of this bug. As far as I can say, the reason for this is that the VO table currently provided by exoplanet.eu is not entirely standard compatible because, as you see in the error message, "Yes" is not a valid boolean value, and astropy does not handle this smoothly (well, it does the right thing actually). I contacted exoplanet.eu about this issue, but I have not heard something so far. So maybe it is not a general issue or I am simply not right in my evaluation.
At any rate, I had hoped that the issue would not require a tailored solution from my side. Yet, I start to see the necessity now. I will look into this and see that I can provide a solution soon!
Stefan
Hi again,
this was quicker than I expected. I just pushed a commit, which should resolve the issue. Invalid columns are now masked, which prevents an error. However, quite a few values (in particular, nonexisting) will also be masked. I think this is a change in behavior compared to the previous situation.
I hope that helps! Stefan
Hi again,
I just tested this, and it works. I had to rename some stuff (names of columns are slightly different), but at least I can get the data again. Thanks for the quick fix.
Daniel
Hi,
great.
I also looked at the "old" class (ExoplanetEU), which stopped working. Obviously, the mechanism for downloading the data ceased to work for the CSV data, due to a change on the server side, and I could not (quickly) come up with a working alternative (still works for the votable format, and I hope that will continue). So unfortunately, this is seems to be beyond repair for the moment.
Stefan
Yes, I understand it is out of our hands. I think you can close this issue though. The VOtable is working again.
Daniel
Hi Stefan,
I get a rather long error message when I try to run
pyasl.ExoplanetEU2()
. See below.As a sidenote, the link for
pyasl.ExoplanetEU
doesn't work anymore: http://exoplanet.eu/catalog/csvI add @sousasag to the conversation as he was the one who found the bug.