#10682: sum fails with lower bound != 0 or 1 (upgrade maxima to 5.26)
---------------------------------------------------------+------------------
   Reporter:  fmaltey                                    |          Owner:  
burcin                    
       Type:  defect                                     |         Status:  
needs_info                
   Priority:  critical                                   |      Milestone:  
sage-5.0                  
  Component:  symbolics                                  |       Keywords:  
maxima 5.26.0 binomial sum
Work_issues:  domain issue, error handling in nintegral  |       Upstream:  N/A 
                      
   Reviewer:  Jean-Pierre Flori,                         |         Author:  
Dima Pasechnik            
     Merged:                                             |   Dependencies:      
                      
---------------------------------------------------------+------------------

Comment(by nbruin):

 Replying to [comment:68 jpflori]:
 > Yup but that won't be because of too high precision and that's what our
 error message says...
 >
 > So let's just remove the "to that precision" part.

 Yes, you're right. Agreed. In fact, I expect that any precision problems
 will always be reported via the error code, so they will *never* come out
 as an error or an unevaluated call. This only happened before because
 fortan's "STOP" raised an error, which it doesn't do now anymore.

 That also makes me think that the body should be
 {{{
     v = ex._maxima_().quad_qags(x, a, b,
                                 epsrel=desired_relative_error,
                                 limit=maximum_num_subintervals)
     #If an error gets raised during evaluation, maxima just returns the
 unevaluated expression
     #we raise an error instead
     if 'quad_qags' in str(v):
         raise ValueError, "Maxima (via quadpack) cannot compute the
 integral"
     return float(v[0]), float(v[1]), Integer(v[2]), Integer(v[3])
 }}}
 i.e., just let `quad_qags` raise its own errors instead of masking it with
 a blanket error message. Presently we are not aware of any error that
 would get raised under normal operation in there anyway, so we would want
 to know what went wrong.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10682#comment:70>
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.

Reply via email to