Skip to content
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

question on GFS forecast data #243

Open
jianjun5212 opened this issue Mar 21, 2025 · 0 comments
Open

question on GFS forecast data #243

jianjun5212 opened this issue Mar 21, 2025 · 0 comments

Comments

@jianjun5212
Copy link

I am a new user and have some question:

—-----------------------------------------------------------
In .yaml file:

dates:
start: 2021-03-23 00:00:00
end: 2022-01-01 18:00:00
frequency: 6h

input:
grib:
path:/gfs.{date:strftime(%Y%m%d)}/{date:strftime(%H)}/atmos/gfs.t{date:strftime(%H)}z.pgrb2.0p25.f072

In grib.py, the line s = s.sel(valid_datetime=dates, **kwargs) encounters an issue because dates correspond to the start date (e.g., 2021-03-23T00:00:00), whereas valid_datetime represents the GFS forecast lead time date (e.g., 2021-03-26T00:00:00 for a 72-hour lead time). This discrepancy results in len(s) == 0. How can I align the start date with the file_name date to correctly select the data?

How can I specify different lead times in the config file using a range of values, such as lead_time: [24, 48, 72, 96]?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant