Allowing multiple instances of the same component type in CMEPS.

[jedwards4b]

👋 Welcome!

I would like to open a discussion of the current restrictions in CMEPS that prevents having multiple components of the same type present, for example multiple ocean or atmosphere components, and how to overcome these restrictions in a general way.

One issue that I can think of is more of a CESM issue than a CMEPS one - how do we extend or redefine the compset naming convention to allow for this?

[jedwards4b]

Currently the number of components is derived from the component_list which is an input parameter in nuopc.runconfig. For a fully coupled case it looks like: component_list: MED ATM LND ICE OCN ROF GLC WAV This list is defined in namelist_definition_drv.xml and set by buildnml based on allowing one component for each component class. So this might be extended by allowing an integer appended to the component classes listed in the component_list. eg: component_list: MED ATM1 ATM2 ATM3 LND ICE OCN1 OCN2 ROF GLC WAV