#13096: find_maximum_on_interval fails when used with a sage function
------------------------------+---------------------------------------------
Reporter: aginiewicz | Owner: jason, jkantor
Type: defect | Status: new
Priority: minor | Milestone: sage-5.1
Component: numerical | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
------------------------------+---------------------------------------------
Comment (by aginiewicz):
I believe this is because find_maximum_on_interval is calling
find_minimum_on_interval with lambda z: -f(z) as argument
(sage/numerical/optimize.py:127) and doing
{{{
try:
return f.find_maximum_on_interval(a=a, b=b,
tol=tol,maxfun=maxfun)
except AttributeError:
pass
}}}
just before that should work. Am I right? This might be also related to
#3955 (quite old ticket but looks like it proposes a better solution, were
there some issues with it, or just no one got into it yet?). If I find
enough time to make patch I will post it, but I have to recreate my build
environment first (since sage 5.0 does not work with my version of gcc I
switched to distribution provided package that is already patched).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13096#comment:1>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
