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.

Sign up for GitHub

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

Jump to bottom

MERRA2 double-sided dynamic lapse rate cutoff #1653

Open
Kristen-M-Whitney opened this issue Dec 16, 2024 · 0 comments
Open

MERRA2 double-sided dynamic lapse rate cutoff #1653

Kristen-M-Whitney opened this issue Dec 16, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Kristen-M-Whitney
Copy link

Option to apply a double-sided cutoff to the MERRA-2 dynamic lapse rate values.

If using MERRA-2 with dynamic lapse rates turned on, then users can specify the following options in the config file:

  • apply a double-sided cutoff - if not present, no cutoff is applied
  • specify a maximum lapse rate cutoff value (K/m) - if not present, the default is 0.01 K/m
  • specify a minimum lapse rate cutoff value (K/m) - if not present, the default is -0.01 K/m

Note that @dmocko and @sujayvkumar have helped with this enhancement.
@Kristen-M-Whitney Kristen-M-Whitney added the enhancement New feature or request label Dec 16, 2024
Kristen-M-Whitney added a commit to Kristen-M-Whitney/LISF that referenced this issue Dec 18, 2024
@Kristen-M-Whitney
Add MERRA-2 dynamic lapse rate double-sided cutoff
c3f3dca 
This commit adds the application of a double-sided cutoff to
pre-generated hourly MERRA-2 lapse rate maps. This optional
functionality will replace any lapse rate value that falls above
(below) the maximum (minimum) cutoff threshold with the cutoff
threshold value. The function is invoked by an optional config entry to
apply the double-sided cutoff. If this config entry is not present, the
cutoffs will not be applied. The commit also includes optional config
entries to specify the minimum and maximum cutoff thresholds in units
of K/m. If the config entry for the maximum (minimum) threshold is not
present, the default is set to +0.01 (-0.01) K/m.

Kristen Whitney and David Mocko worked together to modify the code with
this functionality. Kristen Whitney performed code testing.

For now, this code should remain in the eis-freshwater2 branch, and
should not be merged into the main branch yet.

Credit where credit is due:
@dmocko helped with the corresponding code modifications and
adjustments.

Resolves: NASA-LIS#1653
@Kristen-M-Whitney Kristen-M-Whitney mentioned this issue Dec 18, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Kristen-M-Whitney