Re: [sage-devel] Pari stack growning out of bounds

On 2012-09-24 22:29, John Cremona wrote: > It seems computationally hard to test if an element of QQbar > is positive What does it even mean for an element of QQbar to be positive? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this gr

[sage-devel] Re: SAGE... other GUI than notebook

On 09/25/2012 03:51 AM, alxy wrote: Ok, sorry for doubbleposting here now. But everything worked now for me, except the notebook of course :P I can still see the frontend with the active worksheets and I´m also able to create new ones, but I cant edit them or write something on them. If I enter

Re: [sage-devel] Pari stack growning out of bounds

On 24 September 2012 21:45, Rob Beezer wrote: > > On Monday, September 24, 2012 1:29:24 PM UTC-7, John Cremona wrote: >> >> Does anyone know why QQbar is being used here? > > > For "simple" graphs, the adjaceny matrix will be symmetric, so the > eigenvalues could go into AA instead of QQbar, but I

Re: [sage-devel] Pari stack growning out of bounds

On Monday, September 24, 2012 1:29:24 PM UTC-7, John Cremona wrote: > > Does anyone know why QQbar is being used here? > For "simple" graphs, the adjaceny matrix will be symmetric, so the eigenvalues could go into AA instead of QQbar, but I would guess the problem (comparison with zero) might

[sage-devel] Re: Pari stack growning out of bounds

Some of your eigenvales (many?) are in QQbar, the field of algebraic numbers. Testing equality in this field is extremely expensive for some reason. Also, sum() is sufficiently generic, that I think it is not very efficient either. A recent patch implements eigenvalues of symmetric matrices w

Re: [sage-devel] Pari stack growning out of bounds

A partial answer is that somehow the elements of the spectrum are being created as elements of QQbar, and must have high degree, so pari is (behind the scenes) trying to compare algebraic numbers of high degree, which is hard as it involves creating number fields of high degree. It seems computati

[sage-devel] Pari stack growning out of bounds

Consider the following program that computes the spectrum and chromatic number of a graph: for g in graphs.nauty_geng(str(7)): s = g.spectrum() g.chromatic_number() This works quickly and like a charm. Now consider the following program that computes something related to the spectrum an

Re: [sage-devel] Re: Cannot set 'ymin' in 'semilogy' plot

Hello! On Mon, 24 Sep 2012 11:07:46 -0700 (PDT) P Purkayastha wrote: > > This is now #13528. Not sure what is causing it though. :) > > We don't touch those parameters while doing log plots, as far as I > can tell. > I have also noticed that if I have several curves on a single 'semilogy'

[sage-devel] Re: SAGE... other GUI than notebook

