Re: [sage-devel] Please test sage-5.1.rc1

Hi On 6 July 2012 09:05, Jeroen Demeyer wrote: > Because many of the Sage testing machines (redhawk and all of Skynet) > are down, version sage-5.1.rc1 has been tested much less than usual. > > So, please build sage-5.1.rc1 and report unexpected problems, especially > if you have an unusual syst

Re: [sage-devel] Re: [sage-support] Re: Sage fails to run python script correctly

Hi On 7 July 2012 07:33, Keshav Kini wrote: > Dima Pasechnik writes: > > If you caan ssh from these machines to boxen then it will be good enough. > > In particular, you might do this on your buildbot machine: > > $ sudo apt-get install autossh > $ ssh-keygen # if you haven't done this already

[sage-devel] Re: [sage-support] Re: Sage fails to run python script correctly

Dima Pasechnik writes: > If you caan ssh from these machines to boxen then it will be good enough. In particular, you might do this on your buildbot machine: $ sudo apt-get install autossh $ ssh-keygen # if you haven't done this already $ ssh-copy-id boxen.math.washington.edu $ ssh boxen.math.wa

[sage-devel] Re: Please test sage-5.1.rc1

> So, please build sage-5.1.rc1 and report unexpected problems, especially > if you have an unusual system. Downloads at: > http://www.sagemath.org/download-latest.html > -- > I have tried to compile on my system with sage-5.1.rc1 erroring out. hardware is; AMD 64 pro

[sage-devel] Re: Static and shared libraries for Cygwin

We need to change flint in two ways: 1) Instead of disabling shared library on flint, set it up so that either static or shared can be selected, but not both. It should make its selection based on whether a shared/static library of mpir is available if the user hasn't selected. 2) Don't pass -

[sage-devel] Re: Code duplication and aliases in methods

On 7/6/12 10:02 AM, Birk Eisermann wrote: > Similar, it is for classes. If one class focuses only one responsibility, > the functionality of that class is much easier to understand. Well, the Graph class is not very complicated. It just has one thousand methods that apply to graphs. But at lea

Re: [sage-devel] Re: Code duplication and aliases in methods

On 07/06/2012 08:20 PM, Jeroen Demeyer wrote: On 2012-07-06 14:10, Nathann Cohen wrote: Then, of course, we would have to change the is_isomorphic function (it does not take the bipartition into account). Indeed, if I create a BipartiteGraph object I would expect the is_isomorphic() function t

Re: [sage-devel] Re: Code duplication and aliases in methods

