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
First of all, let me say that I don't think this is an issue. The variable data seems to be the same! However, the differing time axis attributes—and/or maybe something else causing YEAR to not be parsed by ncdump—did confuse me for a while, so it might be worth considering making these consistent.
In the CLM flanduse_timeseries file, the YEAR variable is the actual year.
First of all, let me say that I don't think this is an issue. The variable data seems to be the same! However, the differing time axis attributes—and/or maybe something else causing
YEAR
to not be parsed byncdump
—did confuse me for a while, so it might be worth considering making these consistent.In the CLM
flanduse_timeseries
file, theYEAR
variable is the actual year.However, in the FATES
fluh_timeseries
file it's more complicated. This can't be inspected usingncdump
for some reason:However,
xarray
can see it if you tell it not to decode times:The text was updated successfully, but these errors were encountered: