#14014: Update matrix groups to new Parents, libGAP.
----------------------------------+-----------------------------------------
Reporter: vbraun | Owner: joyner
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.9
Component: group theory | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers: David Roe
Authors: Volker Braun | Merged in:
Dependencies: #14187, #14323 | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by vbraun):
=== comment:14 ===
This is the `_repr_` doctests, which previously was incorrectly
labelled as indirect doctest. In fact, it just showed the output that
was generated in a derived class. I replaced it with an explict
doctest that actually tests `ParentLibGAP._repr_`.
=== comment:15 ===
I just want to allow the GMP backend for long integers, I don't think
we gain anything from trying to support the old home-grown one. Though
at this point you can still use both, the conversion from long
integers to Sage is done via strings. But I'd like to change that in
the future and directly access the GMP limbs.
The libgap before this ticket doesn't handle long its correctly
because I didn't understand what GAP docs mean by "immediate
integers". This is why I wrote the explanatory comment.
=== comment:16 ===
That file has been renamed to just `morphism.py`, if you have all
patches you might have to run `sage -sync-build`
=== comment:17 ===
I agree that there is no unique bilinear scalar form, though I would
call **the** orthogonal group (in absence of any further qualifiers)
over a ring the one with the standard (identity matrix) bilinear
form. In particular since the orthogonal groups for other bilinear
forms have sometimes other names, as you said. The next paragraph
explains how the notation for finite fields differ, so I think thats
clear enough:
{{{
The general orthogonal group `GO(n,R)` consists of all orthogonal
`n\times n` matrices over the ring `R`.
In the case of a finite field and if the degree `n` is even, then
there are two inequivalent quadratic forms and a third parameter
``e`` must be specified to disambiguate these two possibilities.
}}}
My aim was to start the docstring with a friendly
paragraph that says what GO/SO is before hitting the user with the finite
field technicalities.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/14014#comment:18>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
