#11143: Add various Maxima special functions to symbol table
-------------------------+--------------------------------------------------
   Reporter:  kcrisman   |          Owner:  burcin
       Type:  defect     |         Status:  new   
   Priority:  major      |      Milestone:        
  Component:  symbolics  |       Keywords:  ei Ei 
Work_issues:             |       Upstream:  N/A   
   Reviewer:             |         Author:        
     Merged:             |   Dependencies:        
-------------------------+--------------------------------------------------

Comment(by kcrisman):

 Those are good questions.

 I think the most important thing is to make sure that whatever is
 implemented has

  * good numerical evaluation (perhaps via mpmath)
  * translates back and forth to Maxima properly (for integration and
 limits)

 My sense is that !BuiltinFunction would be best.  !GinacFunction probably
 is only good for things that in fact evaluate in Ginac.  This explains
 trig.py.  [http://www.ginac.de/tutorial/Built_002din-functions.html|This
 Ginac page] shows that the ones which are !GinacFunctions are exactly the
 ones which Ginac in fact has.      I don't think it has most of these
 other functions.

 As for !MaximaFunction, it seems to inherit from !BuiltinFunction and
 lives in the special functions file.  This dates from the days when Sage
 had very few options for symbolic stuff and evaluation, and so it just
 does a few extra things.  If we moved to mpmath for a given function, we
 would probably use !BuiltinFunction and then add evaluation options for
 Maxima and add to the conversion dictionary as needed.

 In fact, it wouldn't be a bad idea to have two different eval procedures
 if possible...


 ----

 As for where such things go, probably it would make sense to separate a
 lot of these special functions out into a separate file.  The distinction
 between transcendental and special is not totally obvious, for instance :)

 ----


 By the way, we certainly want fewer of the wrapper functions!  But that
 will take a lot of tedious work.

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