-
Notifications
You must be signed in to change notification settings - Fork 312
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
Comments
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 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. |
Thank you for following up on this issue. I am using ctsm5.1.dev042. |
I have this same issue, may I ask if this was solved yet so that I could have access to the solution? |
Hi @chrystali2002, |
Brief summary of bug
Iris Mužić (@irismuz) has reported the following error for her WRF-CTSM simulation after 11 days:
This error is produced from
lnd_import_export_utils.F90
, where it checks specific humidityforc_q_not_downscaled_grc
coming from the atmosphere with zero:CTSM/src/cpl/utils/lnd_import_export_utils.F90
Lines 129 to 134 in d301320
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
The text was updated successfully, but these errors were encountered: