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

Keyword argument for sending attrvars to other attrvars #916

Closed
kris-brown opened this issue Jun 26, 2024 · 0 comments · Fixed by #918
Closed

Keyword argument for sending attrvars to other attrvars #916

kris-brown opened this issue Jun 26, 2024 · 0 comments · Fixed by #918
Assignees

Comments

@kris-brown
Copy link
Contributor

In homomorphism search, we can sometimes have free floating AttrVars in the domain which can in principle be bound to any concrete value, which means infinite possible homomorphisms (we throw an error in this case). However, if we have the constraint that AttrVars are sent to other AttrVars, it becomes a finite search problem again.

This constraint isn't exactly the same thing as monic, so it deserves a different name. Perhaps bind=true.1 When bind=false, it should be impossible to trigger the error for searching for morphisms from free-floating variables.

Footnotes

  1. Like monic, this could be componentwise too. E.g. bind=[:Weight]

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

Successfully merging a pull request may close this issue.

2 participants