#6371: Implement Riemann theta functions
-----------------------------------------------+----------------------------
   Reporter:  ncalexan                         |          Owner:  cswiercz      
                    
       Type:  enhancement                      |         Status:  needs_work    
                    
   Priority:  minor                            |      Milestone:  sage-4.8      
                    
  Component:  numerical                        |       Keywords:  riemann theta 
klein               
Work_issues:                                   |       Upstream:  N/A           
                    
   Reviewer:  Marco Streng, Bernard Deconinck  |         Author:  Nick 
Alexander, Chris Swierczewski
     Merged:                                   |   Dependencies:                
                    
-----------------------------------------------+----------------------------

Comment(by cswiercz):

 Marco,

 > :) Actually, when I use theta functions in my research, Omega is usually
 the variable and z is usually some fixed vector in with entries in QQ.
 >
 > Anyway, what is the (programming technical) reason for having objects
 that depend on Omega? Is there some kind of caching involved? Some part of
 the algorithm that depends on Omega only and that you only want to do
 once?

 Interesting. I've only seen one other instance in which Omega was varied:
 it was in the context of solving particular boundary value problems.) If
 you don't mind, do you have a paper you can send me about your work?
 (cswiercz [at] gmail ]dot[ com)

 I agree that there should be no distinction between the two parameters.
 From what I understood about {{{BuiltinFunction}}, though, the purpose of
 distinguishing Omega as a parameter is to make it easy to send symbolic
 output. Since I initially made this decision, however, I've learned more
 about the way Sage ({{{BuiltinFuncion}}}?) handles inputs and determines
 if they're symbolic. A rewriting of the way arguments are sent to
 {{{RiemannTheta}}} should be possible.

 I'll see what I can do about restructuring the code. Thank you very much
 for your input and suggestions. I'll keep everyone posted on my (slow)
 progress.

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