On May 29, 3:32 pm, "Jason B. Hill" wrote:
> It is a strange business model, but in certain circles it is well-known.
>
> Just last week, one of my old professors told me that he had bought a
> subscription to Magma for his coding theory + polynomial rings research.
Still, it's not a commercial
It is a strange business model, but in certain circles it is well-known.
Just last week, one of my old professors told me that he had bought a
subscription to Magma for his coding theory + polynomial rings research. He
works at a university/department with all Windows machines. He was confused
by
On 5/29/10 4:31 PM, Ryan Hinton wrote:
sage: import numpy as np
> sage: t1 = np.array([3+1])
> sage: t2 = t1[0]
> sage: t3 = 0
> sage: max(t2, t3)
> 0
> sage: min(t2, t3)
I just reproduced the bug on sagenb.org and an almost-stock 4.4.2
running on linux. However, my stock 4.4.2 (
On 29 May 2010 22:27, Dr. David Kirkby wrote:
> On 05/29/10 10:12 PM, rjf wrote:
>>
>> I would be curious as to whether a Magma commercial license has ever
>> been sold.
>
> Based on the contents of the MAGMA web site, I'm amazed they manage to sell
> any copies at all. (Student, academic, commeri
I reproduced the error on alpha.sagenb.org.
sage: version()
'Sage Version 4.4.1, Release Date: 2010-05-02'
And the max/min names are not overloaded.
sage: min
I agree the behavior is strange. I had a hard time reproducing it at
first. Again, ideas are welcome.
- Ryan
On May 29, 3:10 pm, Ja
On 05/29/10 10:12 PM, rjf wrote:
I would be curious as to whether a Magma commercial license has ever
been sold.
Based on the contents of the MAGMA web site, I'm amazed they manage to sell any
copies at all. (Student, academic, commerical or whatever other licenses they
sell). I know one can
I would be curious as to whether a Magma commercial license has ever
been sold.
--
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.goog
On 5/29/10 3:58 PM, Ryan Hinton wrote:
The following results are strange.
sage: import numpy as np
sage: t1 = np.array([3+1])
sage: t2 = t1[0]
sage: t3 = 0
sage: max(t2, t3)
0
sage: min(t2, t3)
4
I get the same results putting t2 and t3 in a tuple for the other max/
min calling convention. But
The following results are strange.
sage: import numpy as np
sage: t1 = np.array([3+1])
sage: t2 = t1[0]
sage: t3 = 0
sage: max(t2, t3)
0
sage: min(t2, t3)
4
I get the same results putting t2 and t3 in a tuple for the other max/
min calling convention. But the comparison operator seems to be fine
On 05/29/10 07:32 PM, William Stein wrote:
On Sat, May 29, 2010 at 8:49 AM, Dr. David Kirkby
wrote:
For what it is worth, I requested a quote for a Magma license for commercial
purposes a couple of weeks ago. I intended to put the amount in a slide I
did for the London OpenSolaris User Group (
On 5/29/10 1:32 PM, William Stein wrote:
On Sat, May 29, 2010 at 8:49 AM, Dr. David Kirkby
wrote:
For what it is worth, I requested a quote for a Magma license for commercial
purposes a couple of weeks ago. I intended to put the amount in a slide I
did for the London OpenSolaris User Group (LO
On Sat, May 29, 2010 at 2:32 PM, William Stein wrote:
> Thanks for asking. I had always wondered about this. It looks like
> the price for that market is nearly the same as that for Mathematica,
> Maple, or Matlab, right?
>
Maple last time I checked was about $2500. Academic licenses were $125
On Sat, May 29, 2010 at 8:49 AM, Dr. David Kirkby
wrote:
> For what it is worth, I requested a quote for a Magma license for commercial
> purposes a couple of weeks ago. I intended to put the amount in a slide I
> did for the London OpenSolaris User Group (LOSUG), but never got the price
> in time
Keep in mind that Magma's pricing is dictated by the architecture of the
machine(s) on which it will be run, namely by core count of the processors.
If someone were interested in using the newer generation of SPARC
processors, or any machine with more than 4 cores, then the price does go
up.
My in
For what it is worth, I requested a quote for a Magma license for commercial
purposes a couple of weeks ago. I intended to put the amount in a slide I did
for the London OpenSolaris User Group (LOSUG), but never got the price in time.
They support at least Windows, Linux, OS X, Solaris SPARC an
On 29 Mai, 09:45, Robert Bradshaw
wrote:
> On May 28, 2010, at 9:09 PM, Kwankyu Lee wrote:
> > I am wondering why the gsl directory occupy the top-level place in the
> > Sage library. I suppose that the top-level directories represent big
> > themes, but gsl is just a particular library. As gsl is
Yes, the spkg works for me too.
Thank you,
Johannes
On May 29, 12:01 pm, "Dr. David Kirkby"
wrote:
> On May 29, 11:00 am, "Dr. David Kirkby"
> wrote:
>
>
>
> > On May 29, 10:00 am, msapfiri wrote:
>
> > > Hi all,
> > > I just compiled SAGE 4.4.2 on my MacbookPro running Ubuntu 10.04 (64
> > > b
On May 26, 10:56 pm, Robert Bradshaw
wrote:
> I didn't know anyone even looked at those numbers--maybe it would be
> better to put it in the *past* so people know not to trust it. I just
> deleted the date for now, though hopefully June is still a realistic
> target.
>
> - Robert
IMHO, Sage
On May 26, 9:23 pm, kcrisman wrote:
> Wouldn't it be easiest for someone to change the 5.0 release date
> thingie on Trac to "sometime in June, but may be pushed to July or
> later in order to fulfill goals (Cygwin, etc.)"? This seems like even
> more of a tempest in a teapot than the SPKG.txt t
On May 26, 9:13 am, William Stein wrote:
> On Wed, May 26, 2010 at 12:59 AM, David Kirkby
> wrote:
> > Looking at the Sage roadmap
>
> >http://trac.sagemath.org/sage_trac/roadmap
>
> > I see Sage 4.4.3 is "A tiny minor release on the way to 5.0" which is
> > due on 30th May.
>
> > Sage 5.0 is
On May 29, 11:00 am, "Dr. David Kirkby"
wrote:
> On May 29, 10:00 am, msafiri wrote:
>
>
>
> > Hi all,
> > I just compiled SAGE 4.4.2 on my MacbookPro running Ubuntu 10.04 (64
> > bit).
> > An installation of the graph package iGraph failed with the following
> > error:
> > ImportError: /usr/li
On May 29, 10:00 am, msafiri wrote:
> Hi all,
> I just compiled SAGE 4.4.2 on my MacbookPro running Ubuntu 10.04 (64
> bit).
> An installation of the graph package iGraph failed with the following
> error:
> ImportError: /usr/lib/libxml2.so.2: undefined symbol: gzopen64
> The reason is the libz
Hi all,
I just compiled SAGE 4.4.2 on my MacbookPro running Ubuntu 10.04 (64
bit).
An installation of the graph package iGraph failed with the following
error:
ImportError: /usr/lib/libxml2.so.2: undefined symbol: gzopen64
The reason is the libz library shipped with SAGE:
objdump -T $SAGE_ROOT/loca
On May 28, 2010, at 9:09 PM, Kwankyu Lee wrote:
Hi
While I am working on a small patch to a file in sage/gsl/ for the
ticket
http://trac.sagemath.org/sage_trac/ticket/9080
I am wondering why the gsl directory occupy the top-level place in the
Sage library. I suppose that the top-level directo
24 matches
Mail list logo
