You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For now, the processing of WRF files which don't include the Times variable is not possible even though the data should also be available in the XTIME coordinate. I would propose that we fall back on the XTIME variable if the Times variable is not available.
Implementation
Add this to postprocess.py:_decode_times. Check if XTIME already is a datetime variable and if not, call the default xarray cf decoder.
Tests
Drop the Times variable from the raw dataset before .xwrf.postprocess() and compare both Time coordinates.
Questions
Is there anything we have to make transparent to the users? Like could there be floating-point inaccuracies which warrant a warning?
The text was updated successfully, but these errors were encountered:
Description
For now, the processing of WRF files which don't include the
Times
variable is not possible even though the data should also be available in theXTIME
coordinate. I would propose that we fall back on theXTIME
variable if theTimes
variable is not available.Implementation
Add this to
postprocess.py:_decode_times
. Check ifXTIME
already is a datetime variable and if not, call the default xarray cf decoder.Tests
Drop the
Times
variable from the raw dataset before.xwrf.postprocess()
and compare bothTime
coordinates.Questions
Is there anything we have to make transparent to the users? Like could there be floating-point inaccuracies which warrant a warning?
The text was updated successfully, but these errors were encountered: