Skip to content

Conversation

@ajay-mk
Copy link
Member

@ajay-mk ajay-mk commented Dec 24, 2025

Custom Operator Registry Support

This PR refactors Operator logic from depending on a predefined OpType enum to a runtime OpRegistry, enabling users to define custom operators beyond the predefined set.

Will add a detailed description later.

All connectivity info is now encoded using plain strings
All connectivity info is now encoded using plain strings
…ation order

Constructors now take strings as Operator identifiers
…f perturbation order.

Perturbation order does not make any difference on how the operator acts, so it is only for bookkeeping here.
All methods except A and S will check registry make sure the Operator label is registered.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants