Re: [sage-devel] FFT in sage.

2010-10-02 Thread Mitesh Patel
On 10/02/2010 05:57 AM, Mitesh Patel wrote: >> On 10/1/10, ancienthart wrote: >>> I get the following: >>> >>> a = FFT(4) >>> a[1] = 2 >>> a.forward_transform() >>> >>> Everything works fine up to here. Then, when I do this: >>> >>> a.backward_transform() >>> a >>> >>> I get: >>> NameError: name '

[sage-devel] Sympy version 0.6.7: issues with upgrading?

2010-10-02 Thread cjfsyntropy
Sage currently ships v. 0.6.4 of sympy (http://www.sagemath.org/packages/standard/sympy-0.6.4.p0.txt). I found the hint below in another thread. But what are the issues with upgrading sympy to v. 0.6.7? I could not find a ticket in trac (did I miss it)? On Aug 9, 9:55 pm, François Bissey wrote

Re: [sage-devel] FFT in sage.

2010-10-02 Thread Tom Boothby
> That the notebook sometimes doesn't show the SIGSEGV message may be a > different problem. Yes, this is a fun interplay between two bugs. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups

[sage-devel] Re: Rewrite of LP solver interfaces, constraint generations, and..... reviews :-)

2010-10-02 Thread Dima Pasechnik
On Oct 2, 6:07 pm, Nathann Cohen wrote: > >> Hi Nathann, > >> does your code provide for returning infeasibility certificates? > >> in case of CPLEX Python interface, it's here: > >> .solution.advanced.dual_farkas() > > Oh, you mean certificates of infeasibility for the LP itself ! Then it > sho

[sage-devel] Re: [debian-sage] building a Sage package on Debian

2010-10-02 Thread CJ Fearnley
On Sat, Oct 02, 2010 at 06:04:22PM +0200, Giovanni Mascellani wrote: > Hi CJ, thanks for bringing this issue up again and for the summary. > > Il 01/10/2010 02:22, CJ Fearnley ha scritto: > >* Scipy 0.6.7, which is in sid (Debian's development branch), will > > break things, at least beca

[sage-devel] Re: Ticket #9808 for newer numpy and scipy packages would need a final decision

2010-10-02 Thread maldun
On 30 Sep., 14:58, Jason Grout wrote: > On 9/30/10 6:25 AM, maldun wrote: > > > There is another thing that I want to mention another thing: > > > Leif mentioned that it would be important that after installing of > > numpy rebuilding of sage should happen with -b, and not with -ba > > like I sugg

Re: [sage-devel] FFT in sage.

2010-10-02 Thread Mitesh Patel
On 10/02/2010 05:39 AM, Tom Boothby wrote: > Was this on sagenb.org? Frequently, the server will kill your process > at the most inopportune times... > > On 10/1/10, ancienthart wrote: >> I get the following: >> >> a = FFT(4) >> a[1] = 2 >> a.forward_transform() >> >> Everything works fine up to

Re: [sage-devel] FFT in sage.

2010-10-02 Thread Tom Boothby
Was this on sagenb.org? Frequently, the server will kill your process at the most inopportune times... On 10/1/10, ancienthart wrote: > I get the following: > > a = FFT(4) > a[1] = 2 > a.forward_transform() > > Everything works fine up to here. Then, when I do this: > > a.backward_transform() >

Re: [sage-devel] Re: Rewrite of LP solver interfaces, constraint generations, and..... reviews :-)

2010-10-02 Thread Nathann Cohen
>> Hi Nathann, >> does your code provide for returning infeasibility certificates? >> in case of CPLEX Python interface, it's here: >> .solution.advanced.dual_farkas() Oh, you mean certificates of infeasibility for the LP itself ! Then it shouldn't be so hard :-) How would you like to get it ? An

Re: [sage-devel] Re: Rewrite of LP solver interfaces, constraint generations, and..... reviews :-)

2010-10-02 Thread Nathann Cohen
Helloo > Hi Nathann, > does your code provide for returning infeasibility certificates? > in case of CPLEX Python interface, it's here: > .solution.advanced.dual_farkas() Certificates ? No, it raises exceptions for the moment, which can give you some idea of why it failed dep