#7099: serious incomplete gamma function precision bugs
-------------------------------------+-------------------------------------
Reporter: was | Owner: jkantor
Type: defect | Status: needs_info
Priority: major | Milestone: sage-6.2
Component: numerical | Resolution:
Keywords: | Merged in:
Authors: Peter Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/pbruin/7099-incomplete_gamma | 3504d34ae7027b90c66694aa22c3351d44cf37e5
Dependencies: | Stopgaps:
-------------------------------------+-------------------------------------
Changes (by {'newvalue': u'Peter Bruin', 'oldvalue': ''}):
* status: new => needs_info
* commit: => 3504d34ae7027b90c66694aa22c3351d44cf37e5
* branch: => u/pbruin/7099-incomplete_gamma
* author: => Peter Bruin
Comment:
Here is a somewhat rough fix. It doesn't take into account the precisions
of both input parameters separately, but uses the precision of the desired
parent in `Function_gamma_inc`, and the precision of the parent of the
first argument in `ComplexNumber.gamma_inc()` et al. Maybe an expert on
this can say whether this behaviour is consistent with other special
functions in Sage?
(Note that the relatively low precision in the new doctest is because of
cancellation.)
--
Ticket URL: <http://trac.sagemath.org/ticket/7099#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.
