[sage-devel] Re: Expected value of probability space

On Sun, Nov 30, 2008 at 9:39 PM, Paul Butler <[EMAIL PROTECTED]> wrote: > I've been experimenting with probability and found that in Sage, a > probability space is also a random variable by inheritance. This may be > useful. Without it, creating a random variable requires two classes: a > probabil

[sage-devel] Re: Expected value of probability space

[Another response in this thread from David Kohel (who maybe should be posting on list)] Hi William and Paul, Actually, I correct myself -- the average should be over the values of the function, weighted by the probabilities. The domain of the function (the keys) can be in any set (e.g. "A","B"

[sage-devel] Christmas once again ...

>From http://www.walkingrandomly.com/?p=395 featuring some Sage code for a card, and a mathematica snowflake, ... """ You[r] task is to design a Christmas message with a mathematical theme using any mathematical system or programming language of your choice. Your design must be generated algorith

[sage-devel] Re: Christmas once again ...

That p-adic one is actually my design! Here is another one: http://www.usna.edu/Users/math/wdj/greeting.jpg It's a Barnsley fractal I programmed in C long ago, though I've lost the code. I'll try to recreate it in Sage. On Mon, Dec 1, 2008 at 4:56 AM, Harald Schilly <[EMAIL PROTECTED]> wrote: >

[sage-devel] Request for additions to the Sage 3.2.1 Release Tour

Hello folks, 3.2.1 is about done (rc1 should be announced officially in about 2 hours once it passes my build testing and a full test run, but it is in the usual place if you want to get going with it now). My main request is for people to add items to the Sage Release tour at http://wiki.sagemat

[sage-devel] Re: Christmas once again ...

On Dec 1, 2:47 am, "David Joyner" <[EMAIL PROTECTED]> wrote: > That p-adic one is actually my design! Here is another > one:http://www.usna.edu/Users/math/wdj/greeting.jpg > It's a Barnsley fractal I programmed in C long ago, though I've lost the code. > I'll try to recreate it in Sage. > > On

[sage-devel] Re: Request for additions to the Sage 3.2.1 Release Tour

Generally, I'd be happy to help with this sort of thing. This is the end of the semester here now though and not the best time (lots of grading, tutoring, etc). I can try to do what I can though. On Mon, Dec 1, 2008 at 6:20 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > 3.2.1 is abo

[sage-devel] Sage 3.2.1.rc1 released

Hello folks, it took a couple hours longer than planned, but here goes 3.2.1.rc1. The changes merged went a little deeper than planned, i.e. the two biggest changes are massive improvements to the Magma interface by William and the overhaul of module_list.py by Craig. The changes by Craig will fo

[sage-devel] Re: name space pollution

Are there some general guidelines on how to use the namespaces in sage. Like: which function's should be accesible from which namespace (global v.s. local and maybe some hierachical structure in the local namespace). I think some guidelines on this would improve the userfriendliness of sage a big

[sage-devel] Re: Sage 3.2.1.rc1 released

All tests passed on an upgrade from rc0, on an intel mac (10.5). Three cheers for the more flexible upgrade option! -M. Hampton On Dec 2, 7:02 am, mabshoff <[EMAIL PROTECTED]> wrote: > Hello folks, > > it took a couple hours longer than planned, but here goes 3.2.1.rc1. > The changes merged wen

[sage-devel] Re: Sage 3.2.1.rc1 released

On Dec 1, 6:53 am, mhampton <[EMAIL PROTECTED]> wrote: > All tests passed on an upgrade from rc0, on an intel mac (10.5). > > Three cheers for the more flexible upgrade option! > > -M. Hampton Yeah, for me it is the killer feature of 3.2.1 - no disrespect to all the other great features :) But

[sage-devel] Re: Sage 3.2.1.rc1 released

mabshoff wrote: > Hello folks, > > it took a couple hours longer than planned, but here goes 3.2.1.rc1. > The changes merged went a little deeper than planned, i.e. the two > biggest changes are massive improvements to the Magma interface by > William and the overhaul of module_list.py by Craig.

[sage-devel] Re: recommended method to extend sage classes

David Joyner wrote: > By "extend" a Sage class it seems you mean "add a method to" a Sage class. > You want to know how to add a method to the class > matrix_complex_double_dense.pyx > at > http://www.sagemath.org/hg/sage-main/file/8b1d19463fc4/sage/matrix/matrix_complex_double_dense.pyx > ? > >

[sage-devel] Re: Sage 3.2.1.rc1 released

On Dec 1, 7:27 am, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > Upgrade from rc0 on Fedora 9 has the known issues in > sage/rings/polynomial/multi_polynomial_ideal.py > > Jaap Hi Jaap, can you repost the output? I made another one of those GBasis over ZZ computations optional f

[sage-devel] Re: Expected value of probability space

Hi David, Thanks for explaining that, I see how that causes problems when S is not a set of numbers. Even so, would it make sense for the random variable ps to be the identity function X(x) = x on the probability space ps? Currently the random variable ps is the function X(x) = P(x). Is this a use

