Hi folks,
This subject has been raised before, but I want to revive it in case
anyone wants update on the issue.
Ticket #9850 [1] has three patches that aims to make the visual style
of the Sage standard documentation consistent with the theme used by
the Sage website. So far, the patches have re
On 3 Nov., 06:29, Bill Hart wrote:
> [...]
> Firstly, thank you to all the people who took the time to work on
> putting the new MPIR and Pari into Sage.
>
> (By the way, I don't understand why MPIR has been updated to 2.1.2 and
> not 2.1.3 which fixes a serious bug in the mpf functions. Nor do I
That sounds amazing. Assuming enough people submitted often enough, it
would be the best screensaver ever. If there were enough users for it
to be real-time it would be even cooler.
On Nov 2, 5:43 pm, Jason Grout wrote:
> On 11/2/10 7:22 PM, William Stein wrote:
>
>
>
>
>
>
>
>
>
> > On Tue, Nov
Yes, they are very cool to look at. My favourite is Rule 90.
On Nov 2, 5:22 pm, William Stein wrote:
> On Tue, Nov 2, 2010 at 5:15 PM, Hypercube wrote:
> > Some examples of CA usage:
>
> > -cryptography,http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=338094
> > -pseudo-random number
> >
Hi all,
I've been down with the flu for a few days and so amusing myself in
ways that don't make my head hurt too much. So, for fun, I just read
through the *very* long trac ticket for getting the new Pari into
Sage.
Firstly, thank you to all the people who took the time to work on
putting the ne
On 3 Nov., 05:35, leif wrote:
> On 2 Nov., 21:55, François Bissey wrote:
>
>
>
> > > This is a topic which I already touched in the "Merging tickets into
> > > sagenb" thread, but I believe the discussion was not finished.
>
> > > Currently, every new Sage version has a new version of the followi
On Tue, Nov 2, 2010 at 5:04 AM, David Kirkby wrote:
> If Sage were a commercial software product, a set of priorities would
> be set, and people told to work on those things that are most
> important. If people did not agree to work on them, they would
> probably lose their job.
>
> Clearly in an
On 2 Nov., 21:55, François Bissey wrote:
> > This is a topic which I already touched in the "Merging tickets into
> > sagenb" thread, but I believe the discussion was not finished.
>
> > Currently, every new Sage version has a new version of the following
> > spkgs: sage, sage_scripts, extcode, ex
Refereeing #9967 has turned into implementing some of its key features,
and I need to know more about how the Sage library is built by
SAGE_ROOT/devel/sage/setup.py.
I know that it creates a symlink from
SAGE_ROOT/local/lib/python/site-packages to a build directory. What I
eventually want is for t
Hi,
I'd be happy to help configure a pair of images. I have the most experience
with Ubuntu and CentOS (though it's been a couple years with CentOS),
wouldn't have a problem getting any of them up and running.
Cheers,
Geoff Ehrman
Grad Student, Dept. of Mathematics
University of New Hampshire
htt
Hi,
I have a new faster laptop with a lot more RAM (8GB, woot), so it's
suddenly become much easier for me to install Linux into VirtualBox's
in my spare time in the background. So I'm going to be adding
VirtualBox images to boxen for the following OS's:
CentOS-5.5-i386
CentOS-5.5-x86_64
Fedora
On Tue, Nov 2, 2010 at 1:03 AM, Johan S. R. Nielsen
wrote:
> Very nice. Will this be put somewhere persistent where new Sage
> developers can be expected to find it? E.g. as a supplement to the
> Developer's Guide.
I encourage somebody to add it!
Here's the raw html, if that is helpful:
htt
On 11/2/10 7:22 PM, William Stein wrote:
On Tue, Nov 2, 2010 at 5:15 PM, Hypercube wrote:
Some examples of CA usage:
-cryptography, http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=338094
-pseudo-random number generators,
http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=31545
-m
On Tue, Nov 2, 2010 at 5:15 PM, Hypercube wrote:
> Some examples of CA usage:
>
> -cryptography, http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=338094
> -pseudo-random number generators,
> http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=31545
> -modelling of certain chemical reac
Some examples of CA usage:
-cryptography, http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=338094
-pseudo-random number generators,
http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=31545
-modelling of certain chemical reactions,
http://search.ieice.org/bin/summary.php?id=e85-a_9_20
On Nov 2, 4:07 am, David Kirkby wrote:
>
> It would be rather embarrising for Steven Wolfram if Sage could do the
> stuff in Mathematica 1000x faster.
Not really. In this regard he would show ease of programming and
neatness
of display, not speed.
>
> > Their importance in Mathematica per se
> This is a topic which I already touched in the "Merging tickets into
> sagenb" thread, but I believe the discussion was not finished.
>
> Currently, every new Sage version has a new version of the following
> spkgs: sage, sage_scripts, extcode, examples. However, it is likely
> that not all tho
On Tue, Nov 2, 2010 at 12:15 PM, koffie wrote:
> return new_Expression_from_GEx(self._parent,
> g_hold2_wrapper(g_power_construct, self._gobj, g_ex1_2, hold))
>
> Can someone help with this?
It returns a new Expression (sage.symbolic.expression.Expression)
object that corresponds to a GiNaC/Py
On 2 November 2010 17:35, Jeroen Demeyer wrote:
> On 2010-11-02 16:44, Willem Jan Palenstijn wrote:
>> At a guess I'd say /sagenb is causing this? At least a 'find | wc -l' there
>> took longer to complete than I cared to keep it running...
> 3667802
>
> real 25m9.316s
> user 0m10.780s
> sys
Hej All,
I was trying to do some work on:
http://trac.sagemath.org/sage_trac/ticket/9129
The problem seems to be in the .sqrt functiontion for symbolic ring
elements. The source code is:
return new_Expression_from_GEx(self._parent,
g_hold2_wrapper(g_power_construct, self._gobj, g_ex1_2, hold
There are definitely tools to do this sort of automated checking, but if
you're only concerned with inode usage then a simple shell script run as a
periodic cronjob is the most straightforward solution imho.
On Tue, Nov 2, 2010 at 1:20 PM, David Kirkby wrote:
> On 2 November 2010 15:52, Jeroen De
On 2010-11-02 16:44, Willem Jan Palenstijn wrote:
> At a guess I'd say /sagenb is causing this? At least a 'find | wc -l' there
> took longer to complete than I cared to keep it running...
3667802
real25m9.316s
user0m10.780s
sys 1m41.000s
That's 3.6 million files in /sagenb
--
To po
On 2 November 2010 15:52, Jeroen Demeyer wrote:
> On 2010-11-02 16:44, Willem Jan Palenstijn wrote:
>> At a guess I'd say /sagenb is causing this? At least a 'find | wc -l' there
>> took longer to complete than I cared to keep it running...
>
> Could this also explain the recent slowness of http:/
On 2010-11-02 16:44, Willem Jan Palenstijn wrote:
> At a guess I'd say /sagenb is causing this? At least a 'find | wc -l' there
> took longer to complete than I cared to keep it running...
Could this also explain the recent slowness of http://www.sagenb.org/ ?
--
To post to this group, send an e
On Tue, Nov 02, 2010 at 04:24:41PM +0100, Jeroen Demeyer wrote:
> On 2010-11-02 16:18, Willem Jan Palenstijn wrote:
> > Possible options I can think of:
> >
> > * the filesystem could be out of inodes rather than out of space. (Use 'df
> > -i')
>
> That's the issue, on boxen:
> $ df -i
> Filesys
On 2010-11-02 16:18, Willem Jan Palenstijn wrote:
> Possible options I can think of:
>
> * the filesystem could be out of inodes rather than out of space. (Use 'df
> -i')
That's the issue, on boxen:
$ df -i
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/sda1448102
On Tue, Nov 02, 2010 at 07:42:51AM -0700, William Stein wrote:
> On Tuesday, November 2, 2010, David Kirkby wrote:
> > On 2 November 2010 00:10, William Stein wrote:
> >> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer
> >> wrote:
> >>> Hi, I just got the following error on Trac:
> >>>
> >>> Oop
On Tuesday, November 2, 2010, David Kirkby wrote:
> On 2 November 2010 00:10, William Stein wrote:
>> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer
>> wrote:
>>> Hi, I just got the following error on Trac:
>>>
>>> Oops…
>>> Trac detected an internal error:
>>>
>>> OSError: [Errno 28] No space
On 2 November 2010 12:49, Jason Grout wrote:
> On 11/2/10 6:07 AM, David Kirkby wrote:
>>
>> If Sage is ever to become a viable alternative to Mathematica, then it
>> really needs the features of that program.
>
>
> I think early on, there was a distinction made between focusing on having
> parity
On 11/2/10 6:07 AM, David Kirkby wrote:
If Sage is ever to become a viable alternative to Mathematica, then it
really needs the features of that program.
I think early on, there was a distinction made between focusing on
having parity of features with other programs and having the features
u
If Sage were a commercial software product, a set of priorities would
be set, and people told to work on those things that are most
important. If people did not agree to work on them, they would
probably lose their job.
Clearly in an open-source project like Sage, any attempt to tell
people what t
This is a topic which I already touched in the "Merging tickets into
sagenb" thread, but I believe the discussion was not finished.
Currently, every new Sage version has a new version of the following
spkgs: sage, sage_scripts, extcode, examples. However, it is likely
that not all those spkgs cha
On 2 November 2010 02:17, rjf wrote:
> Cellular automata of the sort that Wolfram talks about can be
> implemented
> in languages other than Mathematica much more efficiently. Maybe
> 10,000
> times faster when I wrote some stuff in lisp. Not for doing anything
> useful,
> just a speed competiti
Hi folks,
The following are three documentation tickets needing review:
* #10143 Bring 2D plotting up to 100% doctest coverage (except
plot.py) http://trac.sagemath.org/sage_trac/ticket/10143
* #9655 Add an example plotting spherical harmonics to
spherical_plot3d's docstring
http://trac.sagemath
On 2 November 2010 00:10, William Stein wrote:
> On Mon, Nov 1, 2010 at 5:07 PM, Jeroen Demeyer wrote:
>> Hi, I just got the following error on Trac:
>>
>> Oops…
>> Trac detected an internal error:
>>
>> OSError: [Errno 28] No space left on device:
>> '/var/trac/sage_trac/attachments/ticket/7513'
Hi Johan,
On Tue, Nov 2, 2010 at 7:03 PM, Johan S. R. Nielsen
wrote:
> Very nice. Will this be put somewhere persistent where new Sage
> developers can be expected to find it? E.g. as a supplement to the
> Developer's Guide.
Excellent idea. If you open a ticket and upload a patch, I promise to r
Very nice. Will this be put somewhere persistent where new Sage
developers can be expected to find it? E.g. as a supplement to the
Developer's Guide.
I have one comment: In the current version, sage.misc.misc.deprecation
has some steep limitations. Trac #9919 (along with #9907) fixes it so
it can
37 matches
Mail list logo