Re: [sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Robert Bradshaw
On Mon, Jun 30, 2014 at 3:00 AM, Dima Pasechnik wrote: > On 2014-06-30, Nathann Cohen wrote: >> Hello everybody ! >> >> Here is the problem : we need in the designs code a table of 10 000 >> integers available in a book. I turned this into a file. >> >> 1) It would be ugly to copy/paste that in t

[sage-devel] Re: Control Systems Toolbox

2014-06-30 Thread Robert Dodier
On 2014-06-30, Salvatore Giorgi wrote: > I am a PhD student in electrical engineering and wanted to contribute to > Sage. As my research is in controls, I thought a control systems toolbox, > similar to Matlab or Maple, might be interesting. Is this something Sage > would want? > > I know ar

[sage-devel] Re: [sage-cloud] Re: network access from projects

2014-06-30 Thread William Stein
On Mon, Jun 30, 2014 at 10:18 PM, Morteza Milani wrote: > Hi William, > > Do you think you can enable network access for my project with id > "eda0377d-48b9-456f-8ddf-b8add11febf6" ? Done. > I work on protein structures and I usually need to download protein data > files from rcsb.org. Cool.

[sage-devel] What's this? New Jacobi Iterative Method

2014-06-30 Thread Stephen Kauffman
Just curious about a new article just read, Jacobi Iterative Method: 19th Century Math Gets A 21st Century Makeover: http://www.science20.com/news_articles/jacobi_iterative_method_19th_century_math_gets_a_21st_century_makeover-139626 where speed improved 200 times. -Steve -- You received this

[sage-devel] Re: Best practice when working on multiple (kind of related) tickets

2014-06-30 Thread Volker Braun
Depends on what "related" means, really. Ideally you have a directed graph of dependencies a->b->c. If you can't order the tickets then really you only have one ticket. If you haven't shared the branches yet then it would be nice to clean up the commits, but its in no way required. Don't rewri

Re: [sage-devel] Re: How to simplify square roots

2014-06-30 Thread rjf
On Monday, June 30, 2014 10:24:39 AM UTC-7, William wrote: > > On Mon, Jun 30, 2014 at 9:29 AM, Ondřej Čertík > wrote: > > Thanks Volker for the tip, that does the job. More comments below: > > Another comment. Evidently Sage uses **Maxima** for > rational_simplify, hence the integer factori

[sage-devel] Control Systems Toolbox

2014-06-30 Thread Salvatore Giorgi
Hello, I am a PhD student in electrical engineering and wanted to contribute to Sage. As my research is in controls, I thought a control systems toolbox, similar to Matlab or Maple, might be interesting. Is this something Sage would want? I know are already similar toolboxes written in Pytho

[sage-devel] Best practice when working on multiple (kind of related) tickets

2014-06-30 Thread Vincent Knight
Dear all, James Campbell and I have been working on 3 related tickets (http://trac.sagemath.org/ticket/16331, http://trac.sagemath.org/ticket/16332, http://trac.sagemath.org/ticket/16333). We pushed 16332 to trac a while ago and have an almost positive review and have since been busy with 163

Re: [sage-devel] Re: How to simplify square roots

2014-06-30 Thread Ondřej Čertík
On Mon, Jun 30, 2014 at 11:23 AM, William Stein wrote: > On Mon, Jun 30, 2014 at 9:29 AM, Ondřej Čertík > wrote: >> Thanks Volker for the tip, that does the job. More comments below: > > Another comment. Evidently Sage uses **Maxima** for > rational_simplify, hence the integer factorization tha

[sage-devel] PSA: Review Moar

2014-06-30 Thread Martin Albrecht
Hi, Sage Days 59 is about to wrap up. A few bugs were fixed and are awaiting review on Trac: http://trac.sagemath.org/query?status=needs_info&status=needs_review&keywords=~sd59 Please take a few moments to check that list and review some patches. It would be a shame to let them bitrot. On

Re: [sage-devel] Re: How to simplify square roots

2014-06-30 Thread William Stein
On Mon, Jun 30, 2014 at 9:29 AM, Ondřej Čertík wrote: > Thanks Volker for the tip, that does the job. More comments below: Another comment. Evidently Sage uses **Maxima** for rational_simplify, hence the integer factorization that is required to do this is not-surprisingly insanely stupidly slow

Re: [sage-devel] Re: How to simplify square roots

2014-06-30 Thread Ondřej Čertík
Thanks Volker for the tip, that does the job. More comments below: On Sun, Jun 29, 2014 at 11:52 PM, John Cremona wrote: > Be careful though: > > sage: (sqrt(-2)*sqrt(-3)).simplify_radical() > -sqrt(3)*sqrt(2) > > i.e. you cannot use sqrt(a)*sqrt(b)=sqrt(a*b) everywhere without > reaching a contr

Re: [sage-devel] Make a trivial spkg standard immediately

2014-06-30 Thread William Stein
On Mon, Jun 30, 2014 at 1:04 AM, Nathann Cohen wrote: > Hello everybody ! > > Here is the problem : we need in the designs code a table of 10 000 integers > available in a book. I turned this into a file. > > 1) It would be ugly to copy/paste that in the python code > 2) I created a .txt file in c

