Comment #12 on issue 3814 by mrock...@gmail.com: Relations on
MatrixElements are broken.
http://code.google.com/p/sympy/issues/detail?id=3814
I would be more amenable to having Symbol in a MatrixSymbol if it didn't
carry along all of the Expr baggage. For example MatrixExprs don't use old
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 3985 by sat...@gmail.com: dnot integrate result
http://code.google.com/p/sympy/issues/detail?id=3985
integrate(cos(x)/(1-cos(4*x)), x)
no calc result.
On Wolfram:
Updates:
Status: Valid
Labels: Integration
Comment #1 on issue 3985 by asmeu...@gmail.com: dnot integrate result
http://code.google.com/p/sympy/issues/detail?id=3985
(No comment was entered for this change.)
--
You received this message because this project is configured to
Comment #14 on issue 3814 by asmeu...@gmail.com: Relations on
MatrixElements are broken.
http://code.google.com/p/sympy/issues/detail?id=3814
There was an issue about this somewhere, but I can't find it, but I also
think it would be great if you could still just use Symbol('x') and it
Is this the desired behavior of parse_expr?
In [16]: parse_expr(2log(x), transformations=(standard_transformations+
(implicit_multiplication,)))
Out[16]: 2⋅og⋅x
In [17]: parse_expr(2log(x), transformations=(standard_transformations+
(implicit_multiplication_application,)))
Out[17]: 2⋅g⋅o⋅x
It
Thanks Ondrej, Aaron for the information.
Regards,
Thilina
On Thu, Aug 22, 2013 at 1:38 AM, Aaron Meurer asmeu...@gmail.com wrote:
On Wed, Aug 21, 2013 at 10:02 AM, Ondřej Čertík ondrej.cer...@gmail.com
wrote:
On Tue, Aug 20, 2013 at 3:47 PM, Aaron Meurer asmeu...@gmail.com
wrote:
You
We had a slight regression with elements of MatrixSymbols. A substantially
beneficial code refactoring left us with an expression object that
sometimes fails. We discussed solutions for this in a few PRs (listed
below) but failed to resolve this issue before the 0.7.3 release (I was in
crunch
http://code.google.com/p/sympy/issues/detail?id=3814
https://github.com/sympy/sympy/pull/2093
https://github.com/sympy/sympy/pull/2095
https://github.com/sympy/sympy/pull/2105
On Thu, Aug 22, 2013 at 8:55 AM, Matthew Rocklin mrock...@gmail.com wrote:
We had a slight regression with elements of
Fortunately this issue does not descend from the larger issue and can be
solved independently. See https://github.com/sympy/sympy/pull/2402
On Thu, Aug 22, 2013 at 8:57 AM, Matthew Rocklin mrock...@gmail.com wrote:
http://code.google.com/p/sympy/issues/detail?id=3814
Happy to hear it.
On Thu, Aug 22, 2013 at 11:58 AM, dibus2 dib...@gmail.com wrote:
Alright I had a look at it and tried to run my program which uses it
extensively and it does not complain anymore. Therefore I think that it
works.
Thanks a lot.
Cheers,
F.
Le jeudi 22 août 2013
Have you tested your interpolation op in isolation from SymPy?
A quick glance at the error (quick glance means I can easily be wrong)
leads me to think that this particular issue is localized within the domain
of Theano. If this is the case then I recommend asking about your spline
op on the
Hey Matt,
I am pretty sure that I have tested the theano Op separately from Sympy,
but again, I am probably missing something silly.
After running the test cases, or evaluating
k = TestInterpOp()
k.CreateSuite()
from the SymPy_Theano_KGM_indep.py file, one can run the following lines
In
Correction (independent of testing the theano op), 's' is a simple wrapper
to the spline function, it is not the sympy wrapper. the sympy wrapper is K
and can be evaluated as
In [17]: K._imp_(4.0)
Out[17]: array(16.0)
On Thursday, August 22, 2013 5:44:35 PM UTC-4, Guy Parsey wrote:
Hey Matt,
Here is a printout of the error message:
MissingInputError: ('An input of the graph, used to compute
TheanoInterpWrapOp.theanointerp(y), was not provided and not given a
value', y)
What this says is that some nodes in your graph
(TheanoInterpWrapOp.theanointerp(y),) weren't given access to all
That is precisely what I don't understand. In your example we are
neglecting to give the function all of its inputs and the error message:
MissingInputError: ('An input of the graph, used to compute
Elemwise{add,no_inplace}(x, y), was not provided and not given a value', y)
is saying that we
Looking at your code it's difficult for me to see what you're doing with
the cache. It looks like you're trying to fill it with a particular value
so that SymPy's theano_function call latches onto something you've already
built.
Instead, I recommend that you use theano_code, to transform
On Thu, Aug 22, 2013 at 11:44 AM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Wed, Aug 21, 2013 at 2:08 PM, Aaron Meurer asmeu...@gmail.com wrote:
On Wed, Aug 21, 2013 at 10:02 AM, Ondřej Čertík ondrej.cer...@gmail.com
wrote:
On Tue, Aug 20, 2013 at 3:47 PM, Aaron Meurer
I'm not clear enough on how the standard_transformations work to say
if this should happen or not. We definitely need a better API to our
parser to allow fixing this sort of issue.
By the way, there *is* something that is definitely a bug, though,
which is that it happens in Python 3, even though
I opened https://code.google.com/p/sympy/issues/detail?id=3986 for the
Python 3 issue. Feel free to open an issue for the issue of getting
2*log(x) instead of 2l*og*x.
Aaron Meurer
On Thu, Aug 22, 2013 at 8:09 PM, Aaron Meurer asmeu...@gmail.com wrote:
I'm not clear enough on how the
Maybe a -1 if this means changing xrange. We use it a lot, and it has the
advantage of being unambiguous. And, given a unified source base, I would
value clarity over esthetics.
On Wednesday, August 21, 2013 4:41:20 PM UTC-7, Aaron Meurer wrote:
Thanks. I think we should change the codebase
20 matches
Mail list logo