Ok, sorry for doubbleposting here now. But everything worked now for me, except the notebook of course :P I can still see the frontend with the active worksheets and I´m also able to create new ones, but I cant edit them or write something on them. If I enter the URL (eg http://localhost:8000/ho

[sage-devel] Re: SAGE... other GUI than notebook

Ok.. works now with https://github.com/alxy/sagenb.git -- 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...@googlegr

[sage-devel] Re: SAGE... other GUI than notebook

This leads me to another error: "fatal: http://a...@github.com/ sagenb.git/info/refs not found: ..." I entered my git password before, hope this was right. Am Montag, 24. September 2012 18:26:24 UTC+2 schrieb Volker Braun: > > you are probably behind a firewal

[sage-devel] Re: Cannot set 'ymin' in 'semilogy' plot

On Tuesday, September 25, 2012 1:56:16 AM UTC+8, kcrisman wrote: > > >> >> >In addition to incorrect lower limit of Y axis, the plot using >> > 'semilogy' is also somewhat unstable. If I evaluate the cell time after >> > time without changing its contents, I obtain two alternating variants

[sage-devel] Re: Cannot set 'ymin' in 'semilogy' plot

> > > > >In addition to incorrect lower limit of Y axis, the plot using > > 'semilogy' is also somewhat unstable. If I evaluate the cell time after > > time without changing its contents, I obtain two alternating variants > > of the plot - with two different actual ymin values. > > Off the

[sage-devel] Re: LibGAP spkg vote!

On 09/23/2012 09:40 PM, Volker Braun wrote: LibGAP (the C library interface to GAP) is finally usable and ready to be released into the wild! We will ship it as a separate spkg since * Upstream doesn't build a shared library * The build system is replaced by standard autotools * To avoid symbol c

[sage-devel] Re: Cannot set 'ymin' in 'semilogy' plot

On 09/25/2012 01:36 AM, P Purkayastha wrote: On 09/25/2012 01:00 AM, v...@ukr.net wrote: Hello! I've been experiencing some problems with logarithmic scale plots since the 'semilogy', 'semilogx' and 'loglog' options had been added. For example, when I use the 'semilogy' plot, I can adjust the 'y

[sage-devel] Re: Cannot set 'ymin' in 'semilogy' plot

On 09/25/2012 01:00 AM, v...@ukr.net wrote: Hello! I've been experiencing some problems with logarithmic scale plots since the 'semilogy', 'semilogx' and 'loglog' options had been added. For example, when I use the 'semilogy' plot, I can adjust the 'ymax' value, but not 'ymin' value. 'ym

[sage-devel] Re: Automorphisms of Matrices Under Row/Column Permutations

On Tuesday, 25 September 2012 00:44:56 UTC+8, Volker Braun wrote: > > On Monday, September 24, 2012 5:07:09 PM UTC+1, Dima Pasechnik wrote: > >> I am very curious (I happen to do some work right now on automorphisms of >> "general" polyhedral cones) >> to find out what this normal form is. It's

[sage-devel] Cannot set 'ymin' in 'semilogy' plot

Hello! I've been experiencing some problems with logarithmic scale plots since the 'semilogy', 'semilogx' and 'loglog' options had been added. For example, when I use the 'semilogy' plot, I can adjust the 'ymax' value, but not 'ymin' value. 'ymin' is always set automatically, and not always c

[sage-devel] Re: Automorphisms of Matrices Under Row/Column Permutations

On Monday, September 24, 2012 5:07:09 PM UTC+1, Dima Pasechnik wrote: > I am very curious (I happen to do some work right now on automorphisms of > "general" polyhedral cones) > to find out what this normal form is. It's not described in the PALP > original paper, IMHO. > PS: This might be of

[sage-devel] Re: Automorphisms of Matrices Under Row/Column Permutations

See Section 3.4 of http://arxiv.org/pdf/hep-th/9805190.pdf for the definition of the PALP normal form. On Monday, September 24, 2012 5:07:09 PM UTC+1, Dima Pasechnik wrote: > > I am very curious (I happen to do some work right now on automorphisms of > "general" polyhedral cones) > to find ou

[sage-devel] Re: SAGE... other GUI than notebook

On Tuesday, 25 September 2012 00:19:23 UTC+8, alxy wrote: > > I did not push, I cloned! > > Like so... > > $ git clone g...@github.com:alxy/sagenb.git sagenb-github > > and I first forked it. so where to add a git:// there? > > this looks OK. (In fact I just tried to run this, and it worked for

[sage-devel] Re: SAGE... other GUI than notebook

you are probably behind a firewall that blocks git. Use git over http git clone http://a...@github.com/sagenb.git sagenb-github On Monday, September 24, 2012 5:19:23 PM UTC+1, alxy wrote: > > I did not push, I cloned! > > Like so... > > $ git clone g...@github.com:alxy/sagenb.git sagenb-github

[sage-devel] Re: SAGE... other GUI than notebook

I did not push, I cloned! Like so... $ git clone g...@github.com:alxy/sagenb.git sagenb-github and I first forked it. so where to add a git:// there? Am Montag, 24. September 2012 18:12:56 UTC+2 schrieb Dima Pasechnik: > > > > On Monday, 24 September 2012 23:40:10 UTC+8, alxy wrote: >> >> Thi

[sage-devel] Re: SAGE... other GUI than notebook

On Monday, 24 September 2012 23:40:10 UTC+8, alxy wrote: > > This is hell for windows users... > welcome to the real life, user :) > > Installed git via "yum install git", but now I always get "fatal: The > remote end hung up unexpectedly". > I think, I read something about a perl error whil

[sage-devel] Re: Automorphisms of Matrices Under Row/Column Permutations

I am very curious (I happen to do some work right now on automorphisms of "general" polyhedral cones) to find out what this normal form is. It's not described in the PALP original paper, IMHO. On Thursday, 16 August 2012 23:52:58 UTC+8, Volker Braun wrote: > > The PALP normal form is already

[sage-devel] Re: SAGE... other GUI than notebook

This is hell for windows users... Installed git via "yum install git", but now I always get "fatal: The remote end hung up unexpectedly". I think, I read something about a perl error while git installation, but I´m not sure. I also installed perl after that, but the error stays the same. Is the

[sage-devel] Re: SAGE... other GUI than notebook

You need to log in as the user "sage" with password "sage" (try ctrl-alt-Fn until you find a free console). The Sage install is under his home directory. On Monday, September 24, 2012 3:36:06 PM UTC+1, alxy wrote: > > Mh, ok, this also works on VM :) > > And I also managed to start the termina

[sage-devel] Re: SAGE... other GUI than notebook

Mh, ok, this also works on VM :) And I also managed to start the terminal by pressing strg/ctrl + alt + f1. But as I dont know too many commands, i stack here. How to go on? I tried "ls /" to list the directories, but there is nothing like "sage", just "root", "dev", "bin" and so on... So where

Re: [sage-devel] LibGAP spkg vote!

On Sun, Sep 23, 2012 at 9:40 AM, Volker Braun wrote: > LibGAP (the C library interface to GAP) is finally usable and ready to be > released into the wild! We will ship it as a separate spkg since > * Upstream doesn't build a shared library > * The build system is replaced by standard autotools

[sage-devel] Re: Automorphisms of Matrices Under Row/Column Permutations

