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

New SFS products requested from CPC #887

Open
4 of 6 tasks
WenMeng-NOAA opened this issue Mar 6, 2024 · 10 comments
Open
4 of 6 tasks

New SFS products requested from CPC #887

WenMeng-NOAA opened this issue Mar 6, 2024 · 10 comments
Labels

Comments

@WenMeng-NOAA
Copy link
Collaborator

WenMeng-NOAA commented Mar 6, 2024

Request from CPC:

  • 200-hPa velocity potential
  • streamfunction
  • Helicity" (HLCY3000_0m, 0-3000 m above ground)
  • Total sky downward direct radiation at the surface
  • subsurface runoff
  • temporal max wind at 10 m

On 02/12/2024, CPC requested the following new variables in the SFS product list:

Requests:

"vertical velocity" in pressure coordinates (for diagnosing the maintenance of 3-D atmospheric circulation anomalies)

"200-hPa velocity potential" and "streamfunction" (for MJO predictions and for diagnosing atmospheric circulation anomalies)
“subsurface runoff” (variable name is “drain” in the Noah-MP land surface model) (for calculation of Standardized Runoff Index, a key indicator for hydrological drought)
"Helicity" (HLCY3000_0m, 0-3000 m above ground) (for several weather tool)
Total sky downward direct radiation at the surface" (for calculating Universal Thermal Climate Index (UTCI) and other Excessive Heat Indices)

@WenMeng-NOAA
Copy link
Collaborator Author

On 02/13/2024, @HuiyaChuang-NOAA commented CPC's request:

  • "vertical velocity" in pressure coordinates

we are planning to retire omega and ask stakeholders to switch to w. This is because nonhydrostatic FV3's prognostic variable is w but UPP computes omega using hydrostatic equation to support users who couldn't switch right away

@yangfanglin
Copy link

@WenMeng-NOAA @HuiyaChuang-NOAA We will likely use the hydrostatic dycore option for running SFS. Xiaqiong Zhou can comment if omega can be (should be) used for SFS.

@WenMeng-NOAA
Copy link
Collaborator Author

@WenMeng-NOAA @HuiyaChuang-NOAA We will likely use the hydrostatic dycore option for running SFS. Xiaqiong Zhou can comment if omega can be (should be) used for SFS.

@yangfanglin That's great. We will hold off this variable added in SFS product list until Xiaqiong give us a greenlight. There might be some changes at UPP side.

@WenMeng-NOAA
Copy link
Collaborator Author

On 03/08/2024, CPC added a new request as:

Wanqui stopped by last Friday and asked that we add temporal max wind at 10 m
in SFS v1 output.

Wen and I just talked and we agreed since RRFS v1 outputs hourly max wind, we can
send a request to the modeling team to see if this feature can be added for SFS/GFS.
Keep in mind that the bucket for GFS is currently 6 hours.

We will follow up with the modeling team at the next SFS meeting or prior to it.

There are efforts needed at model side to output 6-hour or longer time averaged 10-m U/V and at UPP side to update the hard-wired 1-hour averaged grib2 metadata setting.

@GwenChen-NOAA
Copy link

@KarinaAsmar-NOAA and @WenMeng-NOAA, Standardized Runoff Index is calculated from total runoff = surface runoff (SSRUN) + subsurface runoff/baseflow (BGRUN). Please output both of them. @barlage can provide the definition of these two variables from Noah-MP if needed.

https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-2-1-0.shtml

@WenMeng-NOAA
Copy link
Collaborator Author

@GwenChen-NOAA No worry about this SFS atmosphere component post-processing. We have collaborated with upstream model developers to address this request.

@HuiyaChuang-NOAA
Copy link
Collaborator

@KarinaAsmar-NOAA and @WenMeng-NOAA, Standardized Runoff Index is calculated from total runoff = surface runoff (SSRUN) + subsurface runoff/baseflow (BGRUN). Please output both of them. @barlage can provide the definition of these two variables from Noah-MP if needed.

https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-2-1-0.shtml

@GwenChen-NOAA Wen is very busy being the only UPP code manager supporting all UFS applications, in addition to helping Karina spin up on SFS post processing.

However, you are more than welcome to update UPP to output the two variables you indicated above. It's pretty simple and many of our internal and external collaborators have done the it. Please follow excellent instructions listed on Wen's UPP wiki page on how this can be done: https://github.com/NOAA-EMC/UPP/wiki/UPP-Code-Development

@WenMeng-NOAA
Copy link
Collaborator Author

@KarinaAsmar-NOAA and @WenMeng-NOAA, Standardized Runoff Index is calculated from total runoff = surface runoff (SSRUN) + subsurface runoff/baseflow (BGRUN). Please output both of them. @barlage can provide the definition of these two variables from Noah-MP if needed.

https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-2-1-0.shtml

@GwenChen-NOAA Thanks for your comments. Karina and I have forged a strong partnership with model developers from the land team and CPC to discern the capabilities of UFS in generating outputs and UPP in processing to meet this CP's request. If you have any new ideas, please incorporate changes in UFS and UPP code, run tests and submit relevant PRs to UFS and UPP repositories. We would be glad to review and implement your modifications in UPP and liaise with CPC accordingly.

@KarinaAsmar-NOAA
Copy link
Contributor

On 03/08/2024, CPC added a new request as:

Wanqui stopped by last Friday and asked that we add temporal max wind at 10 m
in SFS v1 output.
Wen and I just talked and we agreed since RRFS v1 outputs hourly max wind, we can
send a request to the modeling team to see if this feature can be added for SFS/GFS.
Keep in mind that the bucket for GFS is currently 6 hours.
We will follow up with the modeling team at the next SFS meeting or prior to it.

There are efforts needed at model side to output 6-hour or longer time averaged 10-m U/V and at UPP side to update the hard-wired 1-hour averaged grib2 metadata setting.

On 07/11/2024 CPC clarified what is needed for this request

CPC Hazards products are ideally based on the maximum wind during a period, gust or sustained, either one, it's the peak value (like PKWND in a METAR).

So we want a WMax value that's analogous to a Tmax value. The highest wind during a preceding period (6, 12, or at most 24), from all of the model steps during that assessment period. Currently we are using the instantaneous wind speed at the 6hour intervals, and that underestimates the high wind value.

@KarinaAsmar-NOAA
Copy link
Contributor

On 03/08/2024, CPC added a new request as:

Wanqui stopped by last Friday and asked that we add temporal max wind at 10 m
in SFS v1 output.
Wen and I just talked and we agreed since RRFS v1 outputs hourly max wind, we can
send a request to the modeling team to see if this feature can be added for SFS/GFS.
Keep in mind that the bucket for GFS is currently 6 hours.
We will follow up with the modeling team at the next SFS meeting or prior to it.

There are efforts needed at model side to output 6-hour or longer time averaged 10-m U/V and at UPP side to update the hard-wired 1-hour averaged grib2 metadata setting.

On 07/11/2024 CPC clarified what is needed for this request

CPC Hazards products are ideally based on the maximum wind during a period, gust or sustained, either one, it's the peak value (like PKWND in a METAR).

So we want a WMax value that's analogous to a Tmax value. The highest wind during a preceding period (6, 12, or at most 24), from all of the model steps during that assessment period. Currently we are using the instantaneous wind speed at the 6hour intervals, and that underestimates the high wind value.

On 7/16/2024 SFS Monthly Task Discussion meeting, CPC confirmed what is needed is the 10m max wind speed

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

No branches or pull requests

5 participants