-
Notifications
You must be signed in to change notification settings - Fork 64
TODO 6VZMW Add topological derivation interface for anomaly cancellation conditions #900
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Introduce a `TopologicalDerivation` structure recording anomaly cancellation conditions as linear, quadratic and cubic homogeneous forms arising from a formal derivation (e.g. triangle diagrams or index-theoretic methods). Provide a canonical map from `TopologicalDerivation` to `ACCSystem`, together with basic simp lemmas, and update the document structure accordingly.
|
Is there a difference between |
Introduce `TopologicalDerivation` as a lightweight abbreviation for `ACCSystem`, used to record the intended topological or perturbative origin of anomaly cancellation conditions (e.g. via triangle diagrams or index-theoretic methods). This avoids duplicating the structure of `ACCSystem` while addressing the corresponding TODO item.
|
Sorry for the late reply, I’ve been quite busy recently. : / This is my first time handling a TODO in the project, so I’m still learning the conventions and best practices here. Thanks a lot for the comment and for pointing this out, I really appreciate it. = ) I’ve updated the code to avoid duplicating ACCSystem and instead introduced TopologicalDerivation as a lightweight abbreviation, whose purpose is only to record the intended origin of the anomaly cancellation conditions. I hope this aligns better with the overall design. = ) |
|
No worries :). This is probably one of the harder TODOs one could have picked :). I think what is probably best, because the documentation you have included is nice is the following:
If this makes sense. |
…tion Expand the documentation of `ACCSystem` and the Open TODO section to clarify that anomaly cancellation conditions are intended to arise from formal derivations (e.g. via triangle Feynman diagrams or index-theoretic methods). No new definitions are introduced; the corresponding TODO item is kept open.
|
Thanks a lot, that makes sense. = ) Before working on TODO 6VZMW more concretely, I just wanted to check what level of formalization you would expect there. In particular, would you envision something like a lightweight abstract structure encoding “gauge data” together with a map producing an ACCSystem, or is the intention more to keep this purely at the level of documentation for now? I want to make sure any further work aligns well with the intended scope of this file and the project. = ) |
|
Awesome, thanks for your edits. I think the former. Ideally one would have a data type corresponding to a gauge field, and then be able to construct the triangle diagrams or use the topological index theorems to get from that to the ACC conditions. There are likely easier intermediate steps that could be done here though and maybe a start would be to break this TODO down into smaller TODO items. |
jstoobysmith
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved - and will merge now :).
|
More generally, in this direction is this GitHub issue #880 which involves refactoring all of the code around these anomaly cancellation conditions, to make them centered on a key data structure. |
Introduce a
TopologicalDerivationstructure recording anomaly cancellation conditions as linear, quadratic and cubic homogeneous forms arising from a formal derivation (e.g. triangle diagrams or index-theoretic methods).Provide a canonical map from
TopologicalDerivationtoACCSystem, together with basic simp lemmas, and update the document structure accordingly.