But once you remove the term, it is gone forever. I think nsimplify is not the right thing. I don't think it exists, though I may be wrong.
I'm also not clear where exactly this should happen. In the series code maybe. Someone who knows their way around the algorithm should take a look. Aaron Meurer On Fri, Jan 10, 2014 at 5:03 PM, Avichal Dayal <[email protected]> wrote: > >> There should be some canonical way to remove floating point >> numbers that are smaller than their given precision (i.e., almost >> equal to 0). evalf(chop=True) does this, but there should be some way >> to do it without calling evalf on the expression. But I'm not sure >> what it is if there is such a way. > > > I guess nsimplify does this but I'm not sure if it uses evalf as an internal > function. > > But if we use nsimplify, evalf or any simplifying function, won't it be > slow? > Limits are calculated using series and we might have to simplify every term > to remove floating numbers smaller than their given precision. > > Also gruntz is a highly recursive function which uses limits and series many > number of times. Simplifying every term does not seem feasible. > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/sympy. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sympy. For more options, visit https://groups.google.com/groups/opt_out.
