#20174: Avoid recomputing vacancy numbers for rigged configurations
-------------------------------------+-------------------------------------
Reporter: tscrim | Owner: sage-combinat
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-7.1
Component: combinatorics | Resolution:
Keywords: rigged | Merged in:
configurations | Reviewers:
Authors: Travis Scrimshaw | Work issues:
Report Upstream: N/A | Commit:
Branch: | 8591c4aca549ef8d0e8e487878a1efe4cad02456
public/rigged_configurations/speedup_crystal_ops-20174| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Description changed by tscrim:
Old description:
> Many of rigged configuration operations, such as `e()` and `f()`,
> needlessly recompute the vacancy numbers. We simply need to tell the
> constructor to avoid doing these computations.
New description:
Many of rigged configuration operations, such as `e()` and `f()`,
needlessly recompute the vacancy numbers. We simply need to tell the
constructor to avoid doing these computations.
Also, because the Cartan matrices are sparse and general matrix
implementation details, it is relatively expensive to iterate over the
row. Instead, it is much fast to get the specific entry by `CM[i,j]`.
--
--
Ticket URL: <http://trac.sagemath.org/ticket/20174#comment:3>
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 https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
