Additional NUOPC_Connector metadata

[theurich]

There are a few more settings we need to support on the generic NUOPC_Connector via attributes:

• A flag to disable VMEpoch usage. It cannot just be ON/OFF, because NUOPC_Connector makes its own decision on whether VMEpoch can be turned ON/OFF (according to the limitation that VMEpoch is currently supported for disjoint send/recv petLists). But this option should allow the user to disable any usage of VMEpoch, even if NUOPC_Connector could turn it ON. On the other hand the option should not suggest to the user that they have a way to force the usage of VMEpoch.
• We already have the EpochThrottle option exposed. We need to also expose the EpochEnterKeepAlloc and EpochExitKeepAlloc

In the ConnectionOptions attribute

• We already have dumpWeights. We need something like dumpCommMatrix to allow dumping of the communication matrix that is available on each RH. Not sure exactly how filename is specified here... need to think about that also for dumpWeights.

[anntsay]

@danrosen25 FYI

[danrosen25]

@anntsay This looks like connector metadata being used internally. I'm not sure this is field metadata. Is it?

[anntsay]

Hi Dan, Got it. thanks for pointing that out. so basically this sounds like it is to expand the NUOPC_Connector attributes. so i think you are right. @theurich could you confirm?

[theurich]

Yes, I just want to add a few more items to the existing Connection Options approach to provide NUOPC access to existing ESMF functionality.

[anntsay]

Gerhard: is motivated to have this in.