#18356: special resultants ``composed_sum`` and ``composed_product``
-------------------------------------+-------------------------------------
Reporter: pernici | Owner:
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-6.7
Component: algebra | Resolution:
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/pernici/ticket/18356 | 3806e8403764abf4d391161f836f0ec422201cc5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by pernici):
Hi Vincent,
I opened #18373 based on the development branch, replacing this ticket.
I followed your suggestions here and in #18242 :
In `newton_sum` the ring `R` is added as an argument
Avoided using fraction fields (apart from ``R(QQ(1)/p1)`` there was
also a division by `x`).
Eliminated duplicate code, merging `composed_add` and
`composed_product`.
I did some benchmark; there is a strong dependence on the sparseness
of the polynomials.
The resultant algorithm is faster with some polynomials with few
coefficients and high degree.
By default `composed_op` selects which algorithm to use, based on the
degree and the number
of nonvanishing coefficients.
The dependence on the size of the coefficients does not seem to make
much difference.
I eliminated `hadamard_product`.
--
Ticket URL: <http://trac.sagemath.org/ticket/18356#comment:6>
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/d/optout.
