Re: [sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread William Stein
On Sat, Jun 1, 2013 at 3:47 PM, mmarco wrote: > >>I haven't tested it, ... Why is it suboptimal? > > I used the word "suboptimal" to reffer to the virtualbox based > solution, not to the cygwin one. > > If by "native" you mean "without cygwin"... i am afraid that that we > would be very far away

Re: [sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread Eviatar
On Thursday, 30 May 2013 12:21:25 UTC-7, rjf wrote: > I repeat. Generating random arguments is not sensible. (Incidentally, > you will still need to be able to generate the correct answers for these > functions. This seems to have been overlooked. > What do you do if your benchmark test shows sl

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread mmarco
>I haven't tested it, ... Why is it suboptimal? I used the word "suboptimal" to reffer to the virtualbox based solution, not to the cygwin one. If by "native" you mean "without cygwin"... i am afraid that that we would be very far away from that. Not only from the sage side (at the end of the d

[sage-devel] Re: GSoC "New decoding error-correcting codes algorithm for Sage"

2013-06-01 Thread mmarco
Welcome on board, Veronica. Please keep us up to date to your progress. I am your mentor, but i am sure the rest of the sage community would like to have you involved. Just a little clarification: Veronica has been selected under the umbrella of lmonade, even thoigh her work will be focused on sa

[sage-devel] Re: recompilation with "sage -clone" and after "sage -sync-build"

2013-06-01 Thread leif
leif wrote: leif wrote: John H Palmieri wrote: Is there a ticket for the sage-sync-build problem? Not yet. There are a couple of ways to (quickly or temporarily) "fix" this: 1) Unmerge #14570, which doesn't fix a bug, but only introduces a new (btw. non-configurable) feature. [A bit odd, e

Re: [sage-devel] LELA for matrices?

2013-06-01 Thread Charles Bouillaguet
My understanding is that only a very small subset of linbox is wired into Sage. In particular, all the iterative methods for the [rank/minpoly/charpoly/det] of sparse matrices are not accessible yet, but they are Linbox's strong point. Currently, sparse matrices are converted to dense ones, and

Re: [sage-devel] LELA for matrices?

2013-06-01 Thread Martin Albrecht
Hi, as far as I know LELA does not support the same operations as LinBox, it's not a straight-forward fork but a re-implementation of a subset (that's my understanding, anyway). it has some advantages, i.e., that some bits nicely generic, i.e., it should be fairly easy to add new matrix types b

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread leif
rjf wrote: On Friday, May 31, 2013 5:25:39 AM UTC-7, kcrisman wrote: I think the mentor thing is a red herring, though; the number of projects proposed on Windows probably would roughly match the number of mentors (at least by proportion), because you wouldn't likely get int

[sage-devel] LELA for matrices?

2013-06-01 Thread Volker Braun
I would like to have some discussion about the roadmap for matrices in Sage. It seems that linbox has essentially been forked by LELA (http://www.singular.uni-kl.de/lela). Since it optionally contains M4RI, one would think that it is a good fit for Sage, too. Has anybody given any thoughts to s

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread Harald Schilly
On Saturday, June 1, 2013 4:51:39 PM UTC+2, rjf wrote: > Lisp Programmer $95,000. > I raise you the VAX Mainframe: $100,000 http://www.indeed.com/salary?q1=vax+mainframe Welcome to the cloud! Could we stop this pointless "discussion" please? -- You received this message bec

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread leif
rjf wrote: On Friday, May 31, 2013 3:21:06 AM UTC-7, Volker Braun wrote: On Friday, May 31, 2013 7:39:02 AM UTC+1, rjf wrote: Interesting perspective. Where did you get the $10k/year difference? http://www.indeed.com/salary?q1=Unix+System+Administrator&q2=windows+System+Admin

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread rjf
On Saturday, June 1, 2013 6:16:59 AM UTC-7, mmarco wrote: > > > > On the other hand, there are people working on a cygwin port. I > haven't tested it, ... Why is it suboptimal? (one guess: you can't > have a one-click windows installer?) I thought this had been done some time ago -- a cygwn s

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread rjf
On Friday, May 31, 2013 5:25:39 AM UTC-7, kcrisman wrote: > > >I think the mentor thing is a red herring, though; the number of > projects proposed on Windows probably would roughly match the number of > mentors (at least by proportion), because you wouldn't likely get > interested in Sage

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread rjf
On Friday, May 31, 2013 3:21:06 AM UTC-7, Volker Braun wrote: > > On Friday, May 31, 2013 7:39:02 AM UTC+1, rjf wrote: > >> Interesting perspective. Where did you get the $10k/year difference? >> > > > http://www.indeed.com/salary?q1=Unix+System+Administrator&q2=windows+System+Administrator > >

[sage-devel] Re: 3 GSoC projects for Sage

2013-06-01 Thread mmarco
I know that this is not exactly about the windows port situation, but still, it is closely related to the sage-on-windows issue: On the project ideas suggestions that were proposed by sage, there was one dedicated to writing a GUI to handle the sage installation in windows. No student decided to p

[sage-devel] Re: recompilation with "sage -clone"

2013-06-01 Thread leif
leif wrote: John H Palmieri wrote: Is there a ticket for the sage-sync-build problem? Not yet. There are a couple of ways to (quickly or temporarily) "fix" this: 1) Unmerge #14570, which doesn't fix a bug, but only introduces a new (btw. non-configurable) feature. [A bit odd, especially sin

[sage-devel] Re: recompilation with "sage -clone"

2013-06-01 Thread leif
John H Palmieri wrote: On Thursday, May 30, 2013 9:57:07 PM UTC-7, leif wrote: leif wrote: > Looks like reinstalling the Sage library spkg would meanwhile also > trigger the rebuild of *all* extension modules; not sure since when > though... (seen with Sage 5.10.beta5 at leas