-
Notifications
You must be signed in to change notification settings - Fork 1.1k
pvlib.forecast has stopped working #1423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@DavidLloydNGP I've seen that error when an empty file is returned by the THREDDS server. In this case, the error occurs on this line. (I ran your code in the Spyder debugger). A few lines earlier, the This appears to be a THREDDS issue. Perhaps pvlib could return a more informative error somehow. |
Thanks @cwhanse for that. Subsequent to my post, I had even tried running the code in a new virtual environment, hoping it was a problem with another library but I received the same error. I think this supports your analysis that something is amiss further upstream with THREDDS. I managed to 'solve' this problem by bypassing pvlib and using siphon directly to access GFS data. For instance, to download the wind data for the next 24 hours for Greenwich, London:
I have done a few non-exhaustive checks and the data obtained this way seems identical to data I had previously downloaded using pvlib. Given the pvlib forecast function always came with a 'highly experimental' warning anyway, I think I am going to stick with the siphon approach, even it requires a little more coding on my part to replicate the ease of pvlib. |
FWIW the example code at the top of this thread seems to work again. Still worth considering a nicer error message though. |
THREDDS appears to be working (at least today it is). Closing in anticipation on #1426 |
Hi,
The example code for importing a forecast from GFS has stopped working for me.
returns an error now:
python version is 3.8 and numpy version is 1.21.2.
Has anyone else encountered this problem?
I was able to read in forecasted data without problems previously but I don't know what's changed between then and now.
Thanks,
David
The text was updated successfully, but these errors were encountered: