Closed marianadobre closed 6 years ago
daymet changed the formatting for how the files are returned. There is an extra line with metadata and the column headers changed: year is now YEAR, yday is now DAY.
It fetches in my test script. Didn't have a change to check the interface, but it should work.?
Almost. Got this error:
Error building climate
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/wepppy/weppcloud/app.py", line 1544, in task_build_climate climate.build() File "/usr/lib/python3/dist-packages/wepppy/nodb/climate.py", line 636, in build self._build_climate_observed() File "/usr/lib/python3/dist-packages/wepppy/nodb/climate.py", line 800, in _build_climate_observed data = res.result() File "/usr/lib/python3.5/concurrent/futures/_base.py", line 398, in result return self.get_result() File "/usr/lib/python3.5/concurrent/futures/_base.py", line 357, in get_result raise self._exception File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run result = self.fn(*self.args, **self.kwargs) File "/usr/lib/python3/dist-packages/wepppy/climates/cligen_client.py", line 199, in observed_daymet raise Exception("Encountered error retrieving from cligen") Exception: Encountered error retrieving from cligen
On Wed, Apr 25, 2018 at 1:11 PM, Roger Lew notifications@github.com wrote:
daymet changed the formatting for how the files are returned. There is an extra line with metadata and the column headers changed: year is now YEAR, yday is now DAY.
It fetches in my test script. Didn't have a change to check the interface, but it should work.?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rogerlew/wepppy/issues/67#issuecomment-384418310, or mute the thread https://github.com/notifications/unsubscribe-auth/Aj7cLrJMux_dWTnSBH9HikMxn4XRkATeks5tsNhcgaJpZM4TkAi5 .
Looks like the requests to daymet are failing occasionally. It is implemented so it will retry 10 times (for each hillslope) before giving up.
It's still not working. It gets stuck and won't move on. Doesn't give an error, though.
On Wed, Apr 25, 2018 at 4:41 PM, Roger Lew notifications@github.com wrote:
Looks like the requests to daymet are failing occasionally. It is implemented so it will retry 10 times (for each hillslope) before giving up.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rogerlew/wepppy/issues/67#issuecomment-384467252, or mute the thread https://github.com/notifications/unsubscribe-auth/Aj7cLv_xbpn42KMEWY8KUwU6UOTgFveuks5tsQmdgaJpZM4TkAi5 .
Wha, oh man. Looks like daymet is down.
I'll check it tomorrow to see if it comes back up.
Oh NO! They got some storms in their clouds. :)
Thanks for checking!
On Wed, Apr 25, 2018 at 10:22 PM, Roger Lew notifications@github.com wrote:
Wha, oh man. Looks like daymet is down. [image: image] https://user-images.githubusercontent.com/3652906/39287137-faf9d43c-48d6-11e8-931f-663d1fe2d7e1.png
I'll check it tomorrow to see if it comes back up.
https://daymet.ornl.gov/data/send/saveData?lat=47&lon=-116& measuredParams=tmax,tmin,dayl,prcp,srad,swe,vp&years=1980,1981
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/rogerlew/wepppy/issues/67#issuecomment-384517096, or mute the thread https://github.com/notifications/unsubscribe-auth/Aj7cLv6ojlacAGZ2Hs7PaxwKEWbZp-uEks5tsVmsgaJpZM4TkAi5 .
The daymet requests are sometimes working, but not reliably enough to build all the hillslopes. It looks like the header format reverted to what they had before. Within the last day they update the clients for their single pixel extraction tool to use a new url. I'd say we should avoid using the multiple hillslope for the next couple days and see if they get the bugs sorted out. All the additional requests probably aren't helping.
The single climate might work, some of the time, except for when it doesn't. ;)
Sounds good, Roger! I can use the single climate with Prism adjustments for the class tomorrow.
Thanks for checking on this. M
On Apr 26, 2018, at 10:43 AM, Roger Lew notifications@github.com wrote:
The daymet requests are sometimes working, but not reliably enough to build all the hillslopes. It looks like the header format reverted to what they had before. Within the last day they update the clients for their single pixel extraction tool to use a new url. I'd say we should avoid using the multiple hillslope for the next couple days and see if they get the bugs sorted out. All the additional requests probably aren't helping.
The single climate might work, some of the time, except for when it doesn't. ;)
ornldaac/daymet-single-pixel-batch@bb856da#diff-dbcac071a6d45d89ee4345e21bbd069f
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
daymet observed has been reimplemented to use locally stored .nc4 files.
I am trying to build wepp daymet climates for the Paradise Creek watershed here in Moscow and getting the error below. I've ran it fine last week, though.
https://wepp1.nkn.uidaho.edu/weppcloud/runs/mdob0443-91e8-474d-a1c7-b434e068b803/0/
Error building climate
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/wepppy/weppcloud/app.py", line 1544, in task_build_climate climate.build() File "/usr/lib/python3/dist-packages/wepppy/nodb/climate.py", line 636, in build self._build_climate_observed() File "/usr/lib/python3/dist-packages/wepppy/nodb/climate.py", line 758, in _build_climate_observed lng=ws_lng, lat=ws_lat File "/usr/lib/python3/dist-packages/wepppy/climates/cligen_client.py", line 199, in observed_daymet raise Exception("Encountered error retrieving from cligen") Exception: Encountered error retrieving from cligen