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

Fix an error in the Modified Todd-Coxeter (subgroup presentations on specified generators) that could lead to wrong results when using IsomorphismFpGroupByGenerators #5469

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

fingolfin
Copy link
Member

@fingolfin fingolfin commented Jun 29, 2023

A replacement routine had been improved to also allow for cyclic
replacement, but that may only be used on relators, not on representatives.

Fixes #5467

Extracted from PR #5468 by @hulpke

A replacement routine had been improved to also allow for cyclic
replacement, but that may only be used on relators, not on representatives.
@fingolfin fingolfin added kind: bug Issues describing general bugs, and PRs fixing them kind: bug: wrong result Issues describing bugs that result in mathematically or otherwise wrong results, and PRs fixing them release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes labels Jun 29, 2023
@fingolfin fingolfin changed the title FIX: Overly eager cyclic replacement in MTC Fix an error in the Modified Todd-Coxeter (subgroup presentations on specified generators) that could lead to wrong results Jun 29, 2023
@fingolfin fingolfin changed the title Fix an error in the Modified Todd-Coxeter (subgroup presentations on specified generators) that could lead to wrong results Fix an error in the Modified Todd-Coxeter (subgroup presentations on specified generators) that could lead to wrong results when using IsomorphismFpGroupByGenerators Jun 29, 2023
@hulpke
Copy link
Contributor

hulpke commented Jun 29, 2023

Is there a reason to take this out of the existing PR without approving that PR itself?

@fingolfin
Copy link
Member Author

Yes. Your existing PR mushes together a bunch of unrelated changes. So to review, approve and merge it will take much longer.

Moving this independent part into a separate PR simplifies the review process and will get it merged much quicker.

(The same would hold for other parts of your PR, which also seem independent).

I would normally require contributors to submit separate changes in separate PRs, but make an exception for you, and do the splitting for you.

@fingolfin fingolfin merged commit 18e8927 into gap-system:master Jun 29, 2023
@fingolfin fingolfin deleted the mh/fix branch June 29, 2023 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug: wrong result Issues describing bugs that result in mathematically or otherwise wrong results, and PRs fixing them kind: bug Issues describing general bugs, and PRs fixing them release notes: use title For PRs: the title of this PR is suitable for direct use in the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IsomorphismFpGroupByGenerators gives group of incorrect size
2 participants