[sage-devel] Re: recommended method to extend sage classes

Simon Beaumont wrote: > What is the recommended way to extend sage classes? - I want to add > some functionality to the complex matrix class - specifically tests > for: is_symmetric, is_hermitian, is_unitary etc... you get the idea. As noted in other replies, you could add these methods to either

[sage-devel] Re: Sage 3.2.1.rc1 released

mabshoff wrote: > > > On Dec 1, 7:27 am, Jaap Spies <[EMAIL PROTECTED]> wrote: >> mabshoff wrote: > > > >> Upgrade from rc0 on Fedora 9 has the known issues in >> sage/rings/polynomial/multi_polynomial_ideal.py >> >> Jaap > > Hi Jaap, > > can you repost the output? I made another one of tho

[sage-devel] Re: plot3d problem - stalled in maxima

David Joyner wrote: > Since > > sage: x,y = var("x y") > sage: plot3d(x^2-y^2, (x,-1,1),(y,-1,1)) > > works fine, why not just use variables > > sage: f = x^2-y^2 > sage: f.variables() > (x, y) > > to find the missing variables in plot3d(x^2-y^2, (-1,1),(-1,1)) > and then replace the arguments

[sage-devel] Re: Sage 3.2.1.rc1 released

This is also the unique doctest failure under RHEL5 on my 64-bit Opteron box (upgraded from rc0). Kiran On Dec 1, 10:35 am, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > > On Dec 1, 7:27 am, Jaap Spies <[EMAIL PROTECTED]> wrote: > >> mabshoff wrote: > > > > > >> Upgrade from rc0 o

[sage-devel] Re: Sage 3.2.1.rc1 released

On Dec 1, 7:40 am, Kiran Kedlaya <[EMAIL PROTECTED]> wrote: > This is also the unique doctest failure under RHEL5 on my 64-bit > Opteron box (upgraded from rc0). > > Kiran Jaap, Kiran, this is basically caused by #4593. We can also make that doctest optional for now since the failure is also d

[sage-devel] Re: plot3d problem - stalled in maxima

Jason Grout wrote: > David Joyner wrote: >> Since >> >> sage: x,y = var("x y") >> sage: plot3d(x^2-y^2, (x,-1,1),(y,-1,1)) >> >> works fine, why not just use variables >> >> sage: f = x^2-y^2 >> sage: f.variables() >> (x, y) >> >> to find the missing variables in plot3d(x^2-y^2, (-1,1),(-1,1)) >>

[sage-devel] Re: [sympy] patch review

On Mon, Dec 1, 2008 at 8:50 PM, Vinzent Steinberg <[EMAIL PROTECTED]> wrote: > > Sage has problems with reviewing patches: > > http://sagemath.blogspot.com/2008/11/sage-patch-review.html > > I think our current patch review system could be improved too. So I > suggest to take part in the discussio

[sage-devel] Re: Expected value of probability space

Hi Paul, > Thanks for explaining that, I see how that causes problems when S is not a > set of numbers. Even so, would it make sense for the random variable ps to > be the identity function X(x) = x on the probability space ps? Currently the > random variable ps is the function X(x) = P(x). Is th

[sage-devel] Re: Sage 3.2.1.rc1 released

mabshoff wrote: > Hello folks, > > it took a couple hours longer than planned, but here goes 3.2.1.rc1. > The changes merged went a little deeper than planned, i.e. the two > biggest changes are massive improvements to the Magma interface by > William and the overhaul of module_list.py by Craig.

[sage-devel] Re: Sage 3.2.1.rc1 released

On Dec 1, 2008, at 05:02 , mabshoff wrote: > > Hello folks, > > it took a couple hours longer than planned, but here goes 3.2.1.rc1. > The changes merged went a little deeper than planned, i.e. the two > biggest changes are massive improvements to the Magma interface by > William and the overhau

[sage-devel] Re: Sage 3.2.1.rc1 released

Justin C. Walker wrote: > > On Dec 1, 2008, at 05:02 , mabshoff wrote: > >> Hello folks, >> >> it took a couple hours longer than planned, but here goes 3.2.1.rc1. >> The changes merged went a little deeper than planned, i.e. the two >> biggest changes are massive improvements to the Magma inter

[sage-devel] Re: Expected value of probability space

Hi David, When I was referring to the "probability space ps" and the "random variable ps", I was referring to the fact that ps is by inheritance a probability space and a random variable (is_DiscreteProbabilitySpace(ps) == is_DiscreteRandomVariable(ps) == True). I do see that the values are neces

[sage-devel] Re: Sage 3.2.1.rc1 released

On Dec 1, 2008, at 16:59 , Jaap Spies wrote: > > Justin C. Walker wrote: >> >> On Dec 1, 2008, at 05:02 , mabshoff wrote: >> >>> Hello folks, >>> >>> it took a couple hours longer than planned, but here goes 3.2.1.rc1. >>> The changes merged went a little deeper than planned, i.e. the two >>> bi

[sage-devel] libm4ri

