New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid recomputing vacancy numbers for rigged configurations #20174
Comments
comment:1
With branch:
vs old version
Slightly annoying how simple changes these were and resulting in such a large speed gain... New commits:
|
Commit: |
Branch pushed to git repo; I updated commit sha1. New commits:
|
This comment has been minimized.
This comment has been minimized.
Reviewer: Anne Schilling |
Changed branch from public/rigged_configurations/speedup_crystal_ops-20174 to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Many of rigged configuration operations, such as
e()
andf()
, 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]
.CC: @sagetrac-sage-combinat @anneschilling @bsalisbury1
Component: combinatorics
Keywords: rigged configurations
Author: Travis Scrimshaw
Branch/Commit:
8591c4a
Reviewer: Anne Schilling
Issue created by migration from https://trac.sagemath.org/ticket/20174
The text was updated successfully, but these errors were encountered: