GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

processor agglomeration does not support non-processor coupled patches

Functionality to add/problem to solve

processor agglomeration does not support non-processor coupled patches e.g. cyclicAMI

Target audience

Parallel runs that

benefit from processor agglomeration
use cyclicAMI/cyclicACMI

Proposal

Add general I/O for sending/receiving GAMG interfaces & fields.

What does success look like, and how can we measure that?

Use processorAgglomerator masterCoarsest on cases with cyclicAMI.