[sage-devel] Sage at EuroSciPy?

2014-08-21 Thread Joris Vankerschaver
Hi all, Is anybody planning to be at EuroScipy 2014 next week in Cambridge? https://www.euroscipy.org/2014/ Any Sage or SageMathCloud projects that could benefit from an impromptu sprint? All the best, Joris -- You received this message because you are subscribed to the Google Groups "s

[sage-devel] Re: SageManifolds: differential geometry and tensor calculus in Sage

2013-07-07 Thread Joris Vankerschaver
This is a very nice package! Are you aware of #9439 (hyperbolic geometry) and #10132 (surfaces embedded > in R^3) which are somewhat related? > > As for #10132, I can see the functionality of that patch being subsumed into this package, once the extrinsic manifold geometry has been implemented

Re: [sage-devel] Re: (abs(sin(x))^2).simplify_full()

2013-07-02 Thread Joris Vankerschaver
> But the example in my original message works -- this really confuses me. > Clearly, simplify_trig invokes maxima to do the simplification, so why does > setting this flag in pynac make it work? Are functions of real variables > treated differently from functions taking a complex argument? >

Re: [sage-devel] Re: (abs(sin(x))^2).simplify_full()

2013-07-02 Thread Joris Vankerschaver
Hi Michael, Thanks for your message. I'm still a little confused about the way Sage handles assumptions, can you maybe shine your light on this? On Monday, July 1, 2013 8:55:43 PM UTC+1, Michael Orlitzky wrote: > > > > sage: u = var('u') > > sage: assume(u, 'real') > > This makes an assumptio

[sage-devel] Re: (abs(sin(x))^2).simplify_full()

2013-07-01 Thread Joris Vankerschaver
On Friday, February 15, 2013 11:31:41 AM UTC, Julius wrote: > > > With sage 5.6 > sage: assume(x, 'real') > sage: (abs(sin(x))^2).simplify_full() > abs(sin(x))^2 > > For trigonometric simplifications, this is very inconvenient. For example > sage: (abs(sin(x))^2 + abs(cos(x))^2).sim

Re: [sage-devel] Re: _cleanup method in DifferentialForms class

2013-07-01 Thread Joris Vankerschaver
y, June 28, 2013 3:36:24 PM UTC+1, Dox wrote: > > I could try to change something... However, What is the way to provide a > patch? Is it through github? > > On Friday, 28 June 2013 09:36:47 UTC-4, Joris Vankerschaver wrote: >> >> >> Symbolic expressions hav

[sage-devel] Re: Changes in Maxima behavior

2013-07-01 Thread Joris Vankerschaver
implify_radical not really being a simplify_ method, and this should be fixed once #11912 and #12737 are approved. Therefore I won't open a new ticket, but I'll just add to the discussion of those patches. All the best, Joris On Friday, June 28, 2013 1:09:49 PM UTC+1, Joris Vankerschaver

Re: [sage-devel] Re: _cleanup method in DifferentialForms class

2013-06-28 Thread Joris Vankerschaver
> Symbolic expressions have a .is_trivial_zero() method which is more > suitable for use here. It doesn't try anything advanced so it has > predictable runtime. > I just wanted to say that I had no idea that this function existed when I wrote that code, and it seems like a good idea to use i

[sage-devel] Changes in Maxima behavior

2013-06-28 Thread Joris Vankerschaver
Hi all, I've been out of the Sage loop for a while, but upon upgrading to 5.10, I found that Maxima seems to choke on the following innocuous code which used to run fine. I'm posting this here, because this issue came up while I was working on #10132, and also because it affects usability.

Re: [sage-devel] Re: Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-28 Thread Joris Vankerschaver
't any code out there that exploits that > > though, so I would vote to not bother with a deprecation warning. > > > > -Marshall Hampton > > > > > > On Tuesday, September 25, 2012 5:28:26 AM UTC-5, Joris Vankerschaver > wrote: > >> > &g

[sage-devel] Bunch of small changes to sage/gsl/interpolation.pyx

2012-09-25 Thread Joris Vankerschaver
With best wishes, Joris Vankerschaver -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com.

[sage-devel] Re: Anyone developing Differential System and Cartan--Kaehler in sage?

