Closed ekluzek closed 5 years ago
When this is done the setting of these in CLM's config_component.xml can be removed.
In the clm branch that is needed for compatibility with CIME5 - this must be moved to config_compsets.xml in order to get anything to work.
See https://svn-ccsm-models.cgd.ucar.edu/clm2/branches/clm4_5_8_r174_esmciport/components/clm
The only changes are in cime_config.
On Thu, Jul 7, 2016 at 11:37 AM, Erik Kluzek notifications@github.com wrote:
When this is done the setting of these in CLM's config_component.xml can be removed.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/CESM-Development/cime/issues/470#issuecomment-231151765, or mute the thread https://github.com/notifications/unsubscribe/AHlxE5wvyVq-Hr1hP2F_dDNQx-gm_PfQks5qTTlKgaJpZM4JHUhb .
This is already done.
Set BARRIER_N/OPTION in the driver namelist
March 7, 2016
Where should BARRIER_N go?
There were opinions for both CLM's config_compsets.xml (which does have some other similar xml variable settings) and for the driver's config_component.xml. We lean slightly towards driver's config_component.xml.
Ideally this would apply to any compsets that are datm with non-dlnd – which is part of the argument for having this in the driver rather than clm. However, "not" is hard to do in the xml, so for now match clm + datm.