Closed ssiccha closed 3 years ago
@fingolfin What do you think of changing ThrowAwayFixedPoints
such that it always performs the "throwing away" for primitive groups?
@ssiccha It is unclear to me what the connection between your comment is and the issue you report above. I can dig into the source to figure it out, but if you want to save time, perhaps just elaborate as to what the one has to do with the other? Alternatively, submit a PR for discussion.
Ah. The reason that LargeBasePrimitive
can't handle fixed points is simply that it assumes that the given group G
acts on the set [1 .. NrMovedPoints(G)]
. If G
has fixed points that is not the case. If we were to call ThrowAwayFixedPoints
, then the resulting group does act on [1 .. NrMovedPoints(G)]
.
Currently ThrowAwayFixedPoints
creates a homomorphism for an input group H
if 3 * NrMovedPoints(H) >= LargestMovedPoint(H)
. If we would let it create a homomorphism for every primitive group that has fixed points that would make the problem of LargeBasePrimitive
go away.
I've made a PR. See #191.
The large base group, or jellyfish group, recognition is not able to cope with a group which has fixed points.
Consider the following two examples. The first one works, the second is a conjugate group with fixed points which doesn't: