On Wednesday, April 5, 2023 at 2:49:39 AM UTC+8 John H Palmieri wrote:
In lengthy code, you could start with a line like
OnSets = libgap.OnSets
and then in the rest of the code, you could do `g.Stabilizer([1,2],
OnSets)`. That is, predefine whatever you want from libgap, giving each
item a
In lengthy code, you could start with a line like
OnSets = libgap.OnSets
and then in the rest of the code, you could do `g.Stabilizer([1,2],
OnSets)`. That is, predefine whatever you want from libgap, giving each
item a meaningful name, and then use that name in the rest of the code.
On
On Friday, March 31, 2023 at 1:38:47 AM UTC+8 Dima Pasechnik wrote:
On Thu, 30 Mar 2023, 18:25 'Peter Mueller' via sage-support, <
sage-s...@googlegroups.com> wrote:
When working with finite permutation groups, it seems to me that one has
the choice to either use the groups as sage objects
Dear Dima, thanks a lot! Indeed, one should have expected it like that ...
Anyway, maybe I'm not the only one who got stuck there, and the answer is
useful for others too.
-- Peter Mueller
Dima Pasechnik schrieb am Donnerstag, 30. März 2023 um 19:38:47 UTC+2:
>
>
> On Thu, 30 Mar 2023, 18:25
On Thu, 30 Mar 2023, 18:25 'Peter Mueller' via sage-support, <
sage-support@googlegroups.com> wrote:
> When working with finite permutation groups, it seems to me that one has
> the choice to either use the groups as sage objects like
> `SymmetricGroup(4)`, or as a Gap object via
When working with finite permutation groups, it seems to me that one has
the choice to either use the groups as sage objects like
`SymmetricGroup(4)`, or as a Gap object via `libgap.SymmetricGroup(4)`. The
former has rather limited functionality (and quite a few bugs as reported
earlier), so