2011-12-20 Thread Joris Vankerschaver
Hi Abraham, This sounds like a great project -- I've always wanted to read the Bryant/Griffiths books on EDS but I've always been too lazy to do the computations myself and get a proper grip on the subjects. Such a Sage package could be a great help. I'm not entirely happy with the way that the

[sage-devel] Re: Problems with symbolic vector arithmetic

2011-06-27 Thread Joris Vankerschaver
ith minimal overhead and >         # no type checking. >         cdef FreeModuleElement_generic_dense x >         x = PY_NEW(PY_TYPE(self)) > > David > > On Sat, Jun 25, 2011 at 13:56, Joris Vankerschaver < > > > > > > > > joris.vankerscha...@gmail.com> wrote: > >

[sage-devel] Problems with symbolic vector arithmetic

2011-06-25 Thread Joris Vankerschaver
Dear all, I'm playing around with #11335 which was included in Sage 4.7.1.alpha3. In this patch, I added a symbolic vector class, with the aim of providing simplification methods that act elementwise on symbolic vectors. The symbolic vector class derives from sage.modules.free_module_element.Fre

[sage-devel] Re: DAE solver on Sage.

2011-05-06 Thread Joris Vankerschaver
On May 5, 2:56 am, Guilherme wrote: > IDA is shown as the last on the series DASSL -> DASPK -> IDA. > Sundials is C ++(?) coded. > > Could you handle Mass matrix with DASSL? DASSL handles implicit ODEs of the form F(t, x, x') = 0, so I think it would work for non-constant mass matrices too, b

[sage-devel] Re: DAE solver on Sage.

2011-05-06 Thread Joris Vankerschaver
On May 4, 10:04 pm, Thierry Dumont wrote: > Do you mean that it is possible to define the RHS as a Cython *callback* > function? or is there an other trick ? Can you give me a pointer to that ? The code can for instance be found in the file sage/gsl/ode.pyx (the gsl directory has other classes

[sage-devel] Re: DAE solver on Sage.

2011-05-04 Thread Joris Vankerschaver
On May 3, 11:23 pm, Thierry Dumont wrote: > 1) it takes time to do this, > 2) we have to solve the callback problem: such program make a lot of > callbacks (to the rhs of the system): AFAIK, there are no simple method > to make this work fast enough (the ODE solver in Sage is extremely slow, >

[sage-devel] Re: DAE solver on Sage.

2011-05-03 Thread Joris Vankerschaver
On 3 mei, 15:13, Guilherme wrote: > Is there any DAE solver readily available to Sage? > I wrote a C++ wrapper around DASSL some time ago, but unfortunately this was for personal use and I never put any time into writing documentation and making sure that all the options work well, etc. I don

[sage-devel] Multidimensional root finding with GSL

2011-02-07 Thread Joris Vankerschaver
Dear all, Has there been any effort so far in wrapping the root-finding routines in GSL? Or are there better alternatives for numerical root finding of vector-valued functions in Sage? All I could find is this "mission statement", but it doesn't look as if this was ever completed (I'd love to be

[sage-devel] Re: Callable symbolic expressions and vector functions

2010-12-10 Thread Joris Vankerschaver
On 10 dec, 13:25, Jason Grout wrote: > 3. If you *really* want to use Q like you did above, you could do this: > > sage: Q=var('x,y,z') > sage: f(*Q)=(x-z,y-z) > sage: f > (x, y, z) |--> (x - z, y - z) > This is exactly what I need, but thanks also for the explanation of what goes on behind th

[sage-devel] Callable symbolic expressions and vector functions

2010-12-10 Thread Joris Vankerschaver
Dear all, Is there a reason why Sage doesn't allow you to define vector functions using the following short hand: sage: Q = var('x, y, z') sage: f(Q) = [x - z, y - z] sage: f Q |--> (x - z, y - z) I would have expected/liked the last line to be sage: f (x, y, z) |--> (x - z, y - z) This would

[sage-devel] Bessel functions

2010-11-08 Thread Joris Vankerschaver
Dear all, I wanted to compute some good old Bessel functions, and came upon the following behavior. I did not want to open trac tickets for all of this, since I didn't know (apart from 1) whether this behavior is intentional or not. 1) Sage uses a function "Bessel" which does some input checking