clm5/README.NUOPC_driver.md
2024-05-09 15:14:01 +08:00

52 lines
1.7 KiB
Markdown

# $CTSMROOT/README.NUOPC_driver
CTSM now by default uses the NUOPC based CMEPS driver!
## What's new?
MESH Files:
Mesh files to describe grids are new in both the driver namelist and for example in any
streams files.
Full ESMF Library is used:
The full ESMF Library is used and required to be built in order to run the model.
Single Point cases:
Single point cases can now set their location using PTS_LAT and PTS_LON.
## What's removed?
Domain files are no longer used. And mapping for regriding is created on the fly
rather than using fixed mapping files in almost all cases. Runoff mapping files
still need to be generated offline.
## What files change?
rpointer.drv becomes rpointer.cpl
cpl.log.* files get's split into med.log.* and drv.log.*
user_datm.streams.txt.* file changes goes into the user_nl_datm_streams files
datm.streams.txt.* files are all in one file called datm.streams.xml
## What XML variables change in your case?
DATM_CLMNCEP_YR_* variables change to DATM_YR_*
## New obscure options:
ESMF_AWARE_THREADING --- ESMF is aware of threading (can have differing number of threads in components)
CREATE_ESMF_PET_FILES -- Create output log files from ESMF for each Processor (PET)
ESMF_VERBOSITY_LEVEL --- Verbosity level for ESMF logging
ESMF_PROFILING_LEVEL --- Verbosity level for ESMF profiling
nuopc.runseq is a text file that determines how the driver operates. You can change the operation
by having an updated copy in your case directory.
## What if I want to use the MCT driver?
The MCT driver is now deprecated, and will be removed. So at this point we don't
suggest using it anymore.
For more notes see:
https://docs.google.com/presentation/d/1yjiKSEV53JDAJbYxhpY2T9GTxlWFzQAn