d2516a597a7a8a12ef0c0ce21ed825de/symengine/lib/symengine_wrapper.pyx#L1199
>
>
> Let us know if you need faster non-linear solvers than the ones in
> sympy, and which ones.
>
> Ondrej
>
> On Tue, Nov 10, 2015 at 1:40 PM, Nathan Woods > wrote:
> > Am I
Am I correct in noticing that symengine.py does not yet have Solve (or
equivalent)? That's kind of a dealbreaker, unfortunately.
On Tuesday, November 3, 2015 at 9:56:43 AM UTC-7, Björn Dahlgren wrote:
>
>
>
> On Tuesday, 3 November 2015 16:46:39 UTC+1, Nathan Woods wrote:
>
worse than
the Python call-back overhead. The real gotcha for me is that I need to do
a complete Solve-Generate-Integrate loop many, many times, so the
performance of the generation step matters a lot.
Nathan Woods
On Friday, October 30, 2015 at 3:33:19 PM UTC-6, Aaron Meurer wrote:
>
> I
I see no reason why this idea
could not be adapted to use the built-in Sympy integration routines; that's
just not how I developed it. Please let me know what you think, and whether
this would be a good fit for Sympy.
Nathan Woods
On Tuesday, February 24, 2015 at 11:26:18 AM UTC-7, Aa
can use and we can link to it from our docs/website.
>
>
> Jason
> moorepants.info
> +01 530-601-9791
>
> On Tue, Feb 24, 2015 at 9:08 AM, Nathan Woods > wrote:
>
>> The decoupling is actually pretty easy. Unfortunately, the Sympy-specific
>> stuff isn't es
again!
N
On Tuesday, February 24, 2015 at 9:17:41 AM UTC-7, Joachim Durchholz wrote:
>
> Am 24.02.2015 um 17:03 schrieb Nathan Woods:
> > Anyway, I would like to package this up in a way that would be publicly
> > useful, but I'm not sure where it fits. Sympy seemed a likel
nuity-processing could be decoupled and used with any iterated
integrator that supports manually specified points of discontinuity. If
Sympy isn't a good fit for this, I would appreciate suggestions about other
places that might be better.
Thanks for the help,
Nathan Woods
--
You received th
e by the way.
>
>
> On Tue, Oct 8, 2013 at 1:37 PM, Ondřej Čertík wrote:
>
>> On Tue, Oct 8, 2013 at 2:32 PM, Nathan Woods
>> wrote:
>> > I'm getting a compiler error using "gcc -c integrand.c".
>> >
>> > integrand.c: In functi
Oh, and I should point out that I used a different function (whatever I had
in my code) and that the returned values look correct to me.
On Tue, Oct 8, 2013 at 2:37 PM, Ondřej Čertík wrote:
> On Tue, Oct 8, 2013 at 2:32 PM, Nathan Woods
> wrote:
> > I'm getting a compiler er
this reflects
mathematical practice, so it's probably not a bad thing, but it doesn't
jive quite so well with programming practice, where users might expect
something that's a little less stringent.
On Tue, Oct 8, 2013 at 2:32 PM, Nathan Woods wrote:
> I'm getting a compiler err
art of
'project' *
**/
#include "integrand.h"
#include
double integrand(double t, double x, double y) {
return if (x < 0.5) {
t*x*y + pow(x, 2) + pow(y, 2) + cos(t) - 1
}
else if (x >= 0.5) {
t*x*y + pow(x, 2) + pow(y, 2) + cos(t)
};
}
On Tue, Oct 8, 201
ewise((0, x < 0), (1, x > 0))
> >
> > Try
> >
> > Piecewise((x, x < 0), (x + 1, x > 0))
> >
> > You shouldn't have to do this (ccodegen should be smart enough to handle
> > this), but I suspect it will work in the short term.
> >
I would be happy with either of the following implementations, one or the
other of which might be preferred for other reasons. The immediate intended
use is to wrap the resulting function in ctypes so that I can feed it to
some existing code.
- An if/then construct, like what you mentioned. I don'
to handle indexed data, but I
> never used them.
> On Tuesday, October 8, 2013 8:20:31 AM UTC+2, Ondřej Čertík wrote:
>>
>> Nathan,
>>
>> On Mon, Oct 7, 2013 at 10:52 PM, Nathan Woods
>> >
>> wrote:
>> > The sympy function (the output of pri
tructure(expr)
File
"/Users/woodscn/SCIPYTEST/lib/python2.7/site-packages/sympy/tensor/index_methods.py",
line 401, in get_contraction_structure
result[key] |= d[key]
TypeError: unsupported operand type(s) for |=: 'set' and 'Piecewise'
Thanks for the quick respo
idea
I've had so far is to use Heaviside functions for the discontinuities and
write my own Heaviside implementation for inclusion by codegen.
Thanks for any help.
Nathan Woods
P.S. Thanks for a great product!
--
You received this message because you are subscribed to the Google G
16 matches
Mail list logo
