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
While working on setting up sflux ensemble based on HAFS and GEFS I realized that if the sflux "input" files (e.g. what I generate from HAFS or GEFS) then pyschism incorrectly shifts the time vector:
This is because the schism sflux time hour 00 based, but the vector differences for sflux_*.nc file are calculated based on the actual input .nc file's base time. So for example if I have the following time vector in my custom input nc file:
I know that I'm using custom input .nc file as SfluxDataset, but still I'm not sure if this is intentional (i.e. I need to make sure my input .nc file dates are 00 based) or a bug!
Note that I call this function to read the custom .nc file I generate from HAFS or GEFS:
While working on setting up
sflux
ensemble based on HAFS and GEFS I realized that if thesflux
"input" files (e.g. what I generate from HAFS or GEFS) thenpyschism
incorrectly shifts the time vector:pyschism/pyschism/forcing/nws/nws2/sflux.py
Lines 331 to 338 in 00b1137
This is because the schism sflux time hour
00
based, but the vector differences forsflux_*.nc
file are calculated based on the actual input.nc
file's base time. So for example if I have the following time vector in my custom inputnc
file:then I get the following time in the final sflux file
sflux_air_1.0001.nc
written by pyschism:I know that I'm using custom input
.nc
file asSfluxDataset
, but still I'm not sure if this is intentional (i.e. I need to make sure my input.nc
file dates are00
based) or a bug!Note that I call this function to read the custom
.nc
file I generate from HAFS or GEFS:pyschism/pyschism/forcing/nws/nws2/nws2.py
Lines 35 to 41 in 00b1137
Is this not meant to be used on a generic
.nc
file? My.nc
file has all the required variables, it just doesn't have hour00
based time.The text was updated successfully, but these errors were encountered: