Sorry to be so late (10 months late!) in responding to this; I'm
getting back to Sage development and I'm reading through my sage-devel
archives.
Dirk, I don't know if you still care about this... I'm the original
author of the code (and documentation) in question. I basically made
up the behavio
> It does raise interest. But then there are questions of encouraging
> people to get involved in maintaining the interface between giac and
> Sage. Someone needs to step up and maintain that interface for at
> least 3 years.
>
I don't think it would be a problem, because I could probably maintain
On 07/ 8/10 10:32 PM, Sergey Bochkanov wrote:
Hello!
I've talked about making Sageable interface to ALGLIB two months ago.
It took twice as much time as I previously thought, but now it is
ready to go public.
You can download first beta of ALGLIB double precision interface (as
.spkg o
Hi,
On Fri, Jul 9, 2010 at 10:32 PM, parisse
wrote:
> I'm curious to know if this will raise interest in integrating giac in
> sage one day, now that giac has about the same timings than magma for
> GCD...
It does raise interest. But then there are questions of encouraging
people to get involved
Hello, Jason.
You wrote 9 июля 2010 г., 15:34:07:
> On OSX 10.6.4, I get an error:
> ...
> ...
> This looks like it might be useful, but I don't know:
> http://lists.apple.com/archives/unix-porting/2003/Oct/msg00032.html
I think that it is easy to fix, thanks for the link you gave me. The
only
On 7/9/10 4:47 AM, William Stein wrote:
Hi,
Paul Zimmermann orchestrated the writing of a new -- and amazingly
organized and systematic (!) -- book about Sage. It is now publicly
available:
http://www.loria.fr/~zimmerma/sagebook.html
And it is supposed to be Creative Commons licensed.
I think that the SAGE _factor_cunningham stuff only gives big speedups
for much smaller b in b^n+/-1 (the documentation says that this is b
<=12), and that MAGMA ships with a really big table of factors etc to
help it to factor Cunningham-type numbers.. This is helpful for a lot
of the combinatoric
On Fri, Jul 9, 2010 at 10:56 AM, Pablo Winant wrote:
> According to cpuinfo I have an Intel(R) Core(TM)2 Duo CPU L9400 @
> 1.86GHz
Hmm... that should be fine. If you have the old version around, could
you do the following:
1) Start Sage with "sage -gdb"
2) Run the commands that caused
According to cpuinfo I have an Intel(R) Core(TM)2 Duo CPU L9400
@ 1.86GHz
Here is the rest of the output :
stepping: 6
cpu MHz: 800.000
cache size: 6144 KB
physical id: 0
siblings: 2
core id: 1
cpu cores: 2
apicid: 1
initial apicid: 1
fp
On Fri, Jul 9, 2010 at 1:42 AM, Pablo W. wrote:
> Just to mention that the bug disappear if I build sage manually using
> 'make -j2'. Could there be something wrong with the official build ?
What type of processor are you using? My guess is that the binary was
built on a newer processor than the
Dear Sage-Combinat devs,
- Forwarded message from William Stein -
Paul Zimmermann orchestrated the writing of a new -- and amazingly
organized and systematic (!) -- book about Sage. It is now publicly
available:
http://www.loria.fr/~zimmerma/sagebook.html
And it is supposed
Hi!
On Jul 9, 12:39 pm, Lloyd Kilford wrote:
> ...
> There is a significant difference here.
Not good.
Unfortunately, using _factor_cunningham would not help in this case.
Even after installing the optional cunningham_tables-1.0.spkg, I get
sage: %time c._factor_cunningham()
CPU times: user 2
I have updated the benchmarks page of giac, with comparison with magma
and trip there:
http://www-fourier.ujf-grenoble.fr/~parisse/giac/benchmarks/benchmarks.html
I'm curious to know if this will raise interest in integrating giac in
sage one day, now that giac has about the same timings than magma
Hi,
Paul Zimmermann orchestrated the writing of a new -- and amazingly
organized and systematic (!) -- book about Sage. It is now publicly
available:
http://www.loria.fr/~zimmerma/sagebook.html
And it is supposed to be Creative Commons licensed.
-- william
-- Forwarded message --
So in Bart de Smit's talk at Sage Days 23 he gave in an example the
integer 103^100-1 which had to be factored in order to proceed. There
is a very interesting difference between the performance of Sage 4.4
and Magma 2.15-4 here:
sage: time factor(103^100-1)
CPU times: user 270.59 s, sys: 0.64 s,
On 7/8/10 2:32 PM, Sergey Bochkanov wrote:
Hello!
I've talked about making Sageable interface to ALGLIB two months ago.
It took twice as much time as I previously thought, but now it is
ready to go public.
You can download first beta of ALGLIB double precision interface (as
.spkg or .
Just to mention that the bug disappear if I build sage manually using
'make -j2'. Could there be something wrong with the official build ?
On 9 juil, 00:35, "Pablo W." wrote:
> Hi folks,
>
> The following line seems to reset the sage interpreter (with n bigger
> than 98), which is very annoying a
17 matches
Mail list logo
