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

How to check all components are evoked in BHIST run while using data assimilation

Nuo Chen

Nuo Chen
New Member
I'm running an 80 member CESM2.2 ensemble with DART to perform atmospheric data assimilation. I cannot build the ensemble in one case directory and perform DA as suggested by the DART team because the request time and memory can take up a large amount of derecho resources. Therefore, instead, I built 80 individual cases and run DART in case #0001 with the assimilation window set to 6 hours.

To let the next round of ensemble forecast use the updated cam.i file, I need to keep CONTINUE_RUN=FALSE for case #0002-#0080, so that these cases will use the posterior cam.i file rather than the cam.r file, which obtains no additional information from the observation through assimilation. I also need to provide the mosart.r, cice.r, clm2.r files from the previous cycle to their prespective user_nl_xxx and modify nhours0 in user_nl_pop.

My question is, how do I check if the BHIST run is still fully coupled when the case is reset to initial run every 6 hours? A weird output file I saw is from the glacial component with the filename like "cism.r.tavg.0000-00-00-00000.nc"

My coupling setting is :
ATM_NCPL: 192
CPL_I2O_PER_CAT: TRUE
CPL_SEQ_OPTION: RASM_OPTION1
GLC_NCPL: 1
ICE_NCPL: 192
LND_NCPL: 192
NCPL_BASE_PERIOD: day
OCN_NCPL: 24
ROF_NCPL: 8
WAV_NCPL: 192
 
Solution
Hi Nuo,

If you set up your run the be the fully coupled BHIST, I believe it would be impossible for it to run not fully coupled. You would have to change the long compset name, and rebuild the code. Even then you should get error messages during the build. To check if you're running fully coupled you can do the following in your case directory.

./xmlquery COMPSET
You should get a response of
COMPSET: HIST_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO_MOSART_CISM2%NOEVOLVE_WW3_SIAC_SESP_BGC%BDRD
This is the long compset name for BHIST.

You can also look at the log files in the run directory. The active model component name is usually in the first 40 lines of the log file.

Chris

fischer

CSEG and Liaisons
Staff member
Hi Nuo,

If you set up your run the be the fully coupled BHIST, I believe it would be impossible for it to run not fully coupled. You would have to change the long compset name, and rebuild the code. Even then you should get error messages during the build. To check if you're running fully coupled you can do the following in your case directory.

./xmlquery COMPSET
You should get a response of
COMPSET: HIST_CAM60_CLM50%BGC-CROP_CICE_POP2%ECO_MOSART_CISM2%NOEVOLVE_WW3_SIAC_SESP_BGC%BDRD
This is the long compset name for BHIST.

You can also look at the log files in the run directory. The active model component name is usually in the first 40 lines of the log file.

Chris
 
Vote Upvote 0 Downvote
Solution
Top