#10792: Upgrade numpy to 1.5.1
------------------------+---------------------------------------------------
Reporter: jason | Owner: tbd
Type: task | Status: needs_info
Priority: major | Milestone: sage-4.7
Component: packages | Keywords:
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
------------------------+---------------------------------------------------
Comment(by drkirkby):
Replying to [comment:8 jason]:
> I don't understand the riemann code very well either, but it seems like
the warning is coming from the line where temp (a real array?) is being
assigned a value from self.cps (a complex array)---see the code that is
deleted in the trac-10792-riemann.patch file. I simplified the code a lot
to avoid having a temporary array, but this changed lots of numerical
results. So one question is: are the results it returns now better or
worse than before?
This is where it would be helpful doctests actually documented why the
particular value is correct. I've seen ''sooooo'' many doctests where the
"expected value" is whatever someone got on their computer and is not
substantiated in any way as a comment in the code.
Also, if the algorithm, or its implementation in Sage is has poor
numerical stability, this should be documented.
Could this be computed with Mathematica or Wolfram|Alpha to arbitrary
precision? Just as thought. If so, that could be documented - we have
permission from Wolfram Research to use Wolfram|Alpha for the purpose of
comparing results and documenting those compassions.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10792#comment:18>
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.
