On 06/26/2010 03:26:06 PM, Jason Grout wrote:
On 6/24/10 6:15 AM, kcrisman wrote:
Right. This crops up in the middle of a more complicated
expression. If I could figure out how to break the expression
up in the right way, then I guess I could search for parts
that are exponential functions, take the log of those, and
then simplify the logs. I know how to ultimately find all
the pieces of the function with .operands(), but I don't
then know any way to put them back together with the
proper operators. Maybe there's a way to access the parsed
I believe there is, but I can't figure out how to do it without going
through fast_callable, which doesn't seem right. This information is
in Pynac, but I can't find a method or underscore method that
accesses
it. This is now http://trac.sagemath.org/sage_trac/ticket/9329 .
See http://sagenb.org/home/pub/1760/ for an example of creating an
expression tree (in that worksheet, the expression tree is used to
make a mathematica expression...)
Hey, that's really cool. Thanks!
BTW, at this point, after the further Latex discussion, I realize
that my original problem was really more related to Ticket #9314
than to the expression itself (at least, that's what I'm currently
speculating). But, especially with that example,
it's pretty clear to me what to do if I need to parse an expression.
I believe that Ticket #9329 was generated in response to my original
post, before I understood that there was a Latex issue involved.
I believe that Ticket #9329 should be deleted (closed or whatever).
-Mike
--
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to
sage-support+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/sage-support
URL: http://www.sagemath.org
