Skip to content
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

Sigma migration of morphisms #937

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

Sigma migration of morphisms #937

wants to merge 2 commits into from

Conversation

kris-brown
Copy link
Contributor

@kris-brown kris-brown commented Sep 11, 2024

This PR allows one to call sigma migration objects as if they were functions on both ACSets and ACSetTransformations.

Sigma migration along F: C -> D on morphisms begins with migrating the dom, X, and codom, Y.

The new components, e.g. for some object a in the schema C which is sent to an object, are the unique ones
which make the following square commute:

                         fₐ
               Xₐ      →     Yₐ        
         αXₐ ↓              ↓ αYₐ
      ΣF(X)_F(a) ⤑ ΣF(Y)_F(a)

This is because the results of the sigma migrations are freely generated by some
generators, and we stipulate the homomorphism by saying where the generators go via an initialized hom search.

There are some deeper issues that need to be addressed, unrelated to SigmaMigrations but rather to VarACSets, which are uncovered by migrations in AlgRewriting now stress-testing the chase with AttrVars. I'll update this description with details on this later!

working draft for SimpleMigrations
Copy link
Contributor

Review Checklist

Does this PR follow the development guidelines? Following is a partial checklist:

Tests

  • New features and bug fixes have unit tests
  • New modules have tests that are ultimately called by the test runner (test/runtests.jl)
  • Existing tests have not been deleted
  • Code coverage >= 90% or reduction justified in PR

Documentation

  • All exported functions, types, and constants have docstrings, written in complete sentences
  • Citations are given for any constructions, algorithms, or code drawn from external sources

Other

  • Style guidelines are followed, including indent width 2
  • Changes breaking backwards compatibility have been approved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants