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

WRF-CTSM: Bottom layer specific humidty sent from the atmosphere model is less than zero #1725

Open
negin513 opened this issue Apr 27, 2022 · 5 comments
Labels
type: -support user or developer needs help

Comments

@negin513
Copy link
Contributor

negin513 commented Apr 27, 2022

Brief summary of bug

Iris Mužić (@irismuz) has reported the following error for her WRF-CTSM simulation after 11 days:

ERROR: Bottom layer specific humidty sent from the atmosphere model is less than zero.

This error is produced from lnd_import_export_utils.F90 , where it checks specific humidity forc_q_not_downscaled_grc coming from the atmosphere with zero:

if ( wateratm2lndbulk_inst%forc_q_not_downscaled_grc(g) < 0.0_r8 )then
call shr_sys_abort( subname//&
' ERROR: Bottom layer specific humidty sent from the atmosphere model is less than zero' )
end if
end do

She has checked the 2m specific humidity (Q2M) variable output from all produced ctsm_lilac.clm*.nc files, however, none of the time steps exhibit values less than zero.

General bug information

CTSM version you are using: @irismuz can you please fill this

@negin513
Copy link
Contributor Author

Here CTSM is complaining about negative specific humidity value coming from the atmosphere model (WRF).

My first thought with this is WRF advection schemes:

Although it is physically impossible to have negative mass, the basic RK time integration in WRF advection scheme produces negative mass or negative mixing ratio at sharp gradients. To address this issues, WRF introduced positive definite and monotonic advection schemes, which get rid of the negative mixing ratios caused by advection.

Therefore, the user should always use advection options moist_adv_opt, momentum_adv_opt, and scalar_adv_opt of 1 (positive definite) or 2 (monotonic advection).

For this particular issue, @irismuz has confirmed they are using monotonic advection option (option 2); therefore the advection option is not what causing this issue.

@ekluzek ekluzek added the tag: next this issue should get some attention in the next week or two label Apr 28, 2022
@irismuz
Copy link

irismuz commented Apr 28, 2022

Thank you for following up on this issue. I am using ctsm5.1.dev042.

@billsacks billsacks added type: -support user or developer needs help and removed tag: next this issue should get some attention in the next week or two labels Apr 28, 2022
@chrystali2002
Copy link

I have this same issue, may I ask if this was solved yet so that I could have access to the solution?

@chrystali2002
Copy link

@irismuz, @negin513, may I know how you are able to solve this issue?

@irismuz
Copy link

irismuz commented Jan 11, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: -support user or developer needs help
Projects
None yet
Development

No branches or pull requests

5 participants