-
Notifications
You must be signed in to change notification settings - Fork 161
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
Regression in the new MTC #2892
Comments
I did git bisect for the second problem described in gap-packages/wedderga#43. It does not show up when GAP started with |
for cyclic subgroup search. This resolves gap-system#2892
This is an interesting case, which shows again that FpGroups just can behave rather surprisingly. It is not a regression in code correctness or performance (and I've thus removed the regression label). In particular, it has to do only with the strategy of finding cyclic subgroups, not with performance or correctness of the MTC. The same coset enumeration issue turns up in the 25 years old enumerator inherited from GAP3. What is happening is that the One can further refine the strategy (which I have done in #2895) to make this issue disappear. Independently, is there a reason for making this an fp group example? |
Thanks @hulpke - I will test #2895. The free group example above occurred in this calculation in the code contributed to Wedderga by Allen Herman:
I have managed to extract the group causing the problem from there to make the problem easily reproducible. |
for cyclic subgroup search. This resolves gap-system#2892
for cyclic subgroup search. This resolves gap-system#2892
for cyclic subgroup search. This resolves #2892
for cyclic subgroup search. This resolves #2892
for cyclic subgroup search. This resolves gap-system#2892
I have discovered that Wedderga package tests became broken in the stable-4.10 and master branches (see gap-packages/wedderga#43). Using git bisect lead me to the conclusion that this was introduced in ce04724 which is a part of #2812 by @hulpke.
In GAP 4.9.3 we have:
In stable-4.10 we have:
The full backtrace is
The text was updated successfully, but these errors were encountered: