-
Notifications
You must be signed in to change notification settings - Fork 74
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
WIP: Explicit basis #513
Closed
Closed
WIP: Explicit basis #513
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #513 +/- ##
==========================================
- Coverage 79.78% 77.90% -1.89%
==========================================
Files 26 35 +9
Lines 3216 3838 +622
==========================================
+ Hits 2566 2990 +424
- Misses 650 848 +198
☔ View full report in Codecov by Sentry. |
Closing, cf #517 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the polynomial type implies both a basis and a backend storage type. E.g.,
ImmutablePolynomial
uses the standard basis and a tuple for storage. This PR breaks this up so the basis is explicit -- the equivalent beingImmutableDensePolynomial{StandardBasis}
. If all goes to plan, this will be aliased toImmutablePolynomial
and the PR should be non breaking to the end user.The main types are
MutableDenseUnivariatePolynomial
backed by a vector.MutableDensePolynomial
backed by a vector. This type has an offset, so it will allowLaurentPolynomial
to beMutableDenseLaurentPolynomial{StandardBasis}
.MutableDenseViewPolynomial
non copying when possibleImmutableDensePolynomial
backed by an ntuple. For better type stability, trailing zeros may be present, unlike for the mutable dense polynomial typeMutableSparsePolynomial
backed by a dictionarySome simple benchmarking shows some issues have been improved.
TODO:
[] currently
common.jl
andabstract-polynomial.jl
do the same thing and should be consolidated. (For later, if at all)[x] the types
ImmutablePolynomial
,SparsePolynomial
,LaurentPolynomial
can be removed (Polynomial
too)[x] The
Chebyshev
polynomial example needs to be rewritten to useMutableDensePolynomial
as a backend[x] use this to close #510 and #512. (#511 to be addressed later
[x] check that this doesn't break downstream packages!!
The plan is for this to be followed by another PR which should
[] replaces Polynomial type using new framework
[] makes FactoredPolynomial <: AbstractPolynomial
[] drop polynomials/standardbasis.jl (merging into standard-basis/standardbasis.jl)