I just noticed for m4ri the package is called libm4ri-*.spkg. Any reason this isn't m4ri-*.spkg? - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For

[sage-devel] Re: libm4ri

On Dec 1, 8:40 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > I just noticed for m4ri the package is called libm4ri-*.spkg. Any   > reason this isn't m4ri-*.spkg? That is the name malb gave it initially and it just stuck. The same applies for libfplll.spkg, too. > - Robert Cheers, Michael

[sage-devel] Sage 3.2.2.alpha0 release cycle opened

Hello folks, Sage 3.2.1 is out - at least unofficially - so I have started building my Sage 3.2.2.alpha0 merge tree. It will be a couple hours until I start merging since I will catch some sleep in the meantime, so if you have patches that are supposed to get in please make sure they apply cleanl

[sage-devel] Re: libm4ri

On Dec 1, 2008, at 8:42 PM, mabshoff wrote: > On Dec 1, 8:40 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> I just noticed for m4ri the package is called libm4ri-*.spkg. Any >> reason this isn't m4ri-*.spkg? > > That is the name malb gave it initially and it just stuck. The same > applies fo

[sage-devel] Re: libm4ri

On Dec 1, 8:51 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Dec 1, 2008, at 8:42 PM, mabshoff wrote: > > > On Dec 1, 8:40 pm, Robert Bradshaw <[EMAIL PROTECTED]> > > wrote: > >> I just noticed for m4ri the package is called libm4ri-*.spkg. Any > >> reason this isn't m4ri-*.spkg? > > > Tha

[sage-devel] Re: libm4ri

On Dec 1, 2008, at 8:54 PM, mabshoff wrote: > On Dec 1, 8:51 pm, Robert Bradshaw <[EMAIL PROTECTED]> > wrote: >> On Dec 1, 2008, at 8:42 PM, mabshoff wrote: >> >>> On Dec 1, 8:40 pm, Robert Bradshaw <[EMAIL PROTECTED]> >>> wrote: I just noticed for m4ri the package is called libm4ri-*.spkg.

[sage-devel] Re: libm4ri

On Dec 1, 9:11 pm, Robert Bradshaw <[EMAIL PROTECTED]> wrote: > On Dec 1, 2008, at 8:54 PM, mabshoff wrote: > > > > > On Dec 1, 8:51 pm, Robert Bradshaw <[EMAIL PROTECTED]> > > wrote: > >> On Dec 1, 2008, at 8:42 PM, mabshoff wrote: > > >>> On Dec 1, 8:40 pm, Robert Bradshaw <[EMAIL PROTECTED]>

[sage-devel] Re: Sage 3.2.2.alpha0 release cycle opened

On Mon, Dec 1, 2008 at 8:46 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hello folks, > > Sage 3.2.1 is out - at least unofficially - so I have started building > my Sage 3.2.2.alpha0 merge tree. It will be a couple hours until I > start merging since I will catch some sleep in the meantime, so if

[sage-devel] questions about optional packages

Some random questions about the optional packages available for Sage: Which is more up-to-date: the list obtained by 'sage --optional', or the list on the wiki ? (I'm guessing the former.) Is the list obtained by 'sage --optional'

[sage-devel] Re: questions about optional packages

On Dec 1, 9:36 pm, John H Palmieri <[EMAIL PROTECTED]> wrote: Hi John, > Some random questions about the optional packages available for Sage: > > Which is more up-to-date: the list obtained by 'sage --optional', or > the list on the wiki optional_packages_available_

[sage-devel] credit

Hi, This is a small thing, but I was a bit discouraged when I found that my tiny contribution of reporting ticket #4641 was ill credited to a wrong person in the release note of Sage 3.2.1 rc0. My name is Kwankyu Lee. Is this still correctable? --~--~-~--~~~---~--~--

[sage-devel] Re: credit

On Dec 1, 9:59 pm, Kwankyu <[EMAIL PROTECTED]> wrote: > Hi, Hi, > This is a small thing,  but I was a bit discouraged when I found that > my tiny contribution of reporting ticket #4641 was ill credited to a > wrong person in the release note of Sage 3.2.1 rc0. My name is Kwankyu > Lee. Is this

[sage-devel] Re: credit

On Tue, Dec 2, 2008 at 5:06 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > > On Dec 1, 9:59 pm, Kwankyu <[EMAIL PROTECTED]> wrote: >> Hi, > > Hi, > >> This is a small thing, but I was a bit discouraged when I found that >> my tiny contribution of reporting ticket #4641 was ill credited to a >> wro

[sage-devel] Re: credit

Thank you for your kindness! --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs:

[sage-devel] Re: credit

On Dec 1, 10:15 pm, "Minh Nguyen" <[EMAIL PROTECTED]> wrote: > On Tue, Dec 2, 2008 at 5:06 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > > On Dec 1, 9:59 pm, Kwankyu <[EMAIL PROTECTED]> wrote: > >> Hi, > > > Hi, > > >> This is a small thing,  but I was a bit discouraged when I found that > >> my t