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

[fix] analysis -> point in time #8

Merged
merged 3 commits into from
Jun 25, 2024
Merged

[fix] analysis -> point in time #8

merged 3 commits into from
Jun 25, 2024

Conversation

hrodmn
Copy link
Collaborator

@hrodmn hrodmn commented Jun 24, 2024

Tag all layers where forecast_valid == 'analysis' as point_in_time to facilitate better datacube structure.

@hrodmn hrodmn self-assigned this Jun 24, 2024
@abarciauskas-bgse
Copy link
Contributor

abarciauskas-bgse commented Jun 24, 2024

@hrodmn thanks for making this change. Just to make sure I understand, was the original intent of point_in_time to distinguish between data produced for forecast hour 0 vs all other files (forecast hour 1+), but the underlying metric is the same? In this case, do we need the point_in_time suffix at all? I see that the other forecast "types" (cumulative, summary) are different enough that point in time makes sense).

I noticed for wind speed, there are "instantaneous" variables for forecast hour 0 and periodic max for all other hours. I would assume these are different metrics so I'm wondering how I should annotate that in the UI 🤔

@hrodmn
Copy link
Collaborator Author

hrodmn commented Jun 24, 2024

Just to make sure I understand, was the original intent of point_in_time to distinguish between data produced for forecast hour 0 vs all other files (forecast hour 1+), but the underlying metric is the same? In this case, do we need the point_in_time suffix at all? I see that the other forecast "types" (cumulative, summary) are different enough that point in time makes sense).

Yeah, many of the variables have forecast_valid values that reflect some statistic about a specific range (periodic), or from hour zero to time x (cumulative). The values like 3 hour fcst represent conditions at a specific point in time (I think).

I noticed for wind speed, there are "instantaneous" variables for forecast hour 0 and periodic max. I would assume these are different metrics so I'm wondering how I should annotate that in the UI 🤔

I am not really sure what the "instantaneous" observations mean. I labeled them this way when the forecast_valid string is something like 0-0 day max (see https://www.nco.ncep.noaa.gov/pmb/products/hrrr/hrrr.t00z.wrfsfcf00.grib2.shtml which that shows those rows in the inventory table). Maybe that is a bad label. Since those values only appear in FH 0 maybe it would make sense to skip them for the UI.

@hrodmn hrodmn changed the title Analysis point in time [fix] analysis -> point in time Jun 25, 2024
@hrodmn hrodmn merged commit 0d29e29 into main Jun 25, 2024
5 of 6 checks passed
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

Successfully merging this pull request may close these issues.

2 participants