[sage-devel] Re: Google constraint programming solver

2010-09-24 Thread Dima Pasechnik
I played a bit with the source, and it does not look like it is ready for even sub-prime time... E.g. there is no configure, and the K8 processor is hardwired (- DARCH_K8) in the makefile. As well, it does use "long long int" in C++, which is not standard... On Sep 25, 12:47 pm, Tom Boothby wro

[sage-devel] bug? sage.combinat.sloane_functions.A111776

2010-09-24 Thread Donald Alan Morrison
Sage 4.5.3, 32-bit, Ubuntu 10.04 %time # n 0..35 # http://www.research.att.com/~njas/sequences/table?a=111776&fmt=4 OEIS_A111776 = [1,1,1,1,2,3,1,4,6,10,1,8,12,20,35,1,16,24,40,70,125,1,32,48,80,140,250,450,1,64,96,160,280,500,900,1625] s453_A111776 = sloane.A111776.list(36) OEIS_A111776 == s453

Re: [sage-devel] Re: Google constraint programming solver

2010-09-24 Thread Tom Boothby
> It's also good to have graph algorithm implementations s that are > "orthogonal" to Sage's, even if for the testing purposes. Agreed. > Unfortunately, there isn't much in terms of documentation there. > As well, it is known not to run on MacOSX PPC, which is one of Sage > official platforms. T

[sage-devel] Re: Google constraint programming solver

2010-09-24 Thread Dima Pasechnik
welll, well, well, so you'd get a competitor then :-) But of course C(S)P is much more than that --- sudoku is a nice toy example, though. On Sep 25, 11:56 am, Tom Boothby wrote: > On Fri, Sep 24, 2010 at 8:41 PM, Dima Pasechnik wrote: > > It's worth including, IMHO > > (at least one could solve

Re: [sage-devel] Re: Google constraint programming solver

2010-09-24 Thread Tom Boothby
On Fri, Sep 24, 2010 at 8:41 PM, Dima Pasechnik wrote: > It's worth including, IMHO > (at least one could solve Sudoku in Sage then: > https://sites.google.com/site/ortoolssite/home/using-the-constraint-programming-solver/anatomy-of-a-python-constraint-programming-example > :-)) http://www.sagema

[sage-devel] Re: Google constraint programming solver

2010-09-24 Thread Dima Pasechnik
It's worth including, IMHO (at least one could solve Sudoku in Sage then: https://sites.google.com/site/ortoolssite/home/using-the-constraint-programming-solver/anatomy-of-a-python-constraint-programming-example :-)) It's also good to have graph algorithm implementations s that are "orthogonal" to

Re: [sage-devel] Google constraint programming solver

2010-09-24 Thread Tom Boothby
I kinda like the look of it, though I'm unfamiliar with constraint programming. It looks like it solves TSP, so that seems like a good enough reason for me. However, there are some standard questions before we add something to Sage: Is it stable? Robust? Is the documentation useful / readable?

Re: [sage-devel] dups from sage-devel

2010-09-24 Thread Michael Welsh
On 25/09/2010, at 10:52 AM, Justin C. Walker wrote: > Just checking: is anyone else seeing duplicate mail from sage-devel? Yes. -- http://yomcat.geek.nz -- 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.

[sage-devel] Google constraint programming solver

2010-09-24 Thread Michele Comignano
Hi to all, on September, the 15th Google made public the source code of its operations research internal tools. That consist essetially of a costraint programming solver and some graph-related algorithms. The cp solver has also a nice Python interface making it perfect for Sage integration. Sa

[sage-devel] dups from sage-devel

2010-09-24 Thread Justin C. Walker
Hi, all, Just checking: is anyone else seeing duplicate mail from sage-devel? The dups don't seem to be occurring on other sage- lists, and I haven't seen them on non-sage lists. The issue seemed to start (early) this morning (US-Pacific time), but not all mail has been dup'd. The messages do

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi! On 25 Sep., 00:08, Simon King wrote: > So, I'll try to fix the Expect.quit() method. To sum it up: * Expect.quit() needs to get rid of self.__local_tmpfile * Expect._local_tmpfile() uses self.__local_tmpfile, or computes a new filename that depends on self.pid() and is unique for the given

Re: [sage-devel] does the cdd spkg really need its own (pseudo)random number generator added?

2010-09-24 Thread Peter Jeremy
On 2010-Sep-22 10:24:04 -0700, Dima Pasechnik wrote: >Perhaps in reality each Sage package must get is own rng, arbitrary >precision arithmetic, garbage collection, embedded Lisp... That might be going a bit far. What might be worth thinking about is a general "portability" library that contains

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi! I think I made a progress in understanding why @parallel works well with pid, but not well with the double-underscore __local_tmpile attribute. The @parallel decorator calls p_iter_fork, and this calls sage.interfaces.quit.invalidate_all. So, let us see what happens: sage: s = gap._local_tm

[sage-devel] The PyCUDA package for sage

2010-09-24 Thread maldun
Hi! I packed a PyCUDA package. The last efforts for this seem to go back 2 years ago. Everything can be found under http://trac.sagemath.org/sage_trac/ticket/10010 It works for me but needs testing (I have ubuntu 10.04 latest nvidia devel drivers, and CUDA 3.2) as mentioned in the other thread P

[sage-devel] Re: pyope...@sage

2010-09-24 Thread maldun
Since nobody answered I figured it out myself how it works. Opened a ticket on this. see http://trac.sagemath.org/sage_trac/ticket/10009 . This would need testing, it is only tested on ubuntu 10.04 with latest NVIDIA developer drivers, and CUDA toolkit. I use a geforce 9500 GT. greez, maldun --

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi all! On 24 Sep., 20:39, "Justin C. Walker" wrote: > The fact that all (or some) instances use the same file make it a   > race condition for sure.  It's just that in this case, there may be a   > very simple fix for it (Ryan's suggestion of using distinct temp   > files, for example). Well, a

