Skip to content

Add functionality to adjust observed surface temperature to model face height using a lapse rate (local/constant)#2

Open
spanNOAA wants to merge 13 commits intoRRFSx:developfrom
spanNOAA:feature/GSLSurfaceTCorrection
Open

Add functionality to adjust observed surface temperature to model face height using a lapse rate (local/constant)#2
spanNOAA wants to merge 13 commits intoRRFSx:developfrom
spanNOAA:feature/GSLSurfaceTCorrection

Conversation

@spanNOAA
Copy link

implementation pending

@HuiLiu-NOAA
Copy link

HuiLiu-NOAA commented Aug 27, 2024

Thanks @spanNOAA for the effort!

One comment:
I think it is more clear to blend/merge the "CONSTANT_LAPSE_RATE" option into the "GSL" option, because both options use T2m as input. A new parameter "LAPSE_RATE" can be defined/set to either local or global constant within the "GSL" option. The "WRFDA" and "UKMO" also use their own "CONSTANT_LAPSE_RATE = 0.65K/100m", which may be conflicted/confused with the separate "CONSTANT_LAPSE_RATE" option.

@HuiLiu-NOAA
Copy link

HuiLiu-NOAA commented Aug 27, 2024

Shun also suggested that it may be better to explicitly mention "RRFS" in the GLS option since this is specifically for the RRFS application.

@guoqing-noaa
Copy link
Contributor

@HuiLiu-NOAA Thanks for the review.
@spanNOAA I would suggest we combine CONSTANT_LAPSE_RATE and GSL into one option LAPSE_RATE
Then we have choices to use const lapse rate or local lapse rate
No need to hardwire either GSL or RRFS

@HuiLiu-NOAA
Copy link

How about the T2m, which seems the other key/focus of the "GSL" option?

@guoqing-noaa
Copy link
Contributor

I would think T2m is too general. Others may have other ideas for doing T2m, like doing vertical interpolation instead of doing lapse rate correction. Let's use LAPSE_RATE_T2M?

@HuiLiu-NOAA
Copy link

Any opinions/suggestions from @hu5970 and shun liu (to be added to this list)?

@HuiLiu-NOAA
Copy link

maybe "GSL" is good for now?

@guoqing-noaa
Copy link
Contributor

@HuiLiu-NOAA Are you available for a meeting now?

@HuiLiu-NOAA
Copy link

HuiLiu-NOAA commented Aug 27, 2024 via email

@spanNOAA
Copy link
Author

@HuiLiu-NOAA @guoqing-noaa Please check out the latest updates, and let me know if you have any comments.

@HuiLiu-NOAA
Copy link

Thanks @spanNOAA.

  1. "local_lapse_rate_levels" is only one level. So it may be better "local_lapse_rate_level".
  2. "self%lapse_rate" is only defined for "constant", not "local". So, it can be removed?

@spanNOAA
Copy link
Author

Thanks for the comments @HuiLiu-NOAA .
"local_lapse_rate_levels" has been changed to "local_lapse_rate_level".
"self%lapse_rate" is read by the ufo_sfccorrected_setup subroutine and used in ufo_sfccorrected_simobs. So we still need "self%lapse_rate". This value can be adjusted through the YAML configuration file. For instance, we might set it to the adiabatic lapse rate of 9.8, or use an average lapse rate of approximately 6.5K for testing purposes. The term 'constant' refers to the fact that the lapse rate remains unchanged at any given observation location, but it can still be adjusted through the YAML file.

@spanNOAA spanNOAA marked this pull request as ready for review August 27, 2024 22:21
@guoqing-noaa
Copy link
Contributor

@spanNOAA I send you the new surface prepbufr file.
Not sure if you have time to do a test. It is okay if you don't. But if you do, I can compile a new exec for you.

@spanNOAA
Copy link
Author

@guoqing-noaa Please compile one for me, and I'll check if it works when I have the time.

@guoqing-noaa
Copy link
Contributor

@spanNOAA The compiled exec's are here:
/lfs5/BMC/wrfruc/gge/RDASApp/mpas-build2

@delippi
Copy link

delippi commented Jan 3, 2025

@spanNOAA does this add functionality to match the GSI parameter i_use_2mt4b>0?

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.

4 participants