I have now uploaded a patch that includes the native algorithm, an alternate algorithm and an implementation of the algorithm to calculate a normal form for Laurent polynomials. This patch out of necessity introduces automorphisms of lattice polytopes and as discussed above permutations acting

[sage-devel] Re: wrapping more GSL distribution to SAGE // RealDistribution design problems

On Sep 23, 3:32 pm, Pablo De Napoli wrote: > Hi, > > I'm teaching a probability course right now, and using Sage for doing > some graphics > for my class notes. > I've found that GSL implements a lot of probability distributions that > are not wrapped by Sage. > The problem was reported at > > h

[sage-devel] Re: Opinion on "assert"

On 9/24/12 3:55 AM, Nicolas M. Thiery wrote: That being said, if there is a way to raise ValueError in a way that can be turned off like for assertions, I am happy to change my mind! (I am missing this from MuPAD; we could even change this at runtime which was really cool),. Of course, we can a

[sage-devel] Re: LibGAP spkg vote!

On Sep 23, 9:40 am, Volker Braun wrote: > LibGAP (the C library interface to GAP) is finally usable and ready to be > released into the wild! We will ship it as a separate spkg since >   * Upstream doesn't build a shared library >   * The build system is replaced by standard autotools >   * To a

Re: [sage-devel] Re: LibGAP spkg vote!

A lot of things should work if you just replace gap with libgap (or import libgap as gap). One difference is that the libgap() element constructor prioritizes creating the analogous gap object, in particular for strings: sage: libgap('string') "string" sage: type(_) If you want to evaluate a g

[sage-devel] Re: Voronoi diagram

Thanks for the encouraging replies! I opened a ticket: http://trac.sagemath.org/sage_trac/ticket/13517 moritz -- 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

Re: [sage-devel] Re: LibGAP spkg vote!

On Sun, Sep 23, 2012 at 1:00 PM, mmarco wrote: > >> How hard will porting code be? How much different is the interface >> that Volker ended up developing for libGAP? >> > > Porting my fpgroups code was pretty much straightforward. It is > (almost) a mechanical work... but a work that has to be do

Re: [sage-devel] Error in eigenmatrix_right or in documentation

On 24/09/2012, at 4:29 PM, ancienthart wrote: > Is *this* an error ... :/ Yes. In the documentation, not the test. See http://trac.sagemath.org/sage_trac/ticket/13524 > > On Monday, 24 September 2012 14:25:38 UTC+10, ancienthart wrote: >> >> Hi everyone, >> In the documentation: >> >> http://w

Re: [sage-devel] Opinion on "assert"

Le 24/09/2012 11:13, Volker Braun a écrit : On Monday, September 24, 2012 9:55:34 AM UTC+1, Nicolas M. Thiéry wrote: - It's very concise, readable and to the point. Compare: assert i > 0 With: if i <= 0: raise ValueError("i should be a positive integer") The problem is that

Re: [sage-devel] Opinion on "assert"

On Monday, September 24, 2012 9:55:34 AM UTC+1, Nicolas M. Thiéry wrote: > - It's very concise, readable and to the point. Compare: > assert i > 0 > With: > if i <= 0: > raise ValueError("i should be a positive integer") > The problem is that the error message i

Re: [sage-devel] LibGAP spkg vote!

>LibGAP (the C library interface to GAP) is finally usable and >ready to be released into the wild! Yippee!!! That will make such a difference! >Per the usual rules, new spkgs need a vote so now is your chance to be >heard ;-) +1 without a question. Thanks!

Re: [sage-devel] Re: Opinion on "assert"

On Mon, Sep 24, 2012 at 01:54:26AM -0700, Volker Braun wrote: >There is a temptation to use assert instead of "if ... raise >Exception(msg)" since its shorter and you don't have to write a good error >message. But then, that is exactly what is wrong with it: Instead of >getting an e

Re: [sage-devel] Opinion on "assert"

On 2012-09-24 10:55, Nicolas M. Thiery wrote: > I see the point of writing nice ValueError error messages for the most > public or non speed-critical functions. But for other functions I > think we should allow for using asserts. I like this compromise. I think the default should be "don't use ass

Re: [sage-devel] Opinion on "assert"

Hi Jeroen, Thanks for raising this point! On Mon, Sep 24, 2012 at 09:24:37AM +0200, Jeroen Demeyer wrote: > In Sage, I have seen some quite some places where assert/AssertionError > is used for control flow, where an > > if condition: > raise ValueError("...") # or other exception

[sage-devel] Re: Opinion on "assert"

Agreed. There is a temptation to use assert instead of "if ... raise Exception(msg)" since its shorter and you don't have to write a good error message. But then, that is exactly what is wrong with it: Instead of getting an error that'll point the user to what went wrong, there is just Assert

[sage-devel] Opinion on "assert"

In Sage, I have seen some quite some places where assert/AssertionError is used for control flow, where an if condition: raise ValueError("...") # or other exception would be the right thing to use instead of an assert. I find this bad, because an assert checks something which should alway