Hello Nathann! On 07/06/2012 08:06 PM, Nathann Cohen wrote: > I found that G.Bipartition() will do the job. > Surprisingly (or not) all vertices belong to one class and the other is > empty. For me, BipartiteGraph(k,l) would be more natural (maybe with the > convertion that the first partiti

[sage-devel] Re: bluetooth.h ? Fwd: [sage-support] Re: Sage fails to run python script correctly

On Friday, 6 July 2012 22:43:31 UTC+8, Dima Pasechnik wrote: > > Does this look like a missing Sage dependency? > > On Friday, 6 July 2012 22:26:53 UTC+8, Dima Pasechnik wrote: >> >> here is why _socket extension does not get build: >> >> /home/carlos/Workspace/Sage/src/sage-5.0.1/spkg/build/pyth

[sage-devel] bluetooth.h ? Fwd: [sage-support] Re: Sage fails to run python script correctly

Does this look like a missing Sage dependency? On Friday, 6 July 2012 22:26:53 UTC+8, Dima Pasechnik wrote: > > here is why _socket extension does not get build: > > /home/carlos/Workspace/Sage/src/sage-5.0.1/spkg/build/python-2.7.3.p0/src/Modules/socketmodule.h:51:33: > > fatal error: bluetooth

Re: [sage-devel] Re: sage compiling problem AMD

On Friday, July 6, 2012 1:34:41 PM UTC+1, Jeroen Demeyer wrote: > > This is a known bug in the spkg-install Python script where > sys.stdout.flush() should be used before os.system(). I don't care so much about getting stdout in-order, in the log file its not there at all. Even if you don't flu

Re: [sage-devel] Re: Code duplication and aliases in methods

On Friday, July 6, 2012 1:33:23 PM UTC+1, Nathann Cohen wrote: > > I agree that you may want to compute automorphisms groups quickly, but it > quickly gets painful that every edge addition requires a whole copy of the > graph's structure :-p > Graphs just need a way to add multiple edges in a si

Re: [sage-devel] Re: Code duplication and aliases in methods

>> I also wondered whether you wanted to compute isomorphisms in which the >> two sets are exchanged > I think both questions make sense, depending on the problem you're > working with. Indeed. That's why I think that such code should be "custom code", code that you write for yourself and that jus

Re: [sage-devel] Re: sage compiling problem AMD

On 2012-07-06 14:26, Volker Braun wrote: > The install.log is very confusing, it does not contain the output of the > atlas spkg-install build script (only the atlas make output). The only > reason that I can think of would be if some the build processes were > killed, either because your machine r

Re: [sage-devel] Re: Code duplication and aliases in methods

On 2012-07-06 14:38, Nathann Cohen wrote: > I also wondered whether you wanted to compute isomorphisms in which the > two sets are exchanged I think both questions make sense, depending on the problem you're working with. Maybe the default should be to consider purely the partition, BipartiteGraph

Re: [sage-devel] Re: Code duplication and aliases in methods

> Indeed, if I create a BipartiteGraph object I would expect the > is_isomorphic() function to check for isomorphism *as bipartite graphs*. > > (luckily, for connected graphs, the notions are the same) if self.is_connected(): return Graph.is_isomorphic(self) else: raise ValueError("No idea o

Re: [sage-devel] Re: sage compiling problem AMD

On 2012-07-06 14:26, Volker Braun wrote: > The install.log is very confusing, it does not contain the output of the > atlas spkg-install build script (only the atlas make output). The only > reason that I can think of would be if some the build processes were > killed, either because your machine r

Re: [sage-devel] Re: Code duplication and aliases in methods

> I forgot to mention one of the main advantages of (logically) immutable > objects (better late than never): You cannot cache anything if you allow an > object representing one mathematical entity to be modified into something > completely different. Now perhaps you only care about having the worl

[sage-devel] Re: sage compiling problem AMD

The install.log is very confusing, it does not contain the output of the atlas spkg-install build script (only the atlas make output). The only reason that I can think of would be if some the build processes were killed, either because your machine ran out of memory or a hardware defect. On T

Re: [sage-devel] sage compiling problem AMD

Hi Goutam On 6 July 2012 14:06, Goutam Paul wrote: > Hi Jan, > > Thanks for the reply. > > There is only one error file. Please find attached. > The error_.tgz means replace with your architecture, e.g. i386 or x86. So the filename is a little different. Regards, Jan -- .~. /V\ Jan

Re: [sage-devel] Re: Code duplication and aliases in methods

On 2012-07-06 14:10, Nathann Cohen wrote: > Then, of course, we would have to change the is_isomorphic function (it > does not take the bipartition into account). Indeed, if I create a BipartiteGraph object I would expect the is_isomorphic() function to check for isomorphism *as bipartite graphs*.

Re: [sage-devel] Re: Code duplication and aliases in methods

> A BipartiteGraph object should not just be a graph which happens to be > bipartite. O_O What about giving them a different name then ? If Bipartite graphs are "not just Bipartite graphs" ? :-p > The BipartiteGraph object should have additional structure, > namely the vertex partition. As

[sage-devel] Re: Runtimes of binary versus from-source

The next version of ATLAS will have "generic" presets which will be used e.g. if throttling is enabled. This should greatly reduce the risk of mis-tuned ATLAS installs. On Friday, July 6, 2012 12:58:42 PM UTC+1, Dima Pasechnik wrote: > > What is tuned on one host can be mis-tuned on another. >

Re: [sage-devel] Re: Code duplication and aliases in methods

Hell Birk !!! > Why does the graph complement G make a copy the graph itself and then > changes the edges? I think "G = copy(self)" is the root of problem. The > graph and its complement are too different: in general, properties like > bipartitness, connectedness, > col

[sage-devel] Re: Runtimes of binary versus from-source

On Friday, 6 July 2012 18:18:54 UTC+8, Volker Braun wrote: > > A 20x speedup seems to be a bit too good to be true. It could be that the > binary has a botchered (mis-tuned) ATLAS install. What is tuned on one host can be mis-tuned on another. Nothing strange about this. Perhaps a binary ins

Re: [sage-devel] Runtimes of binary versus from-source

Hi On 6 July 2012 12:25, Jeroen Demeyer wrote: > On 2012-07-06 12:19, Jan Groenewald wrote: > > Yes, it was on the same host, and two or three runs of each gave > > the same results. > And were the Sage sources compiled in both cases as 64-bit? And was it > the same Sage version? > Yes, 5.0.1.

Re: [sage-devel] Runtimes of binary versus from-source

On 2012-07-06 12:19, Jan Groenewald wrote: > Yes, it was on the same host, and two or three runs of each gave > the same results. And were the Sage sources compiled in both cases as 64-bit? And was it the same Sage version? -- -- To post to this group, send an email to sage-devel@googlegroups.c

Re: [sage-devel] Runtimes of binary versus from-source

Hi On 6 July 2012 10:59, Jeroen Demeyer wrote: > On 2012-07-06 10:50, Jan Groenewald wrote: > > Hi > > > > On 5 July 2012 12:40, Jan Groenewald > > wrote: > > > > As an interesting aside, > > > > This problem, when running succesfully, on Ubuntu 11.04, took this

[sage-devel] Re: Runtimes of binary versus from-source

A 20x speedup seems to be a bit too good to be true. It could be that the binary has a botchered (mis-tuned) ATLAS install. I guess its possible to have that kind of speedup, but only with very specific problems that immensely profit from SSE3/4/AVX. On Friday, July 6, 2012 9:50:37 AM UTC+1,

Re: [sage-devel] Re: Code duplication and aliases in methods

On Friday, July 6, 2012 8:41:26 AM UTC+1, Birk Eisermann wrote: > > Somehow I agree that many algorithms do not change the graph and > therefore, the graph classes could be immutable. > I forgot to mention one of the main advantages of (logically) immutable objects (better late than never): You

Re: [sage-devel] Re: [sage-support] Re: Sage fails to run python script correctly

If you caan ssh from these machines to boxen then it will be good enough. -- -- 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

Re: [sage-devel] Runtimes of binary versus from-source

On 2012-07-06 10:50, Jan Groenewald wrote: > Hi > > On 5 July 2012 12:40, Jan Groenewald > wrote: > > As an interesting aside, > > This problem, when running succesfully, on Ubuntu 11.04, took this long > > from upstream sage binary: 264 seconds > from s

[sage-devel] Runtimes of binary versus from-source

Hi On 5 July 2012 12:40, Jan Groenewald wrote: > As an interesting aside, > > This problem, when running succesfully, on Ubuntu 11.04, took this long > > from upstream sage binary: 264 seconds > from sage source compiled: 11 seconds I'd like to demonstrate to students why this difference exist

Re: [sage-devel] Re: Code duplication and aliases in methods

On 2012-07-06 09:41, Birk Eisermann wrote: > To me, BipartiteGraph(n) does not make sense. It is a graph without > edges. Trying to find out to which partition class vertex 0 belongs to > (G=BipartiteGraph(3); G.) I was struck by this immense list of more > than 270 functions. I found that G.Bipart

Re: [sage-devel] Re: Code duplication and aliases in methods

Hello everyone! Here are my answers to these problems. Feel free to comment! @ Nathann 1) Some history : the BipartiteGraph class. > > > Try the following : >> sage: BipartiteGraph(graphs.CompleteBipartiteGraph(3,3)).complement() >> > Why does the graph complement G make a copy the graph itself

[sage-devel] Please test sage-5.1.rc1

Because many of the Sage testing machines (redhawk and all of Skynet) are down, version sage-5.1.rc1 has been tested much less than usual. So, please build sage-5.1.rc1 and report unexpected problems, especially if you have an unusual system. Downloads at: http://www.sagemath.org/download-latest.