Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Abnormal Latent heat values observed when changing DATM_CLMNCEP_YR

Status
Not open for further replies.
K

KeerZ

Member
Hi all,

I am running a case with I2000Clm50SpGs compset. To use forcing data from 1995-2014, I set: DATM_CLMNCEP_YR_ALIGN=1995,DATM_CLMNCEP_YR_START=1995,DATM_CLMNCEP_YR_END=2014

I ran this case for 40 years and then I found very low latent heat flux and vapor pressure monthly value at the January of a year (Figure1 attached). This seems to occur periodically.

Later I found that this abnormal value disappeared if I rerun this case without modifying DATM_CLMNCEP_YR_ALIGN,DATM_CLMNCEP_YR_START,DATM_CLMNCEP_YR_END (that is, the default 1991-2010 forcing data are used). As show in Figure2, the abnormal spikes disappear in my second simulation.

I am wondering why the abnormal values would occur and does this mean my results of other years in my first simulation are all wrong? How to change the forcing data year correctly?

My two cases can be found at /glade/u/home/keerzhang/cases/i.e20.I2000.f09_g16.SSP5_UC_Spinup and /glade/u/home/keerzhang/cases/i.e20.I2000.f09_g16.SSP5_UC_Spinup2

Any suggestions are appreciated. Thanks!
 

Attachments

  • Figure1.png
    Figure1.png
    409.2 KB · Views: 8
  • Figure 2.png
    Figure 2.png
    525 KB · Views: 8
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
It may be related to this issue:

github.com

QBOT is zero for 2014 for GSWP3v1 data · Issue #1099 · ESCOMP/CTSM

QBOT is zero for all of 2014 for the GSWP3v1 data. In order to fix this we need to bring in a cime update that points to the new data. The cime issue that documents this problem is here: ESMCI/cime...
github.com github.com

where QBOT in the forcing data is zero for January 2014 in the GSWP3 data.

Since you are running on cheyenne, I can point you to a fixed version of the GSWP3 data here that you can try:

/glade/p/cgd/tss/people/oleson/atm_forcing.datm7.GSWP3.0.5d.v1.c200929
 
K

KeerZ

Member
oleson said:
It may be related to this issue:

github.com

QBOT is zero for 2014 for GSWP3v1 data · Issue #1099 · ESCOMP/CTSM

QBOT is zero for all of 2014 for the GSWP3v1 data. In order to fix this we need to bring in a cime update that points to the new data. The cime issue that documents this problem is here: ESMCI/cime...
github.com github.com

where QBOT in the forcing data is zero for January 2014 in the GSWP3 data.

Since you are running on cheyenne, I can point you to a fixed version of the GSWP3 data here that you can try:

/glade/p/cgd/tss/people/oleson/atm_forcing.datm7.GSWP3.0.5d.v1.c200929
Click to expand...

Yes! I got normal LE values for that month after using the fixed version of GSWP3 data. Thank you very much!
 
Status
Not open for further replies.
Top