Re: [sage-devel] Re: How to simplify square roots

2014-06-30 Thread kcrisman
On Monday, June 30, 2014 1:52:50 AM UTC-4, John Cremona wrote: > > Be careful though: > > sage: (sqrt(-2)*sqrt(-3)).simplify_radical() > -sqrt(3)*sqrt(2) > > i.e. you cannot use sqrt(a)*sqrt(b)=sqrt(a*b) everywhere without > reaching a contradiction. > > sage: bool( (sqrt(-2)*sqrt(-3)) == sq

Re: [sage-devel] content of polynomials

2014-06-30 Thread John Cremona
That sounds OK -- yes, it must be possible to return the content as a number without any complicated construction, especially as the content (as a number) will be returned by some lower-level library such as FLINT. John On 30 June 2014 08:53, Vincent Delecroix <20100.delecr...@gmail.com> wrote: >

[sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Volker Braun
On Monday, June 30, 2014 6:29:07 AM UTC-4, Dima Pasechnik wrote: > > Or, maybe it can be made a Python pickle? > Why? To make loading marginally faster? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop rec

Re: [sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Francois Bissey
What about making it a sage object (.sobj), as in the conway polynomial database? Look its spkg-install, of course it may be a new spkg but if it is just data I don't see why we cannot fast track it to standard. François On 30/06/2014, at 22:36, Nathann Cohen wrote: >> well, 500 lines of number

Re: [sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Nathann Cohen
> well, 500 lines of numbers. That's OK. > Or, maybe it can be made a Python pickle? I would say that a pickly is the same as a .txt, isn't it ? That you cannot load it at runtime unless it is in SAGE_SHARED. But you are probably right with the python file. Best and easiest ?... Nathann -- You

[sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Dima Pasechnik
On 2014-06-30, Nathann Cohen wrote: >> IMHO it's OK to have it in a .py(x) file... > > http://www.steinertriples.fr/ncohen/tmp/MOLS_table.txt > > Imagine this with a fixed line with of 80 :-P well, 500 lines of numbers. That's OK. Or, maybe it can be made a Python pickle? > > Nathann > -- You r

Re: [sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Nathann Cohen
> IMHO it's OK to have it in a .py(x) file... http://www.steinertriples.fr/ncohen/tmp/MOLS_table.txt Imagine this with a fixed line with of 80 :-P Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop r

[sage-devel] Re: Make a trivial spkg standard immediately

2014-06-30 Thread Dima Pasechnik
On 2014-06-30, Nathann Cohen wrote: > Hello everybody ! > > Here is the problem : we need in the designs code a table of 10 000 > integers available in a book. I turned this into a file. > > 1) It would be ugly to copy/paste that in the python code IMHO it's OK to have it in a .py(x) file... > 2)

Re: [sage-devel] Make a trivial spkg standard immediately

2014-06-30 Thread Nathann Cohen
Yo ! > The reviewer strongly supports the idea of having it in standard! Yep sorry, the message could appear to imply the opposite ^^; It is just that it really takes a lot of time to add 10 000 integers in Sage -_- Nathann -- You received this message because you are subscribed to the Google

Re: [sage-devel] Make a trivial spkg standard immediately

2014-06-30 Thread Vincent Delecroix
Hello, The reviewer strongly supports the idea of having it in standard! Vincent PS: ticket number is #16541. 2014-06-30 10:04 UTC+02:00, Nathann Cohen : > Hello everybody ! > > Here is the problem : we need in the designs code a table of 10 000 > integers available in a book. I turned this int

[sage-devel] Make a trivial spkg standard immediately

2014-06-30 Thread Nathann Cohen
Hello everybody ! Here is the problem : we need in the designs code a table of 10 000 integers available in a book. I turned this into a file. 1) It would be ugly to copy/paste that in the python code 2) I created a .txt file in combinat/design/ for this data 3) Turns out that you cannot read a .

Re: [sage-devel] content of polynomials

2014-06-30 Thread Vincent Delecroix
Dear John, Thanks for your answer. The method content for dense polynomial over ZZ is implemented at a very low level... I am sure somebody cares about its speed. In particular, I am not in favour of pol.content().gen() which needs to build the ideal. Your flag idea is nice. For the deprecation

Re: [sage-devel] content of polynomials

2014-06-30 Thread John Cremona
I'm not sure about the name content_gen, or whether it is necessary if pol.content().gen() works. Also, I suspect that there may be quite a lot of code out there which this change will break. Would it be possible to make the change you suggest for content() but to have a parameter flag such as '

Re: [sage-devel] content of polynomials

2014-06-30 Thread Bruno Grenet
Salut Vincent, I was tempted to open a ticket for this "bug" (or is it a feature?), so I am very much in favor of your proposition! Best wishes, Bruno Le dim. 29 juin 2014 23:32:42 CEST, Vincent Delecroix a écrit : Hello, While reviewing #16516 I bumped into the following bug {{{ sage: R. =