On Dec 8, 2009, at 9:47 PM, Mike Hansen wrote:
> Hello,
>
> On Wed, Dec 9, 2009 at 12:44 PM, Nick Alexander
> wrote:
>> Implementing a particular symbolic function is not outlandishly
>> difficult, thanks to the tireless work of Burcin Erocal and Mike
>> Hansen. (Apologies to any contributers
Hello,
On Wed, Dec 9, 2009 at 12:44 PM, Nick Alexander wrote:
> Implementing a particular symbolic function is not outlandishly
> difficult, thanks to the tireless work of Burcin Erocal and Mike
> Hansen. (Apologies to any contributers I have forgotten.)
>
> You need to subclass sage.symbolic.fu
On 8-Dec-09, at 8:59 PM, Dan Drake wrote:
> On Tue, 08 Dec 2009 at 10:44PM -0300, Pablo De Napoli wrote:
>> I'm trying to do some computations with Bessel functions using Sage.
>> Unfortunately, they don't seem to behave like other functions. For
>> example:
>> to get the plot of the sine funct
On Tue, 08 Dec 2009 at 10:44PM -0300, Pablo De Napoli wrote:
> I'm trying to do some computations with Bessel functions using Sage.
> Unfortunately, they don't seem to behave like other functions. For example:
> to get the plot of the sine function over the interval (0,100)
>
> plot(sin(x),(x,0,1
Greetings!
I had the first successful print of something created in sage. It was
a sphere (radius = 3) and it revealed a small problem: physical size
is proportional to size in sage. The sphere printed with a radius of ~
1 cm. I intend to fix this.
We're about to print a much larger cylinder...
I have posted the relevant code here:
http://trac.sagemath.org/sage_trac/ticket/7634
--
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://group
Hi
I'm trying to do some computations with Bessel functions using Sage.
Unfortunately, they don't seem to behave like other functions. For example:
to get the plot of the sine function over the interval (0,100)
plot(sin(x),(x,0,100))
works. However,
plot(bessel_J(0,x),(x,0,100))
does not. Giv
Very inspiring, thanks for sharing.
Francesco.
--
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.google.com/group/sage-devel
URL: h
>>> In the end : What is going on with the C graphs in Sage, can we
>>> expect
>>> them to eb available soon ?
>
> You can use them right now. They're just not as feature full.
Actually, that's no longer true. As of the closing of #6085, they are
just as full of features as NX-based Sage graphs. T
On Tue, Dec 1, 2009 at 8:56 AM, Nathann Cohen wrote:
> Hmmm... If we can make Sage's C graphs as fast as NetworkX's , I
> assure you it will be very hard for them to compete with LP on our
> side and so many features around in Sage... As most of NetworkX's
> functions are not very hard to rewrite
John H Palmieri wrote:
> On Dec 8, 3:12 pm, Minh Nguyen wrote:
>> Hi David,
>>
>> On Wed, Dec 9, 2009 at 10:08 AM, Dr. David Kirkby
>>
>> wrote:
>>
>>
>>
>>> Yes, I'll do that. I wont promise when, as I am a bit busy now. Many of
>>> these
>>> things can be found in documents on the web, but it
Hi,
If you look at this list of tickets needing review here:
http://trac.sagemath.org/sage_trac/report/30
you'll see that there are now 84 (down from 110 yesterday). The
notebook component had a bunch needing review, since I had been lax,
but now it has none that *can be* reviewed right no
Er, never mind, I had looked into the makefile and gotten the
impression I needed to set DESTDIR to some suitable value. If I don't
do that, the build seems to proceed without trouble. (I get the
impression I am not supposed to install this thing at all, but just
run it from the source directory?)
On Dec 8, 3:12 pm, Minh Nguyen wrote:
> Hi David,
>
> On Wed, Dec 9, 2009 at 10:08 AM, Dr. David Kirkby
>
> wrote:
>
>
>
> > Yes, I'll do that. I wont promise when, as I am a bit busy now. Many of
> > these
> > things can be found in documents on the web, but it would no doubt help to
> > have
Trying to build sage 4.2.1 on Mac OS X 10.5.8 ended in this error message:
( cd examples ; make DESTDIR=/local/pkg/sage_4.2.1 install )
/bin/sh ../support/mkdirs
/local/pkg/sage_4.2.1/local/src/sage/sage-4.2.1/local/share/readline
mkdir /local/pkg/sage_4.2.1/local/src/sage/sage-4.2.1/local/share
Hi David,
On Wed, Dec 9, 2009 at 10:08 AM, Dr. David Kirkby
wrote:
> Yes, I'll do that. I wont promise when, as I am a bit busy now. Many of these
> things can be found in documents on the web, but it would no doubt help to
> have
> them in the developer guide, particularly those related to S
kcrisman wrote:
> Dear Dave,
>
> I think you have a lot of really good ideas about portability.
> However, my fear is that there are so many scripts out there, and
> people without your knowledge won't have a place to go.
>
> Would you be willing to write something for the developer guide that
>
Hi,
This patch: http://trac.sagemath.org/sage_trac/ticket/7514 is pretty
important and really needs review.
It's a much needed rewrite and refactoring of load/attach, it will
bitrot, and it was a full days work. And I can't referee it since I
wrote it. It makes load/attach vastly more systema
Here's another fairly easy one, assuming it hasn't bitrotted - it's
long, but it's all the same kind of thing.
http://trac.sagemath.org/sage_trac/ticket/6522
- kcrisman
On Dec 8, 5:45 am, "Dr. David Kirkby" wrote:
> William Stein wrote:
> > Hi,
>
> > There are now 110 tickets that need review.
Dear Dave,
I think you have a lot of really good ideas about portability.
However, my fear is that there are so many scripts out there, and
people without your knowledge won't have a place to go.
Would you be willing to write something for the developer guide that
has ALL your recommendations on
Many scripts have in them something like
if [ $SAGE64 = "yes" -a $UNAME = "Darwin" ] ; then
some code
fi
Where the '-a' means 'AND'.
The use of the '-a' option is deprecated by both by the 2004
http://www.opengroup.org/onlinepubs/009695399/utilities/test.html
and 2008
http://www.opengroup.or
Oh, no, not this one again! I overhauled the elementary divisors code
a while ago and I thought I had sorted out this one. Personally I feel
that M.elementary_divisors() should always return a list of size min
(M.nrows(), M.ncols()), which should also be the size of the square
matrix output by M.sm
Hi!
I am currently overhauling the code for Infinite Polynomial Rings,
trying to introduce construction functors for it.
At this occasion, I found that the composition of ConstructionFunctors
is broken.
Namely, for construction functors F1 and F2, there are two conventions
of what F1*F2 should d
Hello, from the "report a problem" link I got the complaint that
elementary_divisors() is wrong. It turned out that it behaves
differently with respect to the matrix's ring. I guess it's one of
those left/right issues.
Examples:
sage: M = random_matrix(ZZ, 5,3)
sage: M.elementary_divisors()
[1, 1
Very interesting read!
On Dec 7, 10:30 pm, William Stein wrote:
> Hi,
>
> Paul Zimmermann asked me for a "brief history of Sage" to help inform
> a talk he is going to give about Sage. I sat down to write such a
> thing and instead ended up writing a long 16 page account of my
> involvement in m
William Stein wrote:
> Hi,
>
> There are now 110 tickets that need review. See
>
> http://trac.sagemath.org/sage_trac/report/30
>
> for a nice list sorted by component. If you have some time and know
> how to referee tickets, please referee one.
>
> -- William
>
The following ticket
26 matches
Mail list logo
