On Wed, Mar 16, 2011 at 2:12 AM, Rob Beezer <goo...@beezer.cotse.net> wrote:
> I can fix the stabilizer, but I am wondering if something more
> systematic is called for - consistently setting _deg in subgroup
> creation, or earlier in general group creation, and with less reliance
> on the largest moved point as a best guess. As this is perhaps
> different from the GAP philosophy (which I do not claim to know well)
> maybe there is a good reason for not being so careful? Maybe there
> are times when it is important to scrunch down the degree as happened
> above?
I have a more systematic fix for this in my patch at #10335. The
patch provides a explicit way to say on which set the group (and
subgroup) acts. If you have issues with it, I have an update to the
patch that I'm trying to push to the combinat patch server. I'm
having some issues with it authenticating; I'll post an update to this
thread when it's "live".
sage: D = DihedralGroup(4)
sage: D.domain()
{1, 2, 3, 4}
sage: S = D.stabilizer(4)
sage: S.domain()
{1, 2, 3, 4}
sage: S.degree()
4
sage: S.orbits()
[[1, 3], [2], [4]]
The patch also goes through and make sure all subgroups constructed go
through a common subgroup code path.
--Mike
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
