[sage-devel] Congratulations to IPython
IPython has won the 2012 Free Software foundation award for the Advancement of Free Software ( http://www.fsf.org/news/2012-free-software-award-winners-announced-2). Well deserved! David -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released
Might be because of the SIGCHLD handler issue in libgap that has been waiting for a review at http://trac.sagemath.org/14039. See also http://trac.sagemath.org/14323 for a more temporary fix. Though if thats the root cause then I don't understand why it would not be triggered for everyone... On Saturday, March 23, 2013 4:18:33 PM UTC+1, John Cremona wrote: > > On 19 March 2013 15:16, John Cremona > > wrote: > > Exactly the same happened to me: 2 rogue ecl processes consuming lots > > of RAM. This is on ubuntu, same set up worked fine with 5.8 at the > > same time. > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: sagenb.org is down
On 3/23/13 10:55 AM, gerald wenzel wrote: sagenb.org is returning 503 errors: 503 Service Unavailable No server is available to handle this request. You're right. Thanks. I'm restarting it now. Jason -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] sagenb.org is down
sagenb.org is returning 503 errors: 503 Service Unavailable No server is available to handle this request. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released
While I still think there is a serious issue here, friends will be delighted to hear that I was able to get onto the server in question and kill the two offending ecl processes. I do not know why, but while it was impossible to login from off campus, I could login to a different machine on the university network and login from there to the machine having difficulties. No doubt there is a logical reason for that! John On 23 March 2013 15:18, John Cremona wrote: > On 19 March 2013 15:16, John Cremona wrote: >> Exactly the same happened to me: 2 rogue ecl processes consuming lots >> of RAM. This is on ubuntu, same set up worked fine with 5.8 at the >> same time. > > This report provoked almost no reaction in a thread dominated by vital > discussion of colour schemes. > > I made the mistake of starting "make ptestlong" on a 5.9.beta1 build > last night without checking that that anything had been done so fix > this catastrophic problem (and without creative use of ulimit, I > admit). This morning the machine responds to ping but we cannot login > to it. > > I will not be able to get physical access to the machine room until > Monday at the earliest to reset the machine. In the meantime does > anyone have any suggestions on how to get into it? Increasing the > ConnectTimeout option for ssh does not help: after a few minutes the > connection is broken with a message saying that the server is not > responding. > > How come testing sage-5.9.beta? has not had a similar effect on all > other Sage developers? > > John > >> >> John >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: [sage-release] Re: sage-5.9.beta0 released
On 19 March 2013 15:16, John Cremona wrote: > Exactly the same happened to me: 2 rogue ecl processes consuming lots > of RAM. This is on ubuntu, same set up worked fine with 5.8 at the > same time. This report provoked almost no reaction in a thread dominated by vital discussion of colour schemes. I made the mistake of starting "make ptestlong" on a 5.9.beta1 build last night without checking that that anything had been done so fix this catastrophic problem (and without creative use of ulimit, I admit). This morning the machine responds to ping but we cannot login to it. I will not be able to get physical access to the machine room until Monday at the earliest to reset the machine. In the meantime does anyone have any suggestions on how to get into it? Increasing the ConnectTimeout option for ssh does not help: after a few minutes the connection is broken with a message saying that the server is not responding. How come testing sage-5.9.beta? has not had a similar effect on all other Sage developers? John > > John > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] new M4RI(E) SPKGs need review
Hi, I've released new versions of M4RI and M4RIE and I'd appreciate if someone could take the time to review the relevant tickets to get these updates into Sage: M4RI:http://trac.sagemath.org/sage_trac/ticket/14335 M4RIE: http://trac.sagemath.org/sage_trac/ticket/14336 # What's new? # ## M4RI ## It's faster! For example. here's matrix multiplication on my computer: n 5.8 vanilla 5.8 + #14335Magma 40960.09s 0.07s 0.10s 81920.67s 0.62s More data here: https://martinralbrecht.wordpress.com/2012/12/21/m4ri-20121224/ (20121224 never made it into Sage) ## M4RIE ## ### Performance ### It extends to degree 16 which means GF(2^e) for 10 < e <= 16 is now *a lot* faster in Sage (i.e., not embarrassingly slow) Here's multiplication for 4096 x 4096 matrices over GF(2^e) extension vanilla with patch magma 2.15-10 e: 1, 0.09s 0.07s 0.10s e: 2, 0.30s 0.22s 0.68s e: 3, 0.64s 0.46s 1.89s e: 4, 0.89s 0.70s 6.35s e: 5, 1.34s 1.05s 92.43s e: 6, 1.77s 1.39s e: 7, 2.22s 1.74s e: 8, 2.72s 2.14s e: 9, 31.21s 5.74s e: 10, 41.42s 7.94s e: 11, long9.31s e: 12, long10.56s e: 13, long56.39s e: 14, long100.64s e: 15, long141.88s e: 16, long199.78s 464.14s I didn't run those marked long because I ran out of RAM, check this though (without patch): sage: A = random_matrix(GF(2^11,'a'),500,500) # ~1/10 of above size sage: B = random_matrix(GF(2^11,'a'),500,500) sage: %time A*B CPU times: user 48.05 s, sys: 0.21 s, total: 48.26 s Wall time: 48.43 s Note that e>8 is not optimised yet. More information here: https://martinralbrecht.wordpress.com/2012/08/23/m4rie- support-for-finite-fields-up-to-degree-16-added/ ### Compilation ### I've split up conversion.c which means I can now do this: $ ulimit -v 196608 && make in the M4RIE directory and M4RIE successfully built with 192MB of virtual memory. Cheers, Martin -- name: Martin Albrecht _pgp: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x8EF0DC99 _otr: 47F43D1A 5D68C36F 468BAEBA 640E8856 D7951CCF _www: http://martinralbrecht.wordpress.com/ _jab: martinralbre...@jabber.ccc.de -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)
On Saturday, March 23, 2013 1:43:05 PM UTC+1, Dima Pasechnik wrote: > Now, if 1, 2, and (1,2) are in your domain, is (2,(1,2)) a tuple? > According to the "minimum depth" rule to guess the default action, it is. > And how many different meanings does ((2,(1,2)),((2,(1,2))) have? > There is a unique guess according to the "minimum depth" rule, if that is not what you want then you have to specify the action explicitly. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: a problem in the new permutation groups code (and a solution ?)
> Say, you have 1, 2, (1,2), (2,(1,2)), and perhaps other stuff in the domain. > How many different meanings does "the orbit of ((2,(1,2)),((2,(1,2)))" have? > How can you guess the "right" action for it? Dima it's getting boring. Let's say that I do not try to guess anything if that's a problem, do we agree that a function named "orbit" which knows the type of its input from the value of "action" wiill never encounter a ambiguous input nor return an ambiguous output ? Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: a problem in the new permutation groups code (and a solution ?)
On 2013-03-23, Volker Braun wrote: > --=_Part_1329_18134862.1364030357521 > Content-Type: text/plain; charset=ISO-8859-1 > > We are talking about guessing the action once and for all for a given > input. You are talking about guessing the action each time a group element > acts in the orbit. I agree that the latter is not consistently doable. But > it is possible to guess the action in the beginning of the orbit > computation, and this is unambiguous. Unless you specify the action explicitly, you will need to run a syntactic parser on the group domain before you can compute an orbit, or do any other sem-trivial computation. Certainly part 2 of http://trac.sagemath.org/sage_trac/ticket/14291#comment:28 will not be possible to achieve. Say, you have 1, 2, (1,2), (2,(1,2)), and perhaps other stuff in the domain. How many different meanings does "the orbit of ((2,(1,2)),((2,(1,2)))" have? How can you guess the "right" action for it? Dima (recycling a part of another message in this thread, sorry) > > Other points that might be nice to implement (but are not on the ticket): > * a switch to optionally print the guess used for the action, maybe > verbose=True or action="guess_verbose". > * allow any python function f(g,x) as action=f > > > > On Saturday, March 23, 2013 9:58:06 AM UTC+1, Dima Pasechnik wrote: >> >> OK, great, so (1,2) is not an element. >> Yet, you take (1,2) as an element when you compute the 3rd element of >> the orbit. Is your implementation of the function going to read your >> mind, to work correctly? >> >> > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)
We are talking about guessing the action once and for all for a given input. You are talking about guessing the action each time a group element acts in the orbit. I agree that the latter is not consistently doable. But it is possible to guess the action in the beginning of the orbit computation, and this is unambiguous. Other points that might be nice to implement (but are not on the ticket): * a switch to optionally print the guess used for the action, maybe verbose=True or action="guess_verbose". * allow any python function f(g,x) as action=f On Saturday, March 23, 2013 9:58:06 AM UTC+1, Dima Pasechnik wrote: > > OK, great, so (1,2) is not an element. > Yet, you take (1,2) as an element when you compute the 3rd element of > the orbit. Is your implementation of the function going to read your > mind, to work correctly? > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: [sage-devel] Re: Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)
> no, the 3rd element is computed using a different meaning of (1,2) than > the one used to compute the 2nd one. > If you used the same meaning for the 2nd as the one for the 3rd, your > 2nd would be (1,1). Then how is your input of type "Tuple of Tuple", sir ? > OK, great, so (1,2) is not an element. > Yet, you take (1,2) as an element when you compute the 3rd element of > the orbit. Is your implementation of the function going to read your > mind, to work correctly? Of course, because the type of the value returned is "A list of tuple of tuple". Hence everything at depth <= 3 is a container,and everything at depth 4 is an element. Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch
Just make the source repository public and cut releases for p_group_cohomology from that. Even without the change to git I think that this is a much better model than putting a repo in a tarball and not have it web accessible. Since we are already planning on hosting our own git repo for Sage it would be easy to also host associated repos, I think. On Saturday, March 23, 2013 8:25:40 AM UTC+1, Simon King wrote: > > The Cython, Python, GAP and Singular code, as well as much of the C > code, is not published elsewhere. That's why I've put it under version > control (but the C-MeatAxe part is not under version control in the > spkg, since C-MeatAxe *is* an independent project). IIRC, people agreed > that this is OK in this case. > > So, where should this code go? > > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-combinat-devel] Re: [sage-devel] Re: Re: Re: a problem in the new permutation groups code (and a solution ?)
> Even if you manage to answer the question above satisfactory, > I still hold that it's not acceptable in the first place to have such > design, > forcing one to jump through hoops for no good reason, in an extendable > system like Sage. This design is CORRECT Dima, if you don't believe so just give me one instance for which there is an uncertainty. OnTupleTupleTupleTupleTuple would tell you that the first 5 layers are NOT elements from the domain, and that only the elements of depth 6 are elements of the domain. Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: [sage-devel] Re: [sage-combinat-devel] Re: Re: Re: Re: a problem in the new permutation groups code (and a solution ?)
Helloo ! > In more detail: one writes a function that can do GAP's OnTuplesTuples action, > without even any action guessing involved (this is trivial code, > right, we have things like this on our ticket?), and asks it to do the > orbit of the tuple of tuples ((1,2),(1,2)). The outcome The output would be [ ((1,2),(1,2)), ((2,(1,2)),(2,(1,2))), (((1,2),1),((1,2),1)) ] What is the problem with that ? If you say OnTupleTuple you know that (1,2) has to be considered as the tuple with two elements 1,2 and we can do the job. You know this because it is an action on a tuple of tuple, the tuple of tuple being ((1,2), (1,2)). So there are two tuples, which are (1,2) and (1,2), each one containing two elments. No way you can confuse this with the element (1,2). > Just as one can derive anything from a False statement, one can always > get into trouble with design that creates counterexamples to foundations > of group theory. Tell me how it is wrong or the mistake I made. Otherwise it works. Nathann -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
[sage-devel] Re: [sage-combinat-devel] Re: Adding data in patch
Hi Keshav, hi all, On 2013-03-23, Keshav Kini wrote: >> Hence, "we don't want to pull in upstream source as well" simply does not >> apply. The question is: Do we want to *remove* source, just because Sage >> is the only project that has this code? > > I would say that yes, we do want to remove it - from the unified > repository. If this is the case, then I think we need a general discussion. My concern is my optional group cohomology package p_group_cohomology (which currently needs work since some internals of Sage have changed). It is an optional spkg and not in the Sage library, since - My Cython and Python code in the package relies on C libraries (a fork of C-MeatAxe), and on GAP code of David Green, which in turn uses executables written in C. If I recall correctly, such stuff should not be in the Sage library. - The package uses the SmallGroups library, which can not be a standard package of Sage because of the licence. Hence, p_group_cohomology can't be standard either. The Cython, Python, GAP and Singular code, as well as much of the C code, is not published elsewhere. That's why I've put it under version control (but the C-MeatAxe part is not under version control in the spkg, since C-MeatAxe *is* an independent project). IIRC, people agreed that this is OK in this case. So, where should this code go? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
