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

INPUT ALTITUDES NOT IN ASCENDING ORDER when IMMAX<0 #15

Open
drbel8 opened this issue Mar 8, 2024 · 2 comments
Open

INPUT ALTITUDES NOT IN ASCENDING ORDER when IMMAX<0 #15

drbel8 opened this issue Mar 8, 2024 · 2 comments
Assignees

Comments

@drbel8
Copy link

drbel8 commented Mar 8, 2024

Hello,
in my INPUT_RRTM file I'm setting IMMAX<0 (IBMAX is also <0) but I'm getting
INPUT ALTITUDES NOT IN ASCENDING ORDER

I tried to set ZM to 0.0; to ascending altitude as well as to leave the field empty, the PM field is descending.

The same INPUT_RRTM works correctly with RRTM_LW
Do you have any suggestion?

INPUT_RRTM.txt

@mjiacono
Copy link

Thanks for reporting this issue. There is an oversight in RRTMG_LW that doesn't appear in RRTM_LW because the interfacing to the INPUT_RRTM file is somewhat different. For now, a quick fix involves making two small changes to source module rrtmg_lw.1col.f90: 1) at line 793, add "gravc" to the end of common block "consts", and 2) at line 906 add a line that defines gravc as "gravc = grav * 1.e02". This addition of the gravity constant (in units of cm/s2) will allow the code to correctly specify altitudes from the input pressure values. We will add this correction to a future release.

@drbel8
Copy link
Author

drbel8 commented Mar 12, 2024

Thank you, I confirm this solved my issue.

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

2 participants