ClusterClass templateSelector (keeps explicit mode as default) #575
Description
Hi,
ClusterClass users must pass explicit sourceNode/templateID into PMTs, which is awkward for multi-node/local-template setups. With local storage and identical templates on multiple nodes, users will want to select by tags instead of hardcoding IDs per node.
I propose to add ClusterClass support for a new templateSelector.matchTags and localStorage variables.
If templateSelector absent → current explicit behavior (use sourceNode/templateID).
If templateSelector present → set PMT templateSelector and drop sourceNode/templateID.
localStorage is aligned with Atoms’ PR, which is a pre-req for this.
No change for users who don't specify a templateSelector or localStorage variables.
I link to:
Atoms’ PR enabling multi-node/local-template scheduling.
My follow-up PR against Atoms’ branch adding ClusterClass patches for templateSelector, which will close this issue.