#15104: Special case modn_dense matrix operations to improve performance
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.2
Component: linear algebra | Resolution:
Keywords: | Merged in:
Authors: Nils Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/nbruin/ticket/15104 | a908e28159a544ca33f03dcbf0e8def3cfe9a60e
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by SimonKing):
If I understand correctly, you say that we should keep all the custom
transpose methods, since the matrix classes should know best how to create
one of their instances efficiently.
Since you say that the creation of the parent has the most impact, I
suggest to add a lazy attribute `transposed` to matrix spaces, and this
can be used to create a blank matrix of the correct dimension that can
then be filled by whatever custom method we have.
Variation of this theme: We could instead say that `self.new_matrix()`
should not only check whether the to-be-created matrix lives in the same
parent as self, but make a second special case for the transposed
dimensions.
--
Ticket URL: <http://trac.sagemath.org/ticket/15104#comment:16>
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.
For more options, visit https://groups.google.com/groups/opt_out.
