Sage 2.8.15 has been released. It is available at
http://sagemath.org/download.html
The following people contributed this release:
- Craig Citro
- Dan Drake
- David Harvey
- Michael Abshoff
- Martin Albreecht
- Jen Balakrishnan
- Robert Bradshaw
- Jason Grout
- Mike Hansen
- Leif Hille
- Josh Kantor
- Robert Miller
- Joel Mohler
- David Roe
- Jaap Spies
- William Stein
- Brian "trixb4kidz"
- Carl Witty
- Paul Zimmermann
Cheers,
Michael Abshoff (release chair), William Stein
* Major Features, New Spkgs and Bugfixes
Singular was updated to the latest 3-0-4 release. But neither PolyBoRi
nor ATLAS made it into the final release. But the vast majority of the
prep work needed to make ATLAS a standard spkg was finally done in
this release cycle. PolyBoRi will probably become an optional spkg
first until all the details have been worked out.
We closed a total of 62 tickets, for details see
http://www.sagetrac.org/sage_trac/query?status=closed&milestone=sage-2.8.15
for details.
Closed Tickets:
rc1 - merged:
#1074: Martin Albrecht: Singular segfault with monitor("","io"); -
fixed upstream by Hans Scher L-series
#1309: Robert Miller: graphs: generate trees
#1356: Carl Witty: fix bug when taking abs() of exactly known QQbar
#1357: Carl Witty: the polynomial .roots() method should work with
ring=QQbar
#1368: William Stein: algorithm for computing quotient was sometimes
wrong
#1372: Michael Abshoff: dokchitser.py doctest failure (numerical
noise)
#1973: William Stein, Carl Witty: improve doctests of
quotient_module.py
#1374: Carl Witty, William Stein: segfault in coercion with matrices
and ints
#1375: William Stein: tutorial texing typo issue
#1376: Carl Witty, Michael Abshoff: fix numerical doctest failures in
2.8.15.rc0
alpha2 - Merged:
#787: William Stein: quotient spaces of vector spaces
#799: Leif Hille, William Stein: fix tachyon bug
#962: Mike Hansen: automatic precision extension for long decimal
literals does very strange things
#1128: David Roe, Robert Bradshaw: Coercion of complex numbers
#1160: William Stein: *major* bug in using the sage notebook as a
maxima notebook
#1179: Robert Miller: change all #!/bin/sh to #!/bin/bash in
$SAGE_LOCAL/bin (Solaris related)
#1184: Michael Abshoff: OSX 10.4: moving sage breaks recompile -> NTL
related
#1201: William Stein: add gramm-schmidt to sage
#1208: Jaap Spies: Faster _choose in matrix2.py
#1211: David Harvey: NTL crash in polynomial remainder over ZZ
#1222: Josh Kantor: cvxopt import trouble on PPC OSX 10.4
#1269: Carl Witty: make sage -t --omega work
#1275: Carl Witty: implementation of QQbar
#1290: Dan Drake, William Stein: add computation of Rencontres numbers
#1292: Carl Witty: fix bug in polynomial root finding mod n
#1298: Josh Kantor: build lapack on OSX for the ATLAS build
#1327: Josh Kantor: Solaris: scipy import error - fortran compiler
related
#1342: William Stein: very serious bug in number field residue_field
#1349: to avoid massive confusion, make the default notebook location
$HOME/.sage/notebook
#1353: Robert Miller: fix easy bug in graph_database.py
#1354: Michael Abshoff: Solaris modp 64 bit fix
#1355: Michael Abshoff: numerical noise doctest failures in
rings/polynomial/[complex_roots.py|polynomial_element.pyx]
#1361: Robert Miller: reimplement graph generation
#1364: William Stein: sage/modules/quotient_module.py doctest failure
alpha1 - Merged:
#644: Mike Hansen: fix "(sin + cos)(1) does not work"
#1148: David Harvey, Robert Bradshaw: valuation doesn't work for
rational numbers
#1214: Mike Hansen: error in polynomial ideal membership testing
#1249: Robert Miller: fixes bug in graph plotting with partitions
#1265: Paul Zimmermann: documentation typos
#1279: Martin Abrecht: LLL on "tall" matrices immediately crashes sage
#1280: Mike Hansen: make Permutation(range(10)).random() fast instead
of dog slow.
#1333: William Stein: fix a major inefficiency in floating point
square root computation in Sage
#1334: David Harvey: Constant polynomial can't be converted to
rational
#1341: Josh Kantor: add script so that which_fortran returns g95 or
gfortran
#1350: Mike Hansen: sage-2.8.15.alpha0 doctest error in plot.py
#1352: Mike Hansen: doctest error in 2.8.15.alpha0
polynomial_element.pyx
alpha0 - Merged:
#645: Mike Hansen: multi-argument call for symbolic expressions
#847: Mike Hansen: rewrite the symbolic calculus package to do
evaluation/simplification without recursion
#1107: William Stein: add minkowski bound function for number fields
#1111: Mike Hansen: Symbolic equation expand left and right
#1134: David Harvey: optimize creating elements of orders and number
fields by coercing in lists [I left this ticket open fow now
- see comment]
#1141: Joel Mohler: improve Number Field elements arithmetic speed
#1268: Carl Witty: new version of MPFI.spkg
#1270: Carl Witty: implement complex intervals
#1273: Carl Witty: implement complex root isolation
#1275: Carl Witty: implementation of QQbar
#1295: Jason Grout: Added code to create the butterfly graph
#1330: Michael Abshoff: Solaris: fix sympy doctest numerical noise
#1331: Michael Abshoff: Solaris: fix complex_double doctest numerical
noise
#1335: Michael Abshoff: Linux PPC: lcalc doctest failure
#1336: Michael Abshoff: Linux PPC:
rings/polynomial/polynomial_element.pyx doctest failure
#1345: Mike Hansen: I is sometimes wrapped in SymbolicConstant,
sometimes not
Reviewers: Carl Witty, William Stein, Mike Hansen, Robert Miller,
Michael Abshoff; apologies to anybody I forgot.
Feeback: Jaap Spies, Justin Walker, apologies to anybody I forgot.
* Known Issues with 2.8.15
- FLINT might misbuild due to missing Python
* Upcoming Releases
Sage 2.9 is planned for the end of this week. Proposed major features
are:
- R
- ATLAS BLAS/Lapack
- FLINT 1.0
* Coverage
For 2.8.15:
Overall weighted coverage score: 34.8%
Total number of functions: 17743
Compared to 2.8.13 this is an increase by 0.4%.
* About Sage (http://www.sagemath.org)
Sage is developed by volunteers and combines 71 open source packages.
It is available for download from sagemath.org and its mirrors in
source or binary form. If you have any questions and/or problems
please report them to the google groups sage-devel, sage-support,
sage-forum or sage-newbie. You can also drop by in #sage-devel in
freenode.
--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org
> There already is an optional/experimental R.spkg and because of rpy
> little integration work into Python needs to be done. It will probably
> take a while to expose all the functionality desired by Sage
> developers directly, but we need to start by including it.
well, then if there is anything I can help with - from testing to
whatever - you can count me in :) I'm already downloading it :)
A.
Please type
sage: install_package('sage -i r-2.6.1rc.p1')
and report back whether the install works for you or not (it's an experimental
package still, which means that it's likely to *not* work for a lot of people).
If it does install, try this:
sage: import rpy
sage: rpy.r.t_test(range(100))
Check out
rpy.sourceforge.net
for more discussion about rpy, which provides a very
fast interface to essentially all the functionality of R.
NOTE: As of now, you'll probably want to do
sage: RealNumber = float; Integer = int
to turn off preparsing of floats and ints when using R, since
the patch for making R play nicely with Sage types isn't in
yet.
William
> sage: install_package('sage -i r-2.6.1rc.p1')
I actually installed through command line, but it's mostly same - it
went ok, but.....
> and report back whether the install works for you or not (it's an experimental
> package still, which means that it's likely to *not* work for a lot of people).
I had to edit manually in 2 places, first $SAGE_HOME/local/bin/R has
variable R_HOME_DIR pointing to build dir instead of install dir,
after changing it to right dir I was able to import rpy, because
before it failed...
> If it does install, try this:
>
> sage: import rpy
I did:
sage: from rpy import *
and it worked so quite ok... but not exactly yet :)... at first when I
wanted to check r object I was getting traceback about missing
variable, after change in file rpy.py in line 312 from
Rver = self.__getitem__('R_version_string')
to
Rver = self.__getitem__('R.version.string')
it started to report version, it said:
RPy version 1.0-RC3 [R version 2.6.1 RC (2007-11-24 r43532)]
so ok...
> sage: rpy.r.t_test(range(100))
that test works like a charm...
> Check out
> rpy.sourceforge.net
> for more discussion about rpy, which provides a very
> fast interface to essentially all the functionality of R.
> NOTE: As of now, you'll probably want to do
> sage: RealNumber = float; Integer = int
> to turn off preparsing of floats and ints when using R, since
> the patch for making R play nicely with Sage types isn't in
> yet.
I noticed Integer -> int problem when I was trying
http://rpy.sourceforge.net/rpy_demo.html, got without glitch to some
place, now I try to get:
sage: r.png('faithful_histogram.png',width=int(733),height=int(550))
but no luck currently, anyway I'm still looking around... :)
regards,
Andrzej.
PS.: maybe this should be in separate topic or other list? currently I
use only "reply" from browser, but I think there will be lot more
reports about this :)
Actually, I had posted the wrong direction -- it's still the case that R builds
in the build directory, the install points to that ("make install" for R
doesn't work like for a normal program), then the build directory gets deleted.
See this thread on R in SAge, which has better directions:
In particular, it is best to build like this
sage -f -m r-2.6.1rc.p1
to leave the build directory around afterwards.
I was able to get the image to work last time I tried, so it's definitely
possible.
-- Wiliam
(1) I very much thought that I had done graphics with the above
build options using png. Without those options R will definitely fail
to build on many test platforms, by the way.
(2) I don't see why X11 should be necessary to generate png files
using R -- the whole point of png's should be to avoid having to
use X11.
That said, I could be wrong about some of the above. Does R really
require X11 as a dependency just to do png graphics? That would suck.
William
(1) I very much thought that I had done graphics with the above
build options using png. Without those options R will definitely fail
to build on many test platforms, by the way.
(2) I don't see why X11 should be necessary to generate png files
using R -- the whole point of png's should be to avoid having to
use X11.
That said, I could be wrong about some of the above. Does R really
require X11 as a dependency just to do png graphics? That would suck.
OK -- I just retested this on my *linux* install, and indeed, creating
png's doesn't work because of no X11. How annoying.
William
>
> Hello folks,
>
> Sage 2.8.15 has been released. It is available at
>
> http://sagemath.org/download.html
Built and tested w/o errors on Mac OS X, as follows, both with
"parallel make":
10.4.11 (Dual Quad-Core Xeon -j6):
real 63m1.611s
user 48m35.838s
sys 25m26.978s
All tests passed!
Total time for all tests: 2366.0 seconds
10.5.1 (Core Duo, -j2):
real 89m5.315s
user 74m17.804s
sys 16m57.508s
All tests passed!
Total time for all tests: 2552.2 seconds
Still seeing mwrank crashing during the tests (10.5), but no comment
in the logs.
Justin
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
My wife 'n kids 'n dogs are gone,
I can't get Jesus on the phone,
But Ol' Milwaukee's Best is my best friend.
-----------
>> Still seeing mwrank crashing during the tests (10.5), but no comment
>> in the logs.
>
> Any chance you could narrow this down to a specific doctests case,
> i.e. input parameters for mwrank? Then I could take a look then, but
> just shooting into the blue seems pointless.
I thought I batted that ball over to your court :-}
I know it happens during the 'tut.tex' doc test, and on a few more
way later in the tests; the latter whiz by quickly, so it's very hard
to peg it.
I will use the highly original trick of binary search :-}, and slice
and dice tut.tex to see if I can nail it. I'll try this tonight,
when I'm home.
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------
Thanks. However:
(1) What operating system are you using exactly, and what gcc version?
(2) Could you send the build log for building R (i.e., the end of
SAGE_ROOT/install.log)?
(3) If you type
sage: !R
what happens?
--William
Alright, I'm pretty stumped so far. what happens if you
just edit
/opt/sage/local/lib/python2.5/site-packages/rpy.py
and put a # at the beginning of the line
RException = _rpy.RException
and try again? I'm just curious.
Something is really weird, since for all my installs the context for the code
you list above is:
# Three new exceptions
# base exception
RPyException = _rpy.RPy_Exception;
# R <-> Python conversion exception
RPyTypeConversionException = _rpy.RPy_TypeConversionException;
# Exception raised by R
RPyRException = _rpy.RPy_RException
# for backwards compatibility
RException = RPyException
I wonder why your code looks totally different, why you have
# The new exception
RException = _rpy.RException
That code doesn't even appear in my rpy.py.
--
I'm sorry for the troubles you're having, and greatly appreciate
that your testing the R spkg. That rpy doesn't overwrite
old files, etc., is something I'll have to keep in mind when we make
new spkg's that include new versions of R and rpy -- we'll have
to be careful to delete the old rpy files manually.
-- William
Excellent. Many thanks for your report. We'll incorporate your fixes
into sage: http://trac.sagemath.org/sage_trac/ticket/1476
> On Dec 12, 2007 2:35 AM, Marshall Hampton <hamp...@gmail.com> wrote:
> >
> > Hi,
> >
> > I'm not very familiar with R and rpy, but in reading the rpy
> > documentation they implied that if you install optional R components
> > you do _not_ have to rebuild rpy...but I suppose someone should verify/
> > test that.
> >
> > Marshall Hampton
> >
>
> cheers,
> Andrzej.
>
>
> >
>
--