[sage-devel] Re: import scipy failing in sage 4.6.alpha1

2010-09-24 Thread maldun
Already tried the new numpy and scipy versions from #9808 instead? I'm not sure if it helps, but give it a try. If the fortran compiler is somehow involved the new versions could solve your problem. On 24 Sep., 17:18, Niles wrote: > Sorry for not seeing the other messages in this thread before m

[sage-devel] Re: pyope...@sage

2010-09-24 Thread maldun
Ok solved it already... -- 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.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org

[sage-devel] Re: pyope...@sage

2010-09-24 Thread maldun
After setting up my cuda and opencl on my machine today, I tried to simply pack a package of pyopencl and pycuda. Both installations worked out of the box, but I get these warnings: >/home/maldun/sage/sage-4.5.2/local/bin/sage-test:140: UserWarning: Module >pkg_resources was already imported fro

Re: [sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Justin C. Walker
Hi, Simon, On Sep 24, 2010, at 11:00 AM, Simon King wrote: On 24 Sep., 19:38, "Justin C. Walker" wrote: That is the crux of the problem. This is a race condition (multiple outcomes, depending on the ordering of operations, many of which are outside of your control. Debugging of these proble

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi Justin! On 24 Sep., 19:38, "Justin C. Walker" wrote: > That is the crux of the problem.  This is a race condition (multiple   > outcomes, depending on the ordering of operations, many of which are   > outside of your control.  Debugging of these problems is why we pay   > software developers t

[sage-devel] Sage on Nvidia Tegra 2 (ARM architecture) ?

2010-09-24 Thread Dima Pasechnik
I have a Toshiba netbook (AC100) with such a processor, that should be able to run Linux (there is currently no distribution that is easy to install, but people are working on this, so this would be possible in few weeks, hopefully); it was released as an Android machine, which is akin to putting a

Re: [sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Justin C. Walker
On Sep 24, 2010, at 1:16 AM, Simon King wrote: Hi Justin! On Sep 23, 11:55 pm, "Justin C. Walker" wrote: - If one has a big string s, then singular(s) will not directly send s to the singular interface, but eventually singular._eval_line_using_file(s) is called.In that method, the file sin

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
On 24 Sep., 19:01, Simon King wrote: > ... > * Why is it not possible to access gap.__local_tmpfile, even though > this attribute *can* be accessed from inside the method? Conversely, if I set the attribute, why is it ignored inside the _local_tmpfile method? sage: gap.__local_tmpfile = 'foobar'

[sage-devel] ANN: mpmath 0.16 released

2010-09-24 Thread Fredrik Johansson
Hi all, Version 0.16 of mpmath is now available on the project website: http://code.google.com/p/mpmath/ It can also be downloaded from the Python Package Index: http://pypi.python.org/pypi/mpmath/0.16 Mpmath is a pure-Python library for arbitrary-precision floating-point arithmetic that impleme

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi Ryan! On 24 Sep., 18:13, Ryan Hinton wrote: > Have you considered Python's tempfile module? > > http://docs.python.org/library/tempfile.html No, I didn't, yet. Since the different Gap instances in the parallelised function have different pid, it would solve the problem to make the _local_tmp

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Ryan Hinton
On Sep 24, 8:49 am, Simon King wrote: > On Sep 24, 3:16 pm, Simon King wrote: > > > Doing so, the gap and singular interfaces get different file names, > > Works. > > > and moreover the trouble with the @parallel decorator vanishes. > > Doesn't. Sorry, another idea is needed. Have you considered

[sage-devel] Re: import scipy failing in sage 4.6.alpha1

2010-09-24 Thread Niles
Sorry for not seeing the other messages in this thread before my previous post; SAGE_BINARY_BUILD is indeed the environment variable that does the trick. -Niles On Sep 24, 11:11 am, Niles Johnson wrote: > Oh, according to my install log I had the same problem; I was fooled > by the fact that sa

[sage-devel] Re: Function assume() has no effect on Maxima via desolve()

2010-09-24 Thread kcrisman
As you say, have fun - so I won't waste time responding to most of this, since we've had this discussion before, except to clarify two things. > > 1) Killer app in web-based interface I mean that the web interface IS the killer app. > > 3) Has access to huge amounts of other libraries > > I thi

Re: [sage-devel] import scipy failing in sage 4.6.alpha1

2010-09-24 Thread Niles Johnson
Oh, according to my install log I had the same problem; I was fooled by the fact that sage started up fine. But now I think I have a solution: I got curious about what PIL is, and while googling I came across this nice page http://www.sagemath.org/doc/installation/source.html which lists a lot

[sage-devel] Re: Function assume() has no effect on Maxima via desolve()

2010-09-24 Thread rjf
On Sep 23, 7:43 pm, kcrisman wrote: > On Sep 23, 11:19 am, rjf wrote: > > > On Sep 23, 5:36 am, Burcin Erocal wrote: > > > > I think it would be a huge overstatement to say that the symbolics > > > subsystem in Sage was "designed" in any way. IMHO, it was mostly > > > patched together to suppo

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
On Sep 24, 3:16 pm, Simon King wrote: > Doing so, the gap and singular interfaces get different file names, Works. > and moreover the trouble with the @parallel decorator vanishes. Doesn't. Sorry, another idea is needed. -- To post to this group, send an email to sage-devel@googlegroups.com T

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi! There is one more issue: sage: print gap._local_tmpfile() /home/king/.sage//temp/gauss/16746//interface//tmp16746 sage: print singular._local_tmpfile() /home/king/.sage//temp/gauss/16746//interface//tmp16746 If gap and singular share one _local_tmpfile, there is another potential source of tr

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
On Sep 24, 1:52 pm, Simon King wrote: > ... > I am about to open a ticket for that issue. It is #10004, and I marked it as blocker for sage 4.6.1, since I think that both parallelisation and interfaces are important enough to make this mandatory for a three-digit (== bug fix) release. Cheers, Si

[sage-devel] Re: import scipy failing in sage 4.6.alpha1

2010-09-24 Thread Georg S. Weber
On 24 Sep., 09:40, Minh Nguyen wrote: > Hi Niles, > > On Fri, Sep 24, 2010 at 7:58 AM, Niles wrote: > > Is there something easy I "forgot" to do? > > I couldn't even get Sage to compile successfully on that machine. > Doing a serial compilation with > > $ make > > resulted in > > /usr/local/lib

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi! I think I found the problem, but can not locate it in the interface code, yet. My test suite uses the @parallel decorator, in order to run several tests at the same time. Under normal circumstances, the gap instances in different branches of a parallelised function have distinct _local_tmpfi

Re: [sage-devel] Sage on IBM's AIX operating system

2010-09-24 Thread David Kirkby
On 24 September 2010 10:24, François Bissey wrote: > Hi Dave, Hi François >> If anyone is interested, here's a summary of the what I found. >> > > Seen the bug reports starting to show up on trac. I am interested :) Yes, some are quite interesting, as they show bugs that really should be fixed

[sage-devel] Error while building libfplll in sage -upgrade

2010-09-24 Thread Johannes
Hi list, i just tried to update sage by sage -upgrade errormessage after sage -upgrade g++ -shared -nostdlib /usr/lib/gcc/i486-linux-gnu/4.4.3/../../../../lib/crti.o /usr/lib/gcc/i486-linux-gnu/4.4.3/crtbeginS.o .libs/dummy.o -Wl,--rpath -Wl,/opt/sage-4.5.1/local/lib -Wl,--rpath -Wl,/opt/sage-4.

Re: [sage-devel] Sage on IBM's AIX operating system

2010-09-24 Thread François Bissey
Hi Dave, > I spent a bit of time yesterday seeing how far Sage would build on AIX 5.3 > after resurrecting my IBM RS/6000. > > I've not made any patches for AIX yet, as I'm primarily keen to get Sage > running on 64-bit Solaris, not AIX. I will use Sage on Solaris, but would > only personally bui

[sage-devel] Sage on IBM's AIX operating system

2010-09-24 Thread Dr. David Kirkby
I spent a bit of time yesterday seeing how far Sage would build on AIX 5.3 after resurrecting my IBM RS/6000. I've not made any patches for AIX yet, as I'm primarily keen to get Sage running on 64-bit Solaris, not AIX. I will use Sage on Solaris, but would only personally build Sage on AIX to

[sage-devel] Re: Problem with Expect: Mutilated temporary files in _eval_line

2010-09-24 Thread Simon King
Hi Justin! On Sep 23, 11:55 pm, "Justin C. Walker" wrote: > > - If one has a big string s, then singular(s) will not directly send s > > to the singular interface, but eventually > > singular._eval_line_using_file(s) is called.In that method, the file > > singular._local_tmpfile() is opened for w

Re: [sage-devel] import scipy failing in sage 4.6.alpha1

2010-09-24 Thread Minh Nguyen
Hi Niles, On Fri, Sep 24, 2010 at 7:58 AM, Niles wrote: > Is there something easy I "forgot" to do? I couldn't even get Sage to compile successfully on that machine. Doing a serial compilation with $ make resulted in /usr/local/lib/libpython2.6.a: could not read symbols: Bad value collect2: l