[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
probability space and a random variable on that probability space.
Unfortunately, the random variable doesn't work like I expected. For
example:
sage: ps = DiscreteProbabilitySpace([1,2,3],{1:1/3,2:1/3,3:1/3})
sage: ps.expectation()
0.333
(I expected 2.00)
I've prepared a patch that gives me the value I'd expect, but I'd like to
make sure this is the proper behavior.
-- Paul
Response from David Kohel:
Dear William, Paul,
Indeed, the function definition should be:
def expectation(self):
r
The expectation of the discrete random variable, namely
$\sum_{x \in S} p(x) X[x]$,
where $X$ = self and $S$ is the probability space of $X$.
E = 0
Omega = self.probability_space()
for x in self._function.keys():
E += Omega(x) * x
return E
rather than:
def expectation(self):
r
The expectation of the discrete random variable, namely
$\sum_{x \in S} p(x) X[x]$,
where $X$ = self and $S$ is the probability space of $X$.
E = 0
Omega = self.probability_space()
for x in self._function.keys():
E += Omega(x) * self(x)
return E
Cheers,
David
--~--~-~--~~~---~--~~
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: http://www.sagemath.org
-~--~~~~--~~--~--~---
[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: 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 algorithmically (so you can't design it in Photoshop and import it into Mathematica for example) and it must include source code. Ideally, you should include a quick explanation of the mathematics you featured in your design. greetings Harald --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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.sagemath.org/sage-3.2.1 We have not been doing the best possible job there and actually need to do some fixing for earlier releases where only some rudimentary documentation exists. The Sage Release tour is meant for people not so tightly connected to the development group to gather what are the major new features in Sage. It can also be used very well to showcase one's contribution to Sage [hint hint :)]. I think that for example malb has done a spectacular job documenting some of his contributions to Sage by providing a little blurb and then some code examples that demonstrate the new functionality for many of the features he added/ was part of the team implementing them. In the long term I hope that we can take the data from the Sage Release tour wiki pages and integrate it into the new ReST documentation by extracting the info in some automated fashion from the wiki so that even offline we will have a very nice overview of what has been happening in Sage development. If anybody wants to help pitch in here please let me know so I can direct you to various construction sites in the Sage documentation :) Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 Mon, Dec 1, 2008 at 4:56 AM, Harald Schilly [EMAIL PROTECTED] wrote: Fromhttp://www.walkingrandomly.com/?p=395featuring 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 algorithmically (so you can't design it in Photoshop and import it into Mathematica for example) and it must include source code. Ideally, you should include a quick explanation of the mathematics you featured in your design. Very nice. We should definitely encourage people to participate and get them to donate their Sage code to expand the gallery we have for Sage :) greetings Harald Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 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.sagemath.org/sage-3.2.1 We have not been doing the best possible job there and actually need to do some fixing for earlier releases where only some rudimentary documentation exists. The Sage Release tour is meant for people not so tightly connected to the development group to gather what are the major new features in Sage. It can also be used very well to showcase one's contribution to Sage [hint hint :)]. I think that for example malb has done a spectacular job documenting some of his contributions to Sage by providing a little blurb and then some code examples that demonstrate the new functionality for many of the features he added/ was part of the team implementing them. In the long term I hope that we can take the data from the Sage Release tour wiki pages and integrate it into the new ReST documentation by extracting the info in some automated fashion from the wiki so that even offline we will have a very nice overview of what has been happening in Sage development. If anybody wants to help pitch in here please let me know so I can direct you to various construction sites in the Sage documentation :) Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ What is left for 3.2.1.final is to potentially fix the exponentiation leak [which is likely 99.9% coercion related :)], but since 3.2.2 will be also a rather short release cycle we will release without such a fix. Please build, test and report any issues. The official 3.2.1 sources should be out in 24 hours unless something goes very wrong and be followed in about another day or two by binaries. Cheers, Michael Merged in Sage 3.2.1.rc1: #3122: Michael Abshoff: after make install, sage tries to write in / usr/local [Reviewed by William Stein] #4254: Martin Albrecht: mq.SR improvements for convenience [Reviewed by William Stein] #4261: Willem Jan Palenstijn: sympow Configure fails to handle aliases [Reviewed by William Stein, Mark Watkins, Michael Abshoff] #4308: Philippe Theveny: make mpc an optional spkg [Reviewed by William Stein, Michael Abshoff] #4317: William Stein: Fix easy-install.pth after moving Sage [Reviewed by Michael Abshoff, Craig Citro] #4321: Alexander Dreyer, Michael Abshoff: wrong Unix permissions in some PolyBoRi files #4352: Marshall Hampton: add support for weight vectors to gran/ groebner_fan [Reviewed by William Stein] #4402: William Stein: Sage 3.1.4: magma related optional doctest failure in tut.tex [Reviewed by Michael Abshoff] #4412: John Cremona: extend the local information function for elliptic curves over number fields [Reviewed by William Stein, Minh Nguyen] #4576: Marshall Hampton: biopython optional package upgrade to 1.49beta [Reviewed by William Stein] #4582: Guillaume Moroz: use Singular's capabilities for computing over fraction fields [Reviewed by Martin Albrecht] #4619: Michael Abshoff: Sage 3.2.1.a1: Update HISTORY.txt with the 3.1.3, 3.1.4 and 3.2 release notes [Reviewed by William Stein] #4654: John Palmieri: for 'sage -testall': put sage version in test log [Reviewed by Michael Abshoff] #4655: William Stein: doctest failure in plot.py with 3.2.1.rc0 on 64- bit SuSe linux [Reviewed by Michael Abshoff] #4657: Michael Abshoff: OSX: gnuplot doesn't start due to dreaded libpng conflict [Reviewed by William Stein] #4658: William Stein: magma -- get rid of redundant caching: just have _magma_init_ [Reviewed by Michael Abshoff] #4659: John Palmieri: remove an extra 'cdef class Integer' line from integer.pyx [Reviewed by Robert Bradshaw] #4660: William Stein: mark inline fortran and inline cython examples optional [Reviewed by Michael Abshoff] #4661: Craig Citro: clean up module_list.py [Reviewed by Michael Abshoff] #4664: Michael Abshoff: Sage 3.2.1.rc1: Fix documentation build issues [Reviewed by Craig Citro] #4668: Michael Abshoff: libSingular's header have too tight permissions [Reviewed by Craig Citro] --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 deal in the long run. I personally find the polution of the global namespace and some local namespace's to get already a bit annoying and making the [tab] funtionality a whole less usefull then it could be for when quickly trying to find some funtion. Here are just some random ideas on what might be in these guidlines (I don't claim them all to be good so be happy to comment at them, or propose your own, or just shoot me ;)) 1 A packege should, without a good reason (like almost every mathematician need the package almost all of the time), not use more then X names in the global namespace. (You could ofcourse do import Foo to get more things in the global namespace when using a certain package very heavely). 2 All functionallity related to a package should always be accessible by Packagename.[tab] or Packagename.Subpackage.[tab] or Packagename.Subpackage.SubSubPackage.[tab] e.t.c. 3 Names of Subpackages should start with a capitalized letter, while names of atributes and functions should not (or any other convenient way to make an easy distinction between packages and functions) 4 Maybe some guidelines to encourage nice hierachical namespace design. 5 Some sort of template hierachy to make the user interface (espesially the [tab]) in sage feel the same through all packages. 5.1 For example categorical constructions like (fibred) sum, (firbred) product, etc occur in all area's of mathematics, and could be grouped in PackageName.CategoricalStuff (sorry for the lame name). 5.2 Another one is to make all object initialisation commands available through something like PackageName.Init. using the current graph implementation this addition would make the following two statements equivalent sage: graphs.CompleteGraph(6) sage: Graph.Init.CompleteGraph(6) Hope you don't mind the long tekst. Maarten On Nov 30, 11:11 pm, mabshoff [EMAIL PROTECTED] wrote: SNIP I really like sage: finance.[tab] I don't like explicitly forcing people to import stuff before they can use it at all. Thus I much prefer $ sage sage: finance.[tab] and I don't like $ sage ... sage: import sage.finance as finance sage: finace.[tab] I do like various domains with lots of functions to have their functionality gathered together under a namespace. That said, I'm not for some massive reorganization of the current global namespace, since that wold break a huge amount of existing code -- both in Sage and out (e.g., the examples at wiki.sagemath.org/interact). And it's not the end of the world that len(globals()) is large. It's only a problem to me when there are specific reasons it is a problem. -- William Ok, that is pretty much what I wanted to express, i.e. having most things of a given subsystem gathered under $SUBSYSTEM.[tab]. I did not mean that one would have to import things, so my use of global namespace was not in the pythonic way. Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 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 force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgradehttp://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sa... What is left for 3.2.1.final is to potentially fix the exponentiation leak [which is likely 99.9% coercion related :)], but since 3.2.2 will be also a rather short release cycle we will release without such a fix. Please build, test and report any issues. The official 3.2.1 sources should be out in 24 hours unless something goes very wrong and be followed in about another day or two by binaries. Cheers, Michael Merged in Sage 3.2.1.rc1: #3122: Michael Abshoff: after make install, sage tries to write in / usr/local [Reviewed by William Stein] #4254: Martin Albrecht: mq.SR improvements for convenience [Reviewed by William Stein] #4261: Willem Jan Palenstijn: sympow Configure fails to handle aliases [Reviewed by William Stein, Mark Watkins, Michael Abshoff] #4308: Philippe Theveny: make mpc an optional spkg [Reviewed by William Stein, Michael Abshoff] #4317: William Stein: Fix easy-install.pth after moving Sage [Reviewed by Michael Abshoff, Craig Citro] #4321: Alexander Dreyer, Michael Abshoff: wrong Unix permissions in some PolyBoRi files #4352: Marshall Hampton: add support for weight vectors to gran/ groebner_fan [Reviewed by William Stein] #4402: William Stein: Sage 3.1.4: magma related optional doctest failure in tut.tex [Reviewed by Michael Abshoff] #4412: John Cremona: extend the local information function for elliptic curves over number fields [Reviewed by William Stein, Minh Nguyen] #4576: Marshall Hampton: biopython optional package upgrade to 1.49beta [Reviewed by William Stein] #4582: Guillaume Moroz: use Singular's capabilities for computing over fraction fields [Reviewed by Martin Albrecht] #4619: Michael Abshoff: Sage 3.2.1.a1: Update HISTORY.txt with the 3.1.3, 3.1.4 and 3.2 release notes [Reviewed by William Stein] #4654: John Palmieri: for 'sage -testall': put sage version in test log [Reviewed by Michael Abshoff] #4655: William Stein: doctest failure in plot.py with 3.2.1.rc0 on 64- bit SuSe linux [Reviewed by Michael Abshoff] #4657: Michael Abshoff: OSX: gnuplot doesn't start due to dreaded libpng conflict [Reviewed by William Stein] #4658: William Stein: magma -- get rid of redundant caching: just have _magma_init_ [Reviewed by Michael Abshoff] #4659: John Palmieri: remove an extra 'cdef class Integer' line from integer.pyx [Reviewed by Robert Bradshaw] #4660: William Stein: mark inline fortran and inline cython examples optional [Reviewed by Michael Abshoff] #4661: Craig Citro: clean up module_list.py [Reviewed by Michael Abshoff] #4664: Michael Abshoff: Sage 3.2.1.rc1: Fix documentation build issues [Reviewed by Craig Citro] #4668: Michael Abshoff: libSingular's header have too tight permissions [Reviewed by Craig Citro] --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 for testing Sage rc releases on about a dozen boxes it is very convenient, especially once we have to push out two or three fixes at the very end of a release cycle and building from scratch does take a while. As mentioned earlier 3.2.2 will have experimental build Sage library extensions in parallel, so just like parallel doctesting and recently parallel cythonization and now dev-upgrades it is a feature that once I use it I cannot understand how I ever did development work without it. Now all we need is an idiot proof way to pull all dev repos from my merge tree to a remove install and upgrade, but that isn't too hard either technically, someone just has to do it. Cheers, Michael --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups sage-devel group. 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?hl=en -~--~~~~--~~--~--~---
[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. The changes by Craig will force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ Upgrade from rc0 on Fedora 9 has the known issues in sage/rings/polynomial/multi_polynomial_ideal.py Jaap --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 ? (If you want to license it under the GPLv2+ and don't know how to submit it to Sage as a contribution, that is a separate question.) What is really confusing me is that the docstring for matrix_complex_double_dense.pyx (presumably *complex* matrices) is more or less the same as the docstring for matrix_real_double_dense.pyx at http://www.sagemath.org/hg/sage-main/file/8b1d19463fc4/sage/matrix/matrix_real_double_dense.pyx In other words, there are no examples of *complex* matrices in the docstring for matrix_complex_double_dense.pyx, which seems odd. Yep, that's an error. A copy-paste oversight. It's now trac #4669. Thanks for catching it. Jason --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.1.rc1 released
On Dec 1, 7:27 am, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: SNIP 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 for now since I observed different results on various boxen. Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 useful random
variable that I'm just not aware of?
One way to accomplish this is to override expectation in the
DiscreteProbabilitySpace class with the one you sent earlier. We would also
need to do this for variance, covarience, etc., so I admit this is probably
not the ideal solution.
-- Paul
On Mon, Dec 1, 2008 at 3:48 AM, William Stein [EMAIL PROTECTED] wrote:
[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,C), so the
current behavior is correct.
In the defintition of the probability space itself:
sage: ps = DiscreteProbabilitySpace([1,2,3],{1:1/3,2:1/3,3:1/3})
Consider replacing the domain of ps with such a set. Then it
should be clear that you can't average over A, B, and C.
S = [A,B,C]
P = {}
for i in range(3):
P[S[i]] = 1/3
ps = DiscreteProbabilitySpace(S,P)
ps.expectation() # 0.33
This is the random variable with
f(A) = 1,
f(B) = 2,
f(C) = 3,
for which the expectation is 2:
f = {}
for i in range(3):
f[S[i]] = i+1
rv = DiscreteRandomVariable(ps,f)
rv.expectation() # 2.00
On the other hand, I'd be happy with some syntax for creating a
random variable with the uniform distribution P(x) = 1/n on some
set or tuple. Currently this gives an error:
sage: rv = DiscreteRandomVariable(S,f)
but it could easily create the uniform distribution on S behind
the scenes. The reason I didn't do this is the following:
sage: ps1 = DiscreteProbabilitySpace(S,P)
sage: ps2 = DiscreteProbabilitySpace(S,P)
sage: ps1 == ps2
False
Probably this should be considered a bug. But to avoid creating
many copies of the same space, one should consider caching the
probability spaces. However, since dictionaries are mutable, it
can't be cached.
The correct solution might be to define additional types for the
uniform distribution and other standard distributions (which are
the most likely candidates to be created over and over) and have
only one instance of each.
My type DiscreteProbabilitySpace is also too naive -- it really
only implements a FiniteProbabilitySpace.
It is suitable for the examples I've taught in classical cryptography,
but for a statistics class one certainly needs infinite discrete
probability spaces and more classes for distributions on continuous
intervals.
Some thought also needs to be given to their ease of use. The
usual approach to this is to first write some documentation which
describes the desired behavior and then implement the classes and
functions.
--David
- Forwarded message from David R. Kohel [EMAIL PROTECTED]
-
Date: Mon, 1 Dec 2008 09:04:12 +0100
From: David R. Kohel [EMAIL PROTECTED]
To: William Stein [EMAIL PROTECTED]
Cc: Paul Butler [EMAIL PROTECTED]
Subject: Re: Fwd: [sage-devel] Expected value of probability space
User-Agent: Mutt/1.5.6i
Dear William, Paul,
Indeed, the function definition should be:
def expectation(self):
r
The expectation of the discrete random variable, namely
$\sum_{x \in S} p(x) X[x]$,
where $X$ = self and $S$ is the probability space of $X$.
E = 0
Omega = self.probability_space()
for x in self._function.keys():
E += Omega(x) * x
return E
rather than:
def expectation(self):
r
The expectation of the discrete random variable, namely
$\sum_{x \in S} p(x) X[x]$,
where $X$ = self and $S$ is the probability space of $X$.
E = 0
Omega = self.probability_space()
for x in self._function.keys():
E += Omega(x) * self(x)
return E
Cheers,
David
--~--~-~--~~~---~--~~
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: http://www.sagemath.org
-~--~~~~--~~--~--~---
[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 matrix/matrix_complex_double_dense.pyx (but please then add corresponding methods to matrix_real_double_dense.pyx for consistency), or you could add the methods to matrix_double_dense.pyx. Thanks for thinking of these things! Jason --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.2.1.rc1 released
mabshoff wrote: On Dec 1, 7:27 am, Jaap Spies [EMAIL PROTECTED] wrote: mabshoff wrote: SNIP 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 for now since I observed different results on various boxen. sage -t devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py ** File /home/jaap/work/downloads/sage-3.2.1.alpha2/devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py, line 58: sage: S.a,b = R.quotient((x^2 + y^2, 17)) Expected: verbose 0 ... Warning: falling back to very slow toy implementation. Got nothing ** 1 items had failures: 1 of 47 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /home/jaap/downloads/sage-3.2.1.alpha2/tmp/.doctest_multi_polynomial_ideal.py [13.6 s] exit code: 1024 The other M2 issue seems to be gone! Jaap Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 (-1,1),(-1,1) by (x,-1,1),(y,-1,1) in plot3d.parametric_plot3d? Please use f.arguments() instead of f.variables(). The difference is illustrated below: sage: var(x,y) (x, y) sage: f(x,y) = x sage: f.variables() (x,) sage: f.arguments() (x, y) In this case, using variables won't work since only one thing is passed back, but using arguments does work, since the function was defined as taking two inputs. Jason --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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: SNIP 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 for now since I observed different results on various boxen. sage -t devel/sage/sage/rings/polynomial/multi_polynomial_ideal.py ** File /home/jaap/work/downloads/sage-3.2.1.alpha2/devel/sage/sage/rings/polynomi al/multi_polynomial_ideal.py, line 58: sage: S.a,b = R.quotient((x^2 + y^2, 17)) Expected: verbose 0 ... Warning: falling back to very slow toy implementation. Got nothing ** 1 items had failures: 1 of 47 in __main__.example_0 ***Test Failed*** 1 failures. For whitespace errors, see the file /home/jaap/downloads/sage-3.2.1.alpha2/tmp/.doctest_multi_polynomial_ideal. py [13.6 s] exit code: 1024 The other M2 issue seems to be gone! Jaap Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 due to M2 doing the computation instead of the toy Buchberger. I know malb is busy at a conference, so I will likely go that route and hopefully have #4593 sorted out in 3.2.2. Fixing #4593 itself will require fixing the toy Buchberger to return consistent results on all platforms and considering the time table I don't see that happening in the next 24 hours. Thanks for all the issue reports. Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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)) and then replace the arguments (-1,1),(-1,1) by (x,-1,1),(y,-1,1) in plot3d.parametric_plot3d? Please use f.arguments() instead of f.variables(). The difference is illustrated below: sage: var(x,y) (x, y) sage: f(x,y) = x sage: f.variables() (x,) sage: f.arguments() (x, y) In this case, using variables won't work since only one thing is passed back, but using arguments does work, since the function was defined as taking two inputs. I should note that I'm not commenting on the original problem, just commenting on using .arguments() versus using .variables() Jason --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 discussion. Indeed, thanks for pointing it out! My own horse is gerrit, that Google uses, see this issue: http://code.google.com/p/sympy/issues/detail?id=1197 Andy tried to set it up, but it's a lot of work. Ondrej --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 this a useful random variable that I'm just not aware of? Well, ps is a probability space (you did create it as DiscreteProbabilitySpace, rather than DiscreteRandomVariable, which I had missed in my first reply), hence its values are necessarily probabilities. There is no other valid choice. To create a DiscreteRandomVariable, you currently must first create a probability space, then the function on that space. One could have shorter constructors which assume a finite uniform probability space, if not given. The order of the arguments is probability space, then function or values, but if a probability space is no longer required, this order should change. --David --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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. The changes by Craig will force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ Upgrade from rc0 on Fedora 10, 32 bits gives a new failure: [EMAIL PROTECTED] sage-3.2.1.rc0]$ ./sage -t devel/sage/sage/combinat/root_system/type_dual.py sage -t devel/sage/sage/combinat/root_system/type_dual.py ** File /home/jaap/Download/sage-3.2.1.rc0/devel/sage/sage/combinat/root_system/type_dual.py, line 43: sage: [[x.__cmp__(y) for x in ct] for y in ct] Expected: [[0, 1, -1], [-1, 0, -1], [1, 1, 0]] Got: [[0, 1, 1], [-1, 0, 1], [1, 1, 0]] ** File /home/jaap/Download/sage-3.2.1.rc0/devel/sage/sage/combinat/root_system/type_dual.py, line 45: sage: sorted(ct) Expected: [['A', 4], A1xB2, B2xA1] Got: [A1xB2, B2xA1, ['A', 4]] ** 1 items had failures: 2 of 8 in __main__.example_3 ***Test Failed*** 2 failures. For whitespace errors, see the file /home/jaap/Download/sage-3.2.1.rc0/tmp/.doctest_type_dual.py [3.0 s] exit code: 1024 Jaap --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 overhaul of module_list.py by Craig. The changes by Craig will force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ A dumber-than-usual question. I copy/pasted this line into a Terminal window, and not much happens. Following the link gets me to a webpage that doesn't help much. What am I forgetting to do? Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Weaseling out of things is what separates us from the animals. Well, except the weasel. - Homer J Simpson --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 interface by William and the overhaul of module_list.py by Craig. The changes by Craig will force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ A dumber-than-usual question. I copy/pasted this line into a Terminal window, and not much happens. Following the link gets me to a webpage that doesn't help much. What am I forgetting to do? Put a dot and a slash before sage and be sure you are in the right directory Jaap Justin -- Justin C. Walker, Curmudgeon-At-Large Director Institute for the Enhancement of the Director's Income Weaseling out of things is what separates us from the animals. Well, except the weasel. - Homer J Simpson --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 necessarily probabilities, I'm not suggesting that that be changed. But right now if you ask for the expected value of ps, it uses the probability function (from the constructor) as both the probability function and the random variable. In other words, currently ps.expectation() = sum(P(x)^2 over all x). I only brought it up because after looking at the code I was unsure if it was intentional or just a side-effect of the class organization. I'm not aware of any formal definition of the expectation of a probability space, so I wanted to ask to clarify. You mentioned that continuous random variables are missing, which is something I wouldn't mind working on. I may follow up later with an email to get some input on what needs to be done, if you don't mind. -- Paul On Mon, Dec 1, 2008 at 4:50 PM, David Kohel [EMAIL PROTECTED] wrote: 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 this a useful random variable that I'm just not aware of? Well, ps is a probability space (you did create it as DiscreteProbabilitySpace, rather than DiscreteRandomVariable, which I had missed in my first reply), hence its values are necessarily probabilities. There is no other valid choice. To create a DiscreteRandomVariable, you currently must first create a probability space, then the function on that space. One could have shorter constructors which assume a finite uniform probability space, if not given. The order of the arguments is probability space, then function or values, but if a probability space is no longer required, this order should change. --David --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 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 force you to rebase any patch adding extensions, but not the file is prettied up and most importantly there aren't any duplicates any more. In 3.2.2 we will also merge code written by Craig that allows building of the Sage library extensions in parallel, so it was well worth it. Other than that the usual assortment of bug fixes, among them some long awaited fixes for make install. We also fixed a bug that prevented binaries on sage.math to work properly (see #4317 for the gory details), so form now on I will roll binaries for sage.math again. As usual sources and the sage.math-only binary can be found in http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/ You can also upgrade 3.2.1.alpha2 or higher via sage -upgrade http://sage.math.washington.edu/home/mabshoff/release-cycles-3.2.1/sage-3.2.1.rc1/ A dumber-than-usual question. I copy/pasted this line into a Terminal window, and not much happens. Following the link gets me to a webpage that doesn't help much. What am I forgetting to do? Put a dot and a slash before sage and be sure you are in the right directory Hmm...should have mentioned that I used ./sage, and I was in the 'rc0' directory. Sounds ominous... Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds If you're not confused, You're not paying attention --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 cleanly against 3.2.1.rc1 or later. The first two tickets that will go in are coercion tickets, so depending on how messy those are we might do an alpha0 very, very quick to make rebasing easier. As usual I can only suggest that you mosy on over to trac and do some reviews :) Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 for libfplll.spkg, too. Well, could I propose we change it? - Robert --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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? That is the name malb gave it initially and it just stuck. The same applies for libfplll.spkg, too. Well, could I propose we change it? Fine by me, it could be done with a little magic to deps. But why would you want to do so? For m1ri I would guess? - Robert Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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. 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. Well, could I propose we change it? Fine by me, it could be done with a little magic to deps. But why would you want to do so? For m1ri I would guess? Just for consistency. I actually had trouble finding it (first looked for m*, then unpacked linbox to see if it was in there...) - Robert --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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] 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. Well, could I propose we change it? Fine by me, it could be done with a little magic to deps. But why would you want to do so? For m1ri I would guess? Just for consistency. I actually had trouble finding it (first looked for m*, then unpacked linbox to see if it was in there...) Ok, currently we have the following in the tree: Sprocketer:~ michaelabshoff$ cd Desktop/sage-3.2.1.rc1-qf/spkg/ standard/ Sprocketer:standard michaelabshoff$ ls -al *lib* -rw-r--r--@ 1 michaelabshoff staff 272776 Nov 26 22:28 cddlib-094b.p3.spkg -rw-r--r--@ 1 michaelabshoff staff 1593104 Nov 26 22:28 eclib-20080310.p7.spkg -rw-r--r--@ 1 michaelabshoff staff 293382 Nov 26 22:28 libfplll-2.1.6-20071129.p5.spkg -rw-r--r--@ 1 michaelabshoff staff 970913 Nov 26 22:28 libgcrypt-1.4.0.p2.spkg -rw-r--r--@ 1 michaelabshoff staff 383786 Nov 26 22:28 libgpg_error-1.6.p0.spkg -rw-r--r--@ 1 michaelabshoff staff 713789 Nov 26 22:28 libm4ri-20080909.spkg -rw-r--r--@ 1 michaelabshoff staff 626176 Nov 26 22:28 libpng-1.2.22.p8.spkg -rw-r--r--@ 1 michaelabshoff staff 4832798 Nov 26 22:28 matplotlib-0.98.3.p3.spkg -rw-r--r--@ 1 michaelabshoff staff 436207 Nov 26 22:28 zlib-1.2.3.p4.spkg I plan to upgrade png in 3.2.2 and will also attempt to do the upgrade to fplll 3.0.x. I guess if malb is ok with the rename we could also change the name next time he releases an updated version. I think we can eliminate libgpg_error and libgcrypt since gnutls these days contains its own copy of those two libraries and builds them on demand when it does not detect them externally. Having the in tree versions is certainly a good thing since less can go wrong. So if we do this we can do some cleanup and reducing the number of spkgs is always a good thing IMHO. :) Does anybody else have an opinion? If we do this I can open tickets for the various tasks that need to be done. - Robert Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 you have patches that are supposed to get in please make sure they apply cleanly against 3.2.1.rc1 or later. The first two tickets that will go in are coercion tickets, so depending on how messy those are we might do an alpha0 very, very quick to make rebasing easier. As usual I can only suggest that you mosy on over to trac and do some reviews :) And yes, you can do sage -upgrade to get to sage-3.2.1, or download the source tarball from http://sagemath.org/src/ --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 http://wiki.sagemath.org/ optional_packages_available_for_SAGE? (I'm guessing the former.) Is the list obtained by 'sage --optional' the same as the list on sagemath.org http://sagemath.org/packages/optional/? (I think so.) Should the optional packages boehm_gc-7.1.p0 and jmol-11.5.2-src-v2 be deleted, because the first is now a standard package and for the second, the (presumably newer) package jmol-11.6.rc8 is standard? I've also been trying to put together short descriptions of these, to be put on various web pages and listed when you type 'sage -- optional'. What's the procedure for implementing something like this? Should I open a trac ticket, and if so, what file(s) do I patch? (I can also post my list of descriptions here in sage-devel for people to comment on.) It would also be nice to have descriptions for the standard packages and the experimental ones, while we're at it... John --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 http://wiki.sagemath.org/ optional_packages_available_for_SAGE? (I'm guessing the former.) Yes, the former is more current. I think we should delete the page in the wiki since it is unmaintained. Is the list obtained by 'sage --optional' the same as the list on sagemath.org http://sagemath.org/packages/optional/? (I think so.) Yes, the html page is automatically generated when new spkgs are updated. Should the optional packages boehm_gc-7.1.p0 and jmol-11.5.2-src-v2 be deleted, because the first is now a standard package and for the second, the (presumably newer) package jmol-11.6.rc8 is standard? Not all people will be running Sage = 3.2.1. for a while, so I would keep the boehm_gc around for now. The jmol.spkg is special since the optional spkg is the source version. I guess it would be good if someone updated it one day. I've also been trying to put together short descriptions of these, to be put on various web pages and listed when you type 'sage -- optional'. What's the procedure for implementing something like this? Should I open a trac ticket, and if so, what file(s) do I patch? (I can also post my list of descriptions here in sage-devel for people to comment on.) There already is a ticket for that: #855 It would also be nice to have descriptions for the standard packages and the experimental ones, while we're at it... Yeah, SPKG.txt is supposed to do that. SPKG.txt is written in wiki text and is supposed to be copied into the wiki as they are updated. But many of them are incomplete and often the version in the wiki is not very current. Look at http://wiki.sagemath.org/Sage_Spkg_Tracking if somebody could just extract the current SPKG.txt files from the 3.2.1 release and update the good looking ones in the wiki and then start cleaning up the ugly ones it would be very nice. I mean to add one more section to the default SPKG.txt and that would be a list of all the spkgs that depend on this spkg. I.e. the SPKG.txt in numpy would list scipy as an spkg that depends on it. That way if one updates for example pari one would know that one would have to bump eclib and lcalc amongst others since it isn't always obvious what the dependencies are. Once we are done it would be nice to extract all the dependency data and create a graph for it :) John Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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? --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 still correctable? Oops, *now* I remember creating the trac account for you. It is fixed in http://trac.sagemath.org/sage_trac/attachment/ticket/4646/sage-3.2.1-release-notes-draft2.txt and should show up shortly as the official sage-3.2.1 change log. To avoid issues like that in the future please log into trac and add yourself to the listing of accounts at the bottom of http://trac.sagemath.org/sage_trac/ My apologies again. I had asked around in IRC if anybody knew who klee was and by accident someone with that last name is a grad student at UW. :) Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 wrong person in the release note of Sage 3.2.1 rc0. My name is Kwankyu Lee. Is this still correctable? Oops, *now* I remember creating the trac account for you. It is fixed in http://trac.sagemath.org/sage_trac/attachment/ticket/4646/sage-3.2.1-release-notes-draft2.txt Damn! Just when I'm about to upload a patch against draft 1, you beat me to it :-) My apologies again. I had asked around in IRC if anybody knew who klee was and by accident someone with that last name is a grad student at UW. :) I got the name from the diff file, note as displayed within a web browser, but the file that one would get if click on the link Original Format. -- Regards Minh Van Nguyen --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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: http://www.sagemath.org -~--~~~~--~~--~--~---
[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 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? Oops, *now* I remember creating the trac account for you. It is fixed in http://trac.sagemath.org/sage_trac/attachment/ticket/4646/sage-3.2.1-... Damn! Just when I'm about to upload a patch against draft 1, you beat me to it :-) Well, Kwankyu's initial email was moderated, so I could react before the vast majority of people had even read the email :) My apologies again. I had asked around in IRC if anybody knew who klee was and by accident someone with that last name is a grad student at UW. :) I got the name from the diff file, note as displayed within a web browser, but the file that one would get if click on the link Original Format. Yep. We are currently playing with an upgraded trac 0.11.2.1 and that one offers raw links thanks to Mike Hansen. Unless something bad happens we will switch to the new trac in about a week. It is so much better it isn't even funny. Check out the pretty graphs one can create with it: http://sage.math.washington.edu/home/mabshoff/WeeklyTicketNumbers_01_2006-12_2008.png This one plots opened vs. closed tickets as well as the total number of open tickets on a weekly basis. Anyway: If you ever think that I made a mistake with credits please immediately alert me so I can fix the issue. Giving credit where credit is due is very, very important. In case you don't want to do this on list feel also free to ping me off list. Even if it is an ancient release we are more than happy to fix it. -- Regards Minh Van Nguyen Cheers, Michael --~--~-~--~~~---~--~~ 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: http://www.sagemath.org -~--~~~~--~~--~--~---
