Re: [sage-devel] Randomised testing against Mathematica
Is there a mathematica test suite we could adapt or a standardized set of tests we could use? Maybe we could take the 100 most often used functions and make a test suite? LOOK ITS A SIGNATURE CLICK IF YOU DARE--- http://www.google.com/profiles/zitterbewegung On Wed, Mar 3, 2010 at 12:04 AM, David Kirkby wrote: > Has anyone ever considered randomised testing of Sage against Mathematica? > > As long as the result is either > > a) True or False > b) An integer > > then comparison should be very easy. As a dead simple example, > > 1) Generate a large random number n. > 2) Use is_prime(n) in Sage to determine if n is prime or composite. > 3) Use PrimeQ[n] in Mathematica to see if n is prime or composite. > 4) If Sage and Mathematica disagree, write it to a log file. > > Something a bit more complex. > > 1) Generating random equation f(x) - something that one could integrate. > 2) Generate generate random upper and lower limits, 'a' and 'b' > 3) Perform a numerical integration of f(x) between between 'a' and 'b' in Sage > 4) Perform a numerical integration of f(x) between between 'a' and 'b' > in Mathematica > 5) Compare the outputs of the Sage and Mathematica > > A floating point number, would be more difficult to compare, as one > would need to consider what is a reasonable level of difference. > > Comparing symbolic results directly would be a much more difficult > task, and probably impossible without a huge effort, since you can > often write an equation in several different ways which are equal, but > a computer program could not easily be programmed to determine if they > are equal. > > One could potentially let a computer crunch away all the time, looking > for differences. Then when they are found, a human would had to > investigate why the difference occurs. > > One could then add a trac item for "Mathematica bugs" There was once a > push for a public list of Mathematica bugs. I got involved a bit with > that, but it died a death and I became more interested in Sage. > > Some of you may know of Vladimir Bondarenko, who is a strange > character who regularly used to publish Mathematica and Maple bugs he > had found. In some discussions I've had with him, he was of the > opinion that Wolfram Research took bug reports more seriously than > Maplesoft. I've never worked out what technique he uses, but I believe > is doing some randomised testing, though it is more sophisticated that > what I'm suggesting above. > > There must be a big range of problem types where this is practical - > and a much larger range where it is not. > > You could at the same also compare the time taken to execute the > operation to find areas where Sage is much faster or slower than > Mathematica. > > Dave > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Randomised testing against Mathematica
On 2-Mar-10, at 10:04 PM, David Kirkby wrote: Has anyone ever considered randomised testing of Sage against Mathematica? Randomised? No. But I have tested my code for computing theta functions against all of Mathematica, Maple, and Magma -- curiously, the three rarely agreed. Nick -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] wrapping fortran libraries in an spkg
I couldn't find any good spline routines in Sage for constructing simple splines with given boundary conditions (are there any? There are some spline routines in scipy, but not what I was looking for). So I found one of the standard routines on netlib and used that inside of a %fortran cell in the notebook [1]. If I or one of my students wanted to wrap this routine in a Sage Spline class, does anyone have any tips for how to do it? Is there an example of a fortran library that a Sage class (Cython or Python) interfaces directly with? For example, I know we include lapack, but I didn't find any files in Sage that seemed to directly import or use a lapack function. Thanks, Jason [1] http://sagenb.org/home/pub/1708/ -- Jason Grout -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Randomised testing against Mathematica
Has anyone ever considered randomised testing of Sage against Mathematica? As long as the result is either a) True or False b) An integer then comparison should be very easy. As a dead simple example, 1) Generate a large random number n. 2) Use is_prime(n) in Sage to determine if n is prime or composite. 3) Use PrimeQ[n] in Mathematica to see if n is prime or composite. 4) If Sage and Mathematica disagree, write it to a log file. Something a bit more complex. 1) Generating random equation f(x) - something that one could integrate. 2) Generate generate random upper and lower limits, 'a' and 'b' 3) Perform a numerical integration of f(x) between between 'a' and 'b' in Sage 4) Perform a numerical integration of f(x) between between 'a' and 'b' in Mathematica 5) Compare the outputs of the Sage and Mathematica A floating point number, would be more difficult to compare, as one would need to consider what is a reasonable level of difference. Comparing symbolic results directly would be a much more difficult task, and probably impossible without a huge effort, since you can often write an equation in several different ways which are equal, but a computer program could not easily be programmed to determine if they are equal. One could potentially let a computer crunch away all the time, looking for differences. Then when they are found, a human would had to investigate why the difference occurs. One could then add a trac item for "Mathematica bugs" There was once a push for a public list of Mathematica bugs. I got involved a bit with that, but it died a death and I became more interested in Sage. Some of you may know of Vladimir Bondarenko, who is a strange character who regularly used to publish Mathematica and Maple bugs he had found. In some discussions I've had with him, he was of the opinion that Wolfram Research took bug reports more seriously than Maplesoft. I've never worked out what technique he uses, but I believe is doing some randomised testing, though it is more sophisticated that what I'm suggesting above. There must be a big range of problem types where this is practical - and a much larger range where it is not. You could at the same also compare the time taken to execute the operation to find areas where Sage is much faster or slower than Mathematica. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
Dr. David Kirkby wrote: Dtrace might be a very useful tool to find out what is using the time up. Dtrace was developed by Sun, but Apple use it on OS X. I believe Apple have wrapped it in a GUI called 'Instruments'. I should point out that * You need to be root to use Dtrace * I'm not aware of any common linux ditro with Dtrace That rather cuts down the number of people that have access to it. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
William Stein wrote: By the way, OS X 10.6 was a major new release of OS X, and the big claim that Jobs made when announcing it was: "no new features!" Marketing comes into play a lot here. I think there were good reasons, because 10.5 was highly criticised as buggy. It was all about optimization all over the place, better 64-bit support under the hood, etc. My impression is that this sort of "quality improvement under the hood" -- not necessarily new features -- is something a lot of users really, really value, especially in free software. I agree. (I did think of requesting it was called 5.0 when the Solaris port was finished, but guess that would not be too popular!) What's wrong with that goal? > It would be nice if the 5.0 goal list was similarly comprehensible. How about: 1. 85% doctest coverage score 2. Official Solaris 10 support Could full Solaris support for Sage not be sufficient for a 5.0 release, without the other requirements? A build on a new platform would be a reason for a major release. As would it be when the Cygwin port is working. If so, 5.0 could be out very soon indeed, as I can now build Sage with every doctest passing (including all the long ones). 3. Build with SAGE_CHECK=yes works on all platforms, *and* every package has at least some spkg-check in it, that checks something. 4. Greatly improve the Sage startup time. This needs to be made precise, e.g., the following should take < 0.5 seconds when run repeatedly from a scratch disk on sage.math: time sage -c "print factor(2010)" Right now it takes over 1.5 seconds every time. wst...@sage:~$ time sage -c "print factor(2010)" 2 * 3 * 5 * 67 real0m1.535s user0m1.140s sys 0m0.460s Personaly I don't find that too excessive for a large tool. How long does Gimp take to start? Dtrace might be a very useful tool to find out what is using the time up. Dtrace was developed by Sun, but Apple use it on OS X. I believe Apple have wrapped it in a GUI called 'Instruments'. It was using dtrace that I realised that Sage constantly calling 'top' was bringing my system to its knees. The load average was huge, but no processes appeared to be running. 'top' is called in an infinite loop, as you can see at: http://trac.sagemath.org/sage_trac/attachment/ticket/8391/top-to-prstat.patch If 'top' is not installed, so the Sage library just keeps calling it until the doctest times out. It's next to impossible to see that sort of thing with ps or top. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: sqlite - update to the latest release
Dima Pasechnik wrote: Dave, you ought to say at least how to get the new spkg Dima It was on the ticket, but as Ming has pointed out, it is at http://boxen.math.washington.edu/home/kirkby/Solaris-fixes/sqlite-3.6.22/sqlite-3.6.22.spkg Dave On Mar 3, 10:51 am, "Dr. David Kirkby" wrote: If anyone has a minute, I would appreciate a review of http://trac.sagemath.org/sage_trac/ticket/8408 which is a simple update to the latest stable sqlite release. (There is one minor change to spkg-install, which tests for SAGE64 being only "yes" and not "yes" or "1" as previously the case.) The sqlite update fixes 5 test failures on Solaris - #8397, #8398, #8399 #8400 and #8401. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] fractals in sage
On Tue, Mar 2, 2010 at 5:28 PM, Dr. David Kirkby wrote: > William Stein wrote: >> >> Hi, >> >> A student of mine is going to add to sage the capability of plotting >> lots and lots of fractals easily. E.g., >> >> sage: fractals.[tab] >> lots of stuff >> >> sage: fractals.julia([params]).show(figsize=10) >> [up pops a julia set] >> >> The trac ticket where this starts is here: >> http://trac.sagemath.org/sage_trac/ticket/8423 >> >> This isn't going to be some complicated fancy object oriented >> abstract dynamical metaclassed framework. It's just a bunch of >> functions to draw fractals. And at first it could even be slow >> (though obviously some cython master will probably clear through it at >> some point and make everything really fast, without having to change >> or write any docs). I can imagine that most of the files will consist >> of examples and docstrings rather than actual code, too. >> >> The point of this email: if you like plotting fractals, and have some >> potentially useful code to contribute, then please post to this thread >> or http://trac.sagemath.org/sage_trac/ticket/8423 with them. Or if >> you really want to help, then do so. >> >> -- William >> > > Those sorts of images could be good for your calender. > > I recall many years ago programming the 80387 maths coprocessor chip at the > assembly level to generate the fastest Mandlebrot set I could. If I recall > correctly, it ran at 25 MHz, which I think was the fastest any 80386/80376 > chip run at. So how long did it take to calculate the 256x265 pixels mandelbrot set? I remember it took couple hours for me (I wrote it in Pascal...). > > There is the open-source 'fractint' program which does the same sort of > thing, but in integer maths, which is obviously quicker, though the floating > point processors now are a lot better than they used to be. I recall > computing tables of sin() and cos() for Monte Carlo simulations, then using > a lookup rather than compute the sines and cosines each time, as it was too > slow. Now, you are better to just call sin or cos in an FPU, rather than > look them up in a table. Right. Ondrej -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: sqlite - update to the latest release
Hi Dima, On Wed, Mar 3, 2010 at 2:03 PM, Dima Pasechnik wrote: > Dave, > you ought to say at least how to get the new spkg >From any computer outside of the Sage cluster: $ wget http://boxen.math.washington.edu/home/kirkby/Solaris-fixes/sqlite-3.6.22/sqlite-3.6.22.spkg >From compute node within the Sage cluster: $ cp /home/kirkby/Solaris-fixes/sqlite-3.6.22/sqlite-3.6.22.spkg /home/username/ -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: sqlite - update to the latest release
Dave, you ought to say at least how to get the new spkg Dima On Mar 3, 10:51 am, "Dr. David Kirkby" wrote: > If anyone has a minute, I would appreciate a review of > > http://trac.sagemath.org/sage_trac/ticket/8408 > > which is a simple update to the latest stable sqlite release. (There is one > minor change to spkg-install, which tests for SAGE64 being only "yes" and not > "yes" or "1" as previously the case.) > > The sqlite update fixes 5 test failures on Solaris - #8397, #8398, #8399 #8400 > and #8401. > > Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: How do I add Mercurial patches before Sage built?
Hi Dima, On Wed, Mar 3, 2010 at 1:58 PM, Dima Pasechnik wrote: > perhaps it's a good idea to have these things added to > http://wiki.sagemath.org/MercurialQueues Be my guest. Feel free to do so. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: How do I add Mercurial patches before Sage built?
perhaps it's a good idea to have these things added to http://wiki.sagemath.org/MercurialQueues On Mar 3, 9:24 am, Minh Nguyen wrote: > Hi David, > > On Wed, Mar 3, 2010 at 12:17 PM, Dr. David Kirkby > > wrote: > > > > > 'qimport' reports no issues, but 'qfinish -a' tells me there are no patches > > applied. I've verified that indeed the patches are not applied. > > Correction: > > (1) hg qimport /URL/or/patch/to/patch.path # get/download the patch > (2) hg qpush # really apply the patch > > Repeat (1) and (2) as often as necessary. After that, do this > > $ hg qapplied > > This should return the list of patches you have applied using "hg > qpush". Once you are ready, do > > $ hg qfinish -a > > Apology for missing the "hg qpush" part. > > -- > Regards > Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] sqlite - update to the latest release
If anyone has a minute, I would appreciate a review of http://trac.sagemath.org/sage_trac/ticket/8408 which is a simple update to the latest stable sqlite release. (There is one minor change to spkg-install, which tests for SAGE64 being only "yes" and not "yes" or "1" as previously the case.) The sqlite update fixes 5 test failures on Solaris - #8397, #8398, #8399 #8400 and #8401. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
On Tue, Mar 2, 2010 at 2:42 PM, David Kirkby wrote: > On 2 March 2010 19:01, Robert Bradshaw wrote: > >> Just a thought, would knocking out this important list of bugs be a good >> goal for Sage 5.0? >> >> - Robert > > It is certainly unusual the way Sage version numbers go. In just about > any other software project Assuming the version is of the form X.Y.Z, > > X is incremented if there is major new functionality > Y is incremented if there is added, but less major functionality > Z is incremented when bug fixes are made. > > I think someone might be a bit disappointed if they update Sage to > 5.0.0, without seeing some tangible new functionality. I'll give disappointed customers a full money-back refund. By the way, OS X 10.6 was a major new release of OS X, and the big claim that Jobs made when announcing it was: "no new features!" It was all about optimization all over the place, better 64-bit support under the hood, etc. My impression is that this sort of "quality improvement under the hood" -- not necessarily new features -- is something a lot of users really, really value, especially in free software. > (I did think of requesting it was called 5.0 when the Solaris port was > finished, but guess that would not be too popular!) What's wrong with that goal? It was one of the main goals for Sage-4.0, after all :-). The goals for Sage-4.0 were something like: * 75% doctest coverage *OS X 64-bit port *Solaris 10 support *Switch from maxima to Pynac for symbolics. The above goals were I think great motivation for sage-4.0, and really helped focus and drive development. So again, I don't think Solaris 10 support being a goal for 5.0 is at all unreasonable. And now are chances of success are even high, due to all the hard work everybody has done. One worry about that laundry list being the goals for 5.0 is that it is too complicated and hard to remember. It's pretty cool that I can so easily just remember what the goal list was for sage-4.0. It would be nice if the 5.0 goal list was similarly comprehensible. How about: 1. 85% doctest coverage score 2. Official Solaris 10 support 3. Build with SAGE_CHECK=yes works on all platforms, *and* every package has at least some spkg-check in it, that checks something. 4. Greatly improve the Sage startup time. This needs to be made precise, e.g., the following should take < 0.5 seconds when run repeatedly from a scratch disk on sage.math: time sage -c "print factor(2010)" Right now it takes over 1.5 seconds every time. wst...@sage:~$ time sage -c "print factor(2010)" 2 * 3 * 5 * 67 real0m1.535s user0m1.140s sys 0m0.460s The above spreads the goals around nicely. 1 is about user documentation and better library testing. 2 is about better platform support. 3 is about better quality in our build system, and will pay many rewards later as we upgrade packages (finding bugs as early as possible in the build cycle), and 4 is something every single user will really notice. Note that 4 is probably quite a lot of work all over the place, and its difficulty is not to be underestimated. Thoughts about goals 1-4 above? Are they something you could remember a year from now? William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] summary of doctest failures in Mandriva cooker sagemath 4.3.3 package
2010/3/2 François Bissey :
>> Hi,
>>
>> Some are known problems due to using different versions of certain
>> packages, example:
>>
>> -%<-
>> File "/usr/share/sage/devel/doc/en/numerical_sage/cvxopt.rst", line 57:
>> sage: print(A)
>> Expected:
>> SIZE: (5,5)
>> (0, 0) 2.e+00
>> (1, 0) 3.e+00
>> (0, 1) 3.e+00
>> (2, 1) -1.e+00
>> (4, 1) 4.e+00
>> (1, 2) 4.e+00
>> (2, 2) -3.e+00
>> (3, 2) 1.e+00
>> (4, 2) 2.e+00
>> (2, 3) 2.e+00
>> (1, 4) 6.e+00
>> (4, 4) 1.e+00
>> Got:
>> [ 2.00e+00 3.00e+00 0 0 0 ]
>> [ 3.00e+00 0 4.00e+00 0 6.00e+00]
>> [ 0 -1.00e+00 -3.00e+00 2.00e+00 0 ]
>> [ 0 0 1.00e+00 0 0 ]
>> [ 0 4.00e+00 2.00e+00 0 1.00e+00]
>>
>> -%<-
>> or
>> -%<-
>> File "/usr/share/sage/devel/sage/sage/libs/pari/gen.pyx", line 6844:
>> sage: nf.nfroots(y^2 + 2)
>> Expected:
>> [-zz, zz]
>> Got:
>> [Mod(-zz, zz^2 + 2), Mod(zz, zz^2 + 2)]
>> -%<-
>>
>> Some are due to system wide installation, example:
>> -%<-
>> File "/usr/share/sage/devel/doc/common/builder.py", line 157:
>> sage: b = builder.DocBuilder('tutorial')
>> Exception raised:
>> Traceback (most recent call last):
>> File "/usr/share/sage/local/bin/ncadoctest.py", line 1231, in
>> run_one_test self.run_one_example(test, example, filename, compileflags)
>> File "/usr/share/sage/local/bin/sagedoctest.py", line 38, in
>> run_one_example
>> OrigDocTestRunner.run_one_example(self, test, example,
>> filename, compileflags)
>> File "/usr/share/sage/local/bin/ncadoctest.py", line 1172, in
>> run_one_example
>> compileflags, 1) in test.globs
>> File "", line 1, in
>> b = builder.DocBuilder('tutorial')###line 157:
>> sage: b = builder.DocBuilder('tutorial')
>> File "/usr/share/sage/devel/doc/common/builder.py", line 145, in
>> __init__ mkdir(os.path.join(self.dir, "static"))
>> File "/usr/share/sage/devel/doc/common/builder.py", line 55, in mkdir
>> os.makedirs(path)
>> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
>> mkdir(name, mode)
>> OSError: [Errno 13] Permission denied:
>> '/usr/share/sage/devel/doc/en/tutorial/static'
>> -%<-
>> or
>> -%<-
>> File "/usr/share/sage/devel/doc/en/constructions/plotting.rst", line 209:
>> sage: maxima.eval('load("plotdf");')
>> Expected:
>> '".../local/share/maxima/.../share/dynamics/plotdf.lisp"'
>> Got:
>> '"/usr/share/maxima/5.20.1/share/dynamics/plotdf.lisp"'
>> -%<-
>>
>> Some are somewhat strange, but I believe they are due to using some
>> package with different version, or missing some patch. Examples:
>> -%<-
>> File "/usr/share/sage/devel/sage/sage/matrix/matrix1.pyx", line 448:
>> sage: sorted(numpy.typecodes.items())
>> Expected:
>> [('All', '?bhilqpBHILQPfdgFDGSUVO'), ('AllFloat', 'fdgFDG'),
>> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
>> 'FDG'), ('Float', 'fdg'), ('Integer', 'bhilqp'), ('UnsignedInteger',
>> 'BHILQP')]
>> Got:
>> [('All', '?bhilqpBHILQPfdgFDGSUVOMm'), ('AllFloat', 'fdgFDG'),
>> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
>> 'FDG'), ('Datetime', 'Mm'), ('Float', 'fdg'), ('Integer', 'bhilqp'),
>> ('UnsignedInteger', 'BHILQP')]
>> -%<-
>> and
>> -%<-
>> File "/usr/share/sage/devel/sage/sage/sets/set.py", line 312:
>> sage: Primes() < Set(QQ)
>> Expected:
>> True
>> Got:
>> False
>> -%<-
>> and
>> -%<
>> File "/usr/share/sage/devel/sage/sage/finance/time_series.pyx", line 1505:
>> sage: finance.TimeSeries([z.hurst_exponent() for z in y]).mean()
>> Expected:
>> 0.579848225779347...
>> Got:
>> 0.5798482257793468
>> -%<-
>>
>> Some details that may be useful:
>> 1) I am using a custom cPickle.so and pickle.py in $PYTHONPATH due to
>> sage's patches
>> 2) I am using a custom sets.py in $PYHTONPATH that doesn't generate a
>> DeprecationWarning,
>> otherwise, the number of false positive positives due to
>> Deprecation warnings is too high...
>> 3) I am using gmp5 instead of mpir (needs only a one line patch so far...)
>> 4) I am using a newer givaro and python-mpmath, because other packages
>> resolved to
>> update those packages :-) So, I built a givaro patch, and used
>> mpmath patches from trac
>>
>>
>> I also found out that clisp maxima backend has a serious issue, in
>> that, for example it hangs
>> with the command:
>> sage: maxima.eval('x==x')
>> (as in sage/interfaces/maxima.py eval_line doctest)
>> and, probably because of the timeout and process kill, it causes some
>> other weird
>> doctest failures like:
>> -%<-
>> File "/usr/share/sage/devel/sage/sage/symbolic/relation.py", line 560:
>> sage: solve([cos(x)*sin(x) == 1/2, x+y == 0],x,y)
>> Expected:
>> [[x == 1/4*pi + pi*
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
On Tue, Mar 2, 2010 at 3:37 PM, David Kirkby wrote: > On 2 March 2010 14:50, William Stein wrote: >> On Tue, Mar 2, 2010 at 6:43 AM, Minh Nguyen wrote: > >> What you wrote is already amazingly crystal clear and of course >> matches exactly with what I do anyways (which is probably what you >> were recording there). I just didn't know about it, and clearly David >> didn't either. >> >> Minh -- thanks!! >> >> -- William > > Agreed. > > The only point I thought might be a little troublesome is the use of > the 'patch' command. There is says the preferred method is to use 'cp' > rather than 'patch', but does not totally rule out use of 'patch'. > (There is even an example of its use).I think you said recently > 'patch' must never be used. The page also says the Solaris patch > program can't handle unified diffs, which is not true, but it is > certainly true that one can generate diff's on Linux systems which the > Sun 'patch' command can't handle. > > I've never myself met a Unix system which does not have the 'patch' > command. It is part of the POSIX standard. If it's agreed that 'patch' > must never be used, then perhaps that needs stating a bit more clearly > on that page. It's come up many times, and I personally am against the explicit use of 'patch' in spkg-install. It *was* used recently by somebody for gfan, which made upgrading *break* for an entire Sage release (which was really bad, imho). I just think using patch explicitly tends to be error prone, and is definitely not necessary. -- William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: fractals in sage
On Tue, Mar 2, 2010 at 2:25 PM, Harald Schilly wrote: > On Mar 2, 8:15 pm, William Stein wrote: >> A student of mine is going to add to sage the capability of plotting >> lots and lots of fractals easily. > > That sounds exiting, are there also plans to implement "discrete" > fractals? (combinat.WordMorphisms and word-paths and things like > that?) > > http://www.sagemath.org/doc/reference/sage/combinat/words/paths.html > http://alexis.monnerot-dumaine.neuf.fr/articles/fibonacci%20fractal.pdf > > Disclaimer: I'm not sure if this is really related, just something I > had in the back of my head ;) Yes, sure. There really isn't so much in the way of *big plans* here. We just want fractals.[tab] to be a way to draw tons of cool pictures easily. It'll be a lot of fun. William > > Another thing that comes to my mind are images like that one: > http://serendip.brynmawr.edu/bookshelves/NKS0032.gif > > h > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
Minh Nguyen wrote: Hi David, On Wed, Mar 3, 2010 at 12:17 PM, Dr. David Kirkby wrote: 'qimport' reports no issues, but 'qfinish -a' tells me there are no patches applied. I've verified that indeed the patches are not applied. Correction: (1) hg qimport /URL/or/patch/to/patch.path # get/download the patch (2) hg qpush # really apply the patch Repeat (1) and (2) as often as necessary. After that, do this $ hg qapplied This should return the list of patches you have applied using "hg qpush". Once you are ready, do $ hg qfinish -a Apology for missing the "hg qpush" part. Thank you. That has worked (I've put it below for the record). Now I can repackage it, start the build and go to bed. PS, if you want to check anything, feel free to use: http://redstart.drkirkby.co.uk:8000 It is not fast (only 900 MHz), has only 2 GB RAM, and a slowish network connection, but all patches are included, with the exception of the numerical noise ones, as I forgot to add them to that build. Dave kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ rm -rf sage-4.3.3 kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ tar xfj sage-4.3.3.spkg kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ cd sage-4.3.3 kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../numerical-noise-on-SPARC.patch adding numerical-noise-on-SPARC.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qpush applying numerical-noise-on-SPARC.patch now at: numerical-noise-on-SPARC.patch kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../8374-numerical-noise.patch adding 8374-numerical-noise.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qpush applying 8374-numerical-noise.patch now at: 8374-numerical-noise.patch kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../top-to-prstat.patch adding top-to-prstat.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qpush applying top-to-prstat.patch now at: top-to-prstat.patch kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qapplied numerical-noise-on-SPARC.patch 8374-numerical-noise.patch top-to-prstat.patch kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qfinish -a -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Ugly printing of basic maths
Mike Hansen wrote: Hello, I've looked into it, and it's just and issue with the notebook stripping the initial spaces in the output string. For example, do for i in range(4): print maxima(1-sin(x)^2) and only the first output will be messed up. I would try upgrading the notebook to a newer version (since the one on t2 is old -- 0.4.8). This problem does not occur on sagenb, and I would be surprised if it were platform-specific. --Mike Thank you. I should have tried it earlier, but when I look at it on my own machine, where Sage is based on 4.3.3, but has a ton of patches, the printing looks ok http://redstart.drkirkby.co.uk:8000/home/pub/1/ (That machine is only 900 MHz, though should still be quicker than 't2' but with only 2 GB RAM, don't expect any miracles if you play with it) As soon as we have a release which builds properly on Solaris, I'll update the Sage server on 't2'. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] fractals in sage
William Stein wrote: Hi, A student of mine is going to add to sage the capability of plotting lots and lots of fractals easily. E.g., sage: fractals.[tab] lots of stuff sage: fractals.julia([params]).show(figsize=10) [up pops a julia set] The trac ticket where this starts is here: http://trac.sagemath.org/sage_trac/ticket/8423 This isn't going to be some complicated fancy object oriented abstract dynamical metaclassed framework. It's just a bunch of functions to draw fractals. And at first it could even be slow (though obviously some cython master will probably clear through it at some point and make everything really fast, without having to change or write any docs). I can imagine that most of the files will consist of examples and docstrings rather than actual code, too. The point of this email: if you like plotting fractals, and have some potentially useful code to contribute, then please post to this thread or http://trac.sagemath.org/sage_trac/ticket/8423 with them.Or if you really want to help, then do so. -- William Those sorts of images could be good for your calender. I recall many years ago programming the 80387 maths coprocessor chip at the assembly level to generate the fastest Mandlebrot set I could. If I recall correctly, it ran at 25 MHz, which I think was the fastest any 80386/80376 chip run at. There is the open-source 'fractint' program which does the same sort of thing, but in integer maths, which is obviously quicker, though the floating point processors now are a lot better than they used to be. I recall computing tables of sin() and cos() for Monte Carlo simulations, then using a lookup rather than compute the sines and cosines each time, as it was too slow. Now, you are better to just call sin or cos in an FPU, rather than look them up in a table. I'm giving my age away a bit here! Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
Hi David, On Wed, Mar 3, 2010 at 12:17 PM, Dr. David Kirkby wrote: > 'qimport' reports no issues, but 'qfinish -a' tells me there are no patches > applied. I've verified that indeed the patches are not applied. Correction: (1) hg qimport /URL/or/patch/to/patch.path # get/download the patch (2) hg qpush # really apply the patch Repeat (1) and (2) as often as necessary. After that, do this $ hg qapplied This should return the list of patches you have applied using "hg qpush". Once you are ready, do $ hg qfinish -a Apology for missing the "hg qpush" part. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
Minh Nguyen wrote: Hi David, On Wed, Mar 3, 2010 at 7:03 AM, Dr. David Kirkby wrote: How can I apply those patches before starting to build Sage? At the point the tar file is extracted, I've no 'mercurial' package built, but I do have 'hg' installed on 't2'. Here, I assume you want to use the system-wide Mercurial installation on t2.math and that you have configured Mercurial to use the queues extension. In a Sage source tarball, the Sage library is wrapped up as the package SAGE_ROOT/spkg/standard/sage-x.y.z.spkg Uncompress that bzip2 compressed tarball to get a directory named SAGE_ROOT/spkg/standard/sage-x.y.z/ Now delete SAGE_ROOT/spkg/standard/sage-x.y.z.spkg Next, patch the Sage library as if it had been built and found under SAGE_ROOT/devel: $ cd SAGE_ROOT/spkg/standard/sage-x.y.z/ $ hg qimport /URL/or/path/to/patch.patch $ Once you're happy that you have applied all necessary patches, wrap up the patched Sage library: $ pwd SAGE_ROOT/spkg/standard/sage-x.y.z/ $ hg qfinish -a $ cd .. And see this section http://www.sagemath.org/doc/developer/patching_spkgs.html#overview-of-patching-spkg-s This is not working for me. I've put the patches in /scratch/kirkby/sage-4.3.3/spkg/standard 'qimport' reports no issues, but 'qfinish -a' tells me there are no patches applied. I've verified that indeed the patches are not applied. kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ rm -rf sage-4.3.3 kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ tar xfj sage-4.3.3.spkg kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard] $ cd sage-4.3.3 kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../top-to-prstat.patch adding top-to-prstat.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../8374-numerical-noise.patch adding 8374-numerical-noise.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qimport ../numerical-noise-on-SPARC.patch adding numerical-noise-on-SPARC.patch to series file kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ hg qfinish -a no patches applied kir...@t2:[/scratch/kirkby/sage-4.3.3/spkg/standard/sage-4.3.3] $ Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Ugly printing of basic maths
Hello, I've looked into it, and it's just and issue with the notebook stripping the initial spaces in the output string. For example, do for i in range(4): print maxima(1-sin(x)^2) and only the first output will be messed up. I would try upgrading the notebook to a newer version (since the one on t2 is old -- 0.4.8). This problem does not occur on sagenb, and I would be surprised if it were platform-specific. --Mike -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] summary of doctest failures in Mandriva cooker sagemath 4.3.3 package
> Hi,
>
> Some are known problems due to using different versions of certain
> packages, example:
>
> -%<-
> File "/usr/share/sage/devel/doc/en/numerical_sage/cvxopt.rst", line 57:
> sage: print(A)
> Expected:
> SIZE: (5,5)
> (0, 0) 2.e+00
> (1, 0) 3.e+00
> (0, 1) 3.e+00
> (2, 1) -1.e+00
> (4, 1) 4.e+00
> (1, 2) 4.e+00
> (2, 2) -3.e+00
> (3, 2) 1.e+00
> (4, 2) 2.e+00
> (2, 3) 2.e+00
> (1, 4) 6.e+00
> (4, 4) 1.e+00
> Got:
> [ 2.00e+00 3.00e+00 0 0 0]
> [ 3.00e+00 0 4.00e+00 0 6.00e+00]
> [0 -1.00e+00 -3.00e+00 2.00e+00 0]
> [0 0 1.00e+00 0 0]
> [0 4.00e+00 2.00e+00 0 1.00e+00]
>
> -%<-
> or
> -%<-
> File "/usr/share/sage/devel/sage/sage/libs/pari/gen.pyx", line 6844:
> sage: nf.nfroots(y^2 + 2)
> Expected:
> [-zz, zz]
> Got:
> [Mod(-zz, zz^2 + 2), Mod(zz, zz^2 + 2)]
> -%<-
>
> Some are due to system wide installation, example:
> -%<-
> File "/usr/share/sage/devel/doc/common/builder.py", line 157:
> sage: b = builder.DocBuilder('tutorial')
> Exception raised:
> Traceback (most recent call last):
> File "/usr/share/sage/local/bin/ncadoctest.py", line 1231, in
> run_one_test self.run_one_example(test, example, filename, compileflags)
> File "/usr/share/sage/local/bin/sagedoctest.py", line 38, in
> run_one_example
> OrigDocTestRunner.run_one_example(self, test, example,
> filename, compileflags)
> File "/usr/share/sage/local/bin/ncadoctest.py", line 1172, in
> run_one_example
> compileflags, 1) in test.globs
> File "", line 1, in
> b = builder.DocBuilder('tutorial')###line 157:
> sage: b = builder.DocBuilder('tutorial')
> File "/usr/share/sage/devel/doc/common/builder.py", line 145, in
> __init__ mkdir(os.path.join(self.dir, "static"))
> File "/usr/share/sage/devel/doc/common/builder.py", line 55, in mkdir
> os.makedirs(path)
> File "/usr/lib64/python2.6/os.py", line 157, in makedirs
> mkdir(name, mode)
> OSError: [Errno 13] Permission denied:
> '/usr/share/sage/devel/doc/en/tutorial/static'
> -%<-
> or
> -%<-
> File "/usr/share/sage/devel/doc/en/constructions/plotting.rst", line 209:
> sage: maxima.eval('load("plotdf");')
> Expected:
> '".../local/share/maxima/.../share/dynamics/plotdf.lisp"'
> Got:
> '"/usr/share/maxima/5.20.1/share/dynamics/plotdf.lisp"'
> -%<-
>
> Some are somewhat strange, but I believe they are due to using some
> package with different version, or missing some patch. Examples:
> -%<-
> File "/usr/share/sage/devel/sage/sage/matrix/matrix1.pyx", line 448:
> sage: sorted(numpy.typecodes.items())
> Expected:
> [('All', '?bhilqpBHILQPfdgFDGSUVO'), ('AllFloat', 'fdgFDG'),
> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
> 'FDG'), ('Float', 'fdg'), ('Integer', 'bhilqp'), ('UnsignedInteger',
> 'BHILQP')]
> Got:
> [('All', '?bhilqpBHILQPfdgFDGSUVOMm'), ('AllFloat', 'fdgFDG'),
> ('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
> 'FDG'), ('Datetime', 'Mm'), ('Float', 'fdg'), ('Integer', 'bhilqp'),
> ('UnsignedInteger', 'BHILQP')]
> -%<-
> and
> -%<-
> File "/usr/share/sage/devel/sage/sage/sets/set.py", line 312:
> sage: Primes() < Set(QQ)
> Expected:
> True
> Got:
> False
> -%<-
> and
> -%<
> File "/usr/share/sage/devel/sage/sage/finance/time_series.pyx", line 1505:
> sage: finance.TimeSeries([z.hurst_exponent() for z in y]).mean()
> Expected:
> 0.579848225779347...
> Got:
> 0.5798482257793468
> -%<-
>
> Some details that may be useful:
> 1) I am using a custom cPickle.so and pickle.py in $PYTHONPATH due to
> sage's patches
> 2) I am using a custom sets.py in $PYHTONPATH that doesn't generate a
> DeprecationWarning,
> otherwise, the number of false positive positives due to
> Deprecation warnings is too high...
> 3) I am using gmp5 instead of mpir (needs only a one line patch so far...)
> 4) I am using a newer givaro and python-mpmath, because other packages
> resolved to
> update those packages :-) So, I built a givaro patch, and used
> mpmath patches from trac
>
>
> I also found out that clisp maxima backend has a serious issue, in
> that, for example it hangs
> with the command:
> sage: maxima.eval('x==x')
> (as in sage/interfaces/maxima.py eval_line doctest)
> and, probably because of the timeout and process kill, it causes some
> other weird
> doctest failures like:
> -%<-
> File "/usr/share/sage/devel/sage/sage/symbolic/relation.py", line 560:
> sage: solve([cos(x)*sin(x) == 1/2, x+y == 0],x,y)
> Expected:
> [[x == 1/4*pi + pi*z38, y == -1/4*pi - pi*z38]]
> Got:
> [[x == 1/4*pi + pi*z39, y == -1/4*pi - pi*z39]]
> -%<-
>
> I reported the clisp problem upstream; last response:
>
[sage-devel] Ugly printing of basic maths
Taking one of the examples from the Sage tutorial, I see some pretty ugly printing when trying to use the "print" command from Maxima. Here is a screen shot as I see it in my browser. http://boxen.math.washington.edu/home/kirkby/ugly-maths.png Here is the published web page where I grabbed the image from. http://t2nb.math.washington.edu:8000/home/pub/7/ Is this likely to be 1) Solaris specific ? 2) Lack of Latex ? 3) Lack of jsmath ? 4) My browser (Firefox 3.1b3 on OpenSolaris) 5) A bug that affects everyone (I somewhat doubt that) Whatever the reason that allows this to occur, I think it needs fixing. If it's a lack of Latex, then I'd suggest making latex a perquisite, or including it with Sage. If it's a lack of jsmath, then this should be checked for and signaled. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: ALL doctests pass on Solaris !!!
On 2 March 2010 23:25, Minh Nguyen wrote: > On Wed, Mar 3, 2010 at 10:23 AM, David Kirkby wrote: >> I'm not sure if that would be called 'middle endian' or not! > > It should be called the "median" :-) > > -- > Regards > Minh Van Nguyen Only a mathematician could think of that ! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
On 2 March 2010 14:50, William Stein wrote: > On Tue, Mar 2, 2010 at 6:43 AM, Minh Nguyen wrote: > What you wrote is already amazingly crystal clear and of course > matches exactly with what I do anyways (which is probably what you > were recording there). I just didn't know about it, and clearly David > didn't either. > > Minh -- thanks!! > > -- William Agreed. The only point I thought might be a little troublesome is the use of the 'patch' command. There is says the preferred method is to use 'cp' rather than 'patch', but does not totally rule out use of 'patch'. (There is even an example of its use).I think you said recently 'patch' must never be used. The page also says the Solaris patch program can't handle unified diffs, which is not true, but it is certainly true that one can generate diff's on Linux systems which the Sun 'patch' command can't handle. I've never myself met a Unix system which does not have the 'patch' command. It is part of the POSIX standard. If it's agreed that 'patch' must never be used, then perhaps that needs stating a bit more clearly on that page. But the bit about my question is crystal clear. Minh does a great job of documentation. He is undoubtedly a huge asset to Sage. When there are only a few people working on something, the need for such good documentation is less, but for something where there are 200 or whatever developers, Minh's attention to detail is very good. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: ALL doctests pass on Solaris !!!
On Wed, Mar 3, 2010 at 10:23 AM, David Kirkby wrote: > I'm not sure if that would be called 'middle endian' or not! It should be called the "median" :-) -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: ALL doctests pass on Solaris !!!
On 2 March 2010 19:44, Peter Jeremy wrote: > On 2010-Mar-01 14:42:38 +, "Dr. David Kirkby" > wrote: >>I've just succeeded in getting all doctests to pass on Solaris. > > Firstly, congratulations on this. > > On 2010-Mar-01 19:09:54 +, "Dr. David Kirkby" > wrote: >>There should be minor differences between Solaris 10 on SPARC and >>Solaris 10 on x86. > > Incorrectly #ifdef'd assembly code might be irritating but at least the > assembler will choke on it. More subtle problems will be code that > assumes Sun/Solaris means big-endian. True. A lot of the code in Sage is quite old, so assumptions are made that are not true today. The fact that Solaris does not necessarily mean big-endian might be a problem. Hopefully any such problems will be picked up in tests though - it should be fairly evident at run-time if that is wrong. FWIW, I used to work on a Burker NMR spectrometer, which was 24-bit. I can't recall whether it was the most significant or the least significant byte that was in the middle, but it was one of them! I assume Bruker used to use 16-bits, then switched to 24-bits, so to maintain some compatibility one or the other bytes had to be in the middle. I'm not sure if that would be called 'middle endian' or not! I doubt autoconf could even check for that sort of mix. >>There is quite a difference from Solaris 10 to Open Solaris. The >>latter is aimed much more for desktop use. > > I've found that OpenSolaris feels a lot more like Linux than Solaris does. Yes agree. OpenSolaris is a radical change from Solaris 10. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] summary of doctest failures in Mandriva cooker sagemath 4.3.3 package
Hi,
Some are known problems due to using different versions of certain
packages, example:
-%<-
File "/usr/share/sage/devel/doc/en/numerical_sage/cvxopt.rst", line 57:
sage: print(A)
Expected:
SIZE: (5,5)
(0, 0) 2.e+00
(1, 0) 3.e+00
(0, 1) 3.e+00
(2, 1) -1.e+00
(4, 1) 4.e+00
(1, 2) 4.e+00
(2, 2) -3.e+00
(3, 2) 1.e+00
(4, 2) 2.e+00
(2, 3) 2.e+00
(1, 4) 6.e+00
(4, 4) 1.e+00
Got:
[ 2.00e+00 3.00e+00 0 0 0]
[ 3.00e+00 0 4.00e+00 0 6.00e+00]
[0 -1.00e+00 -3.00e+00 2.00e+00 0]
[0 0 1.00e+00 0 0]
[0 4.00e+00 2.00e+00 0 1.00e+00]
-%<-
or
-%<-
File "/usr/share/sage/devel/sage/sage/libs/pari/gen.pyx", line 6844:
sage: nf.nfroots(y^2 + 2)
Expected:
[-zz, zz]
Got:
[Mod(-zz, zz^2 + 2), Mod(zz, zz^2 + 2)]
-%<-
Some are due to system wide installation, example:
-%<-
File "/usr/share/sage/devel/doc/common/builder.py", line 157:
sage: b = builder.DocBuilder('tutorial')
Exception raised:
Traceback (most recent call last):
File "/usr/share/sage/local/bin/ncadoctest.py", line 1231, in run_one_test
self.run_one_example(test, example, filename, compileflags)
File "/usr/share/sage/local/bin/sagedoctest.py", line 38, in
run_one_example
OrigDocTestRunner.run_one_example(self, test, example,
filename, compileflags)
File "/usr/share/sage/local/bin/ncadoctest.py", line 1172, in
run_one_example
compileflags, 1) in test.globs
File "", line 1, in
b = builder.DocBuilder('tutorial')###line 157:
sage: b = builder.DocBuilder('tutorial')
File "/usr/share/sage/devel/doc/common/builder.py", line 145, in __init__
mkdir(os.path.join(self.dir, "static"))
File "/usr/share/sage/devel/doc/common/builder.py", line 55, in mkdir
os.makedirs(path)
File "/usr/lib64/python2.6/os.py", line 157, in makedirs
mkdir(name, mode)
OSError: [Errno 13] Permission denied:
'/usr/share/sage/devel/doc/en/tutorial/static'
-%<-
or
-%<-
File "/usr/share/sage/devel/doc/en/constructions/plotting.rst", line 209:
sage: maxima.eval('load("plotdf");')
Expected:
'".../local/share/maxima/.../share/dynamics/plotdf.lisp"'
Got:
'"/usr/share/maxima/5.20.1/share/dynamics/plotdf.lisp"'
-%<-
Some are somewhat strange, but I believe they are due to using some package
with different version, or missing some patch. Examples:
-%<-
File "/usr/share/sage/devel/sage/sage/matrix/matrix1.pyx", line 448:
sage: sorted(numpy.typecodes.items())
Expected:
[('All', '?bhilqpBHILQPfdgFDGSUVO'), ('AllFloat', 'fdgFDG'),
('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
'FDG'), ('Float', 'fdg'), ('Integer', 'bhilqp'), ('UnsignedInteger',
'BHILQP')]
Got:
[('All', '?bhilqpBHILQPfdgFDGSUVOMm'), ('AllFloat', 'fdgFDG'),
('AllInteger', 'bBhHiIlLqQpP'), ('Character', 'c'), ('Complex',
'FDG'), ('Datetime', 'Mm'), ('Float', 'fdg'), ('Integer', 'bhilqp'),
('UnsignedInteger', 'BHILQP')]
-%<-
and
-%<-
File "/usr/share/sage/devel/sage/sage/sets/set.py", line 312:
sage: Primes() < Set(QQ)
Expected:
True
Got:
False
-%<-
and
-%<
File "/usr/share/sage/devel/sage/sage/finance/time_series.pyx", line 1505:
sage: finance.TimeSeries([z.hurst_exponent() for z in y]).mean()
Expected:
0.579848225779347...
Got:
0.5798482257793468
-%<-
Some details that may be useful:
1) I am using a custom cPickle.so and pickle.py in $PYTHONPATH due to
sage's patches
2) I am using a custom sets.py in $PYHTONPATH that doesn't generate a
DeprecationWarning,
otherwise, the number of false positive positives due to
Deprecation warnings is too high...
3) I am using gmp5 instead of mpir (needs only a one line patch so far...)
4) I am using a newer givaro and python-mpmath, because other packages
resolved to
update those packages :-) So, I built a givaro patch, and used
mpmath patches from trac
I also found out that clisp maxima backend has a serious issue, in
that, for example it hangs
with the command:
sage: maxima.eval('x==x')
(as in sage/interfaces/maxima.py eval_line doctest)
and, probably because of the timeout and process kill, it causes some
other weird
doctest failures like:
-%<-
File "/usr/share/sage/devel/sage/sage/symbolic/relation.py", line 560:
sage: solve([cos(x)*sin(x) == 1/2, x+y == 0],x,y)
Expected:
[[x == 1/4*pi + pi*z38, y == -1/4*pi - pi*z38]]
Got:
[[x == 1/4*pi + pi*z39, y == -1/4*pi - pi*z39]]
-%<-
I reported the clisp problem upstream; last response:
https://sourceforge.net/mailarchive/forum.php?thread_name=4B8D57D2.4080002%40gnu.org&forum_name=clisp-devel
but the tests work with other lisp backends (only did not yet test gcl
from the available backends in Mandriva package)
Paulo
--
To post to this group, send
Re: [sage-devel] How do I add Mercurial patches before Sage built?
On 2 March 2010 20:17, Robert Bradshaw wrote: > On Mar 2, 2010, at 12:03 PM, Dr. David Kirkby wrote: > >> I want to build Sage on 't2', and know I need to apply 3 Mercurial patches >> to the Sage library - two fix numerical noise issues, the other replaces >> 'top' by 'prstat'). >> >> http://trac.sagemath.org/sage_trac/ticket/8374 >> http://trac.sagemath.org/sage_trac/ticket/8375 >> http://trac.sagemath.org/sage_trac/ticket/8391 >> (all 3 awaiting review by the way). >> >> How can I apply those patches before starting to build Sage? At the point >> the tar file is extracted, I've no 'mercurial' package built, but I do have >> 'hg' installed on 't2'. There is no 'devel' directory. > > When you have an install of sage, there's a devel directory right under sage > root. I don't think it's there until you build sage. The developers guide > should be enough to go from there. The point is though, if you know you need certain patches before Sage will build, one might as well put them in now. > It should be possible to unpack the spkg, cd into it, run "hg import > /path/to/patch" then re-tar the spkg, and then run a make testlong, but I've > never done that. I find it much easier to patch in place. (Then again, I > want to try it out, not just run tests...) > > - Robert I want to try it too, but I suspect the build will finish in the middle of the night, so being able to run the tests immediately after its built is useful. I think this document I published http://t2nb.math.washington.edu:8000/home/pub/7/ shows that even though that particular bit of the documentation passes the test, the output viewed in a browser is rubbish. I'd love to see some way of actually testing what the browser will display. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
On 2 March 2010 20:32, Minh Nguyen wrote: > Hi David, > > On Wed, Mar 3, 2010 at 7:03 AM, Dr. David Kirkby > wrote: > > > >> How can I apply those patches before starting to build Sage? At the point >> the tar file is extracted, I've no 'mercurial' package built, but I do have >> 'hg' installed on 't2'. > > Here, I assume you want to use the system-wide Mercurial installation > on t2.math and that you have configured Mercurial to use the queues > extension. Yes, I've done that. > In a Sage source tarball, the Sage library is wrapped up > as the package > > SAGE_ROOT/spkg/standard/sage-x.y.z.spkg > > Uncompress that bzip2 compressed tarball to get a directory named > > SAGE_ROOT/spkg/standard/sage-x.y.z/ > > Now delete > > SAGE_ROOT/spkg/standard/sage-x.y.z.spkg I must admit, I always omit that step, as it will get overwritten later, so there does not seem a lot of point in actually removing it first. > Next, patch the Sage library as if it had been built and found under > SAGE_ROOT/devel: > > $ cd SAGE_ROOT/spkg/standard/sage-x.y.z/ > $ hg qimport /URL/or/path/to/patch.patch > $ > > Once you're happy that you have applied all necessary patches, wrap up > the patched Sage library: > > $ pwd > SAGE_ROOT/spkg/standard/sage-x.y.z/ > $ hg qfinish -a > $ cd .. > > And see this section > > http://www.sagemath.org/doc/developer/patching_spkgs.html#overview-of-patching-spkg-s > > of the Developer's Guide on find out how to package the newly patched > Sage library, i.e. the directory > > SAGE_ROOT/spkg/standard/sage-x.y.z/ > > Now you should have > > SAGE_ROOT/spkg/standard/sage-x.y.z.spkg > > so you could delete > > SAGE_ROOT/spkg/standard/sage-x.y.z/ > > Finally, proceed to build Sage from source. > > -- > Regards > Minh Van Nguyen Thank you Minh. That was what I was looking for. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
On 2 March 2010 19:01, Robert Bradshaw wrote: > Just a thought, would knocking out this important list of bugs be a good > goal for Sage 5.0? > > - Robert It is certainly unusual the way Sage version numbers go. In just about any other software project Assuming the version is of the form X.Y.Z, X is incremented if there is major new functionality Y is incremented if there is added, but less major functionality Z is incremented when bug fixes are made. I think someone might be a bit disappointed if they update Sage to 5.0.0, without seeing some tangible new functionality. (I did think of requesting it was called 5.0 when the Solaris port was finished, but guess that would not be too popular!) Of course, software called be called by the names of birds, plants, big cats (as Apple do), or anything else you choose. But the way most software numbering works is that X in incremented when there is significant new functionality added, and Z incremented for bug fixes. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: fractals in sage
On Mar 2, 8:15 pm, William Stein wrote: > A student of mine is going to add to sage the capability of plotting > lots and lots of fractals easily. That sounds exiting, are there also plans to implement "discrete" fractals? (combinat.WordMorphisms and word-paths and things like that?) http://www.sagemath.org/doc/reference/sage/combinat/words/paths.html http://alexis.monnerot-dumaine.neuf.fr/articles/fibonacci%20fractal.pdf Disclaimer: I'm not sure if this is really related, just something I had in the back of my head ;) Another thing that comes to my mind are images like that one: http://serendip.brynmawr.edu/bookshelves/NKS0032.gif h -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-combinat-devel] Re: [sage-devel] fractals in sage
2010/3/2 Florent Hivert : > Hi William, > >> A student of mine is going to add to sage the capability of plotting >> lots and lots of fractals easily. E.g., > [...] >> The point of this email: if you like plotting fractals, and have some >> potentially useful code to contribute, then please post to this thread >> or http://trac.sagemath.org/sage_trac/ticket/8423 with them. Or if >> you really want to help, then do so. > > I don't remember who he was, but at the end of sage days 20, one guys made a > short demo about plotting some Rauzy fractal. I don't know the precise > definition but I think it is related to numerations systems in a non integer > base (e.g. the golden number). I cc this mail to sage-combinat-devel where > someone certainly knows the precise guy. > > Cheers, > > Florent > > -- > You received this message because you are subscribed to the Google Groups > "sage-combinat-devel" group. > To post to this group, send email to sage-combinat-de...@googlegroups.com. > To unsubscribe from this group, send email to > sage-combinat-devel+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sage-combinat-devel?hl=en. > Hi William, hi Florent, Perhaps Timo Jolivet (I show from him nice pictures during SAGE days 20) ? We planned with him and Stepan Starosta to implement two way of plotting Rauzy fractals in SAGE for tomorrow afternoon ! If everything goes well, there will be a ticket ready tomorrow evening (Paris time). I won't forget the shortcut fractals.RauzyFractal Cheers, Vincent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] fractals in sage
Hi William, > A student of mine is going to add to sage the capability of plotting > lots and lots of fractals easily. E.g., [...] > The point of this email: if you like plotting fractals, and have some > potentially useful code to contribute, then please post to this thread > or http://trac.sagemath.org/sage_trac/ticket/8423 with them.Or if > you really want to help, then do so. I don't remember who he was, but at the end of sage days 20, one guys made a short demo about plotting some Rauzy fractal. I don't know the precise definition but I think it is related to numerations systems in a non integer base (e.g. the golden number). I cc this mail to sage-combinat-devel where someone certainly knows the precise guy. Cheers, Florent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
How about that and 90% coverage? Or 85% if 90% is too ambitious. -Marshall On Mar 2, 1:01 pm, Robert Bradshaw wrote: > On Mar 1, 2010, at 4:26 AM, William Stein wrote: > > > > > Hi, > > > I've created this trac wiki page with a subset of the 10 most > > important current bug/issues in Sage, according to votes in this > > thread: > > >http://trac.sagemath.org/sage_trac/wiki/stab1 > > > These are all bugs/issues that many people care about. None are > > highly specialized. > > > So if anybody has some time to donate to working on Sage, and you want > > to make an impact that people will definitely appreciate, work on one > > of the bugs listed athttp://trac.sagemath.org/sage_trac/wiki/stab1 > > > After seeing the actual bugs, I no longer see the wisdom of making a > > specific release targeting them. The problem is that they are all > > potentially hard, and there is no telling when they will all be > > resolved. However, listing them all together and seeing that a lot of > > people care about them will help encourage people to work on them. > > Just a thought, would knocking out this important list of bugs be a > good goal for Sage 5.0? > > - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: fractals in sage
Cool, I will try to contribute to this. It might be summertime before I do much, although I couldn't resist adding a little to the ticket already. -Marshall On Mar 2, 1:15 pm, William Stein wrote: > Hi, > > A student of mine is going to add to sage the capability of plotting > lots and lots of fractals easily. E.g., > >sage: fractals.[tab] >lots of stuff > >sage: fractals.julia([params]).show(figsize=10) >[up pops a julia set] > > The trac ticket where this starts is > here:http://trac.sagemath.org/sage_trac/ticket/8423 > > This isn't going to be some complicated fancy object oriented > abstract dynamical metaclassed framework. It's just a bunch of > functions to draw fractals. And at first it could even be slow > (though obviously some cython master will probably clear through it at > some point and make everything really fast, without having to change > or write any docs). I can imagine that most of the files will consist > of examples and docstrings rather than actual code, too. > > The point of this email: if you like plotting fractals, and have some > potentially useful code to contribute, then please post to this thread > orhttp://trac.sagemath.org/sage_trac/ticket/8423with them.Or if > you really want to help, then do so. > > -- William > > -- > William Stein > Associate Professor of Mathematics > University of Washingtonhttp://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
Hi David, On Wed, Mar 3, 2010 at 7:03 AM, Dr. David Kirkby wrote: > How can I apply those patches before starting to build Sage? At the point > the tar file is extracted, I've no 'mercurial' package built, but I do have > 'hg' installed on 't2'. Here, I assume you want to use the system-wide Mercurial installation on t2.math and that you have configured Mercurial to use the queues extension. In a Sage source tarball, the Sage library is wrapped up as the package SAGE_ROOT/spkg/standard/sage-x.y.z.spkg Uncompress that bzip2 compressed tarball to get a directory named SAGE_ROOT/spkg/standard/sage-x.y.z/ Now delete SAGE_ROOT/spkg/standard/sage-x.y.z.spkg Next, patch the Sage library as if it had been built and found under SAGE_ROOT/devel: $ cd SAGE_ROOT/spkg/standard/sage-x.y.z/ $ hg qimport /URL/or/path/to/patch.patch $ Once you're happy that you have applied all necessary patches, wrap up the patched Sage library: $ pwd SAGE_ROOT/spkg/standard/sage-x.y.z/ $ hg qfinish -a $ cd .. And see this section http://www.sagemath.org/doc/developer/patching_spkgs.html#overview-of-patching-spkg-s of the Developer's Guide on find out how to package the newly patched Sage library, i.e. the directory SAGE_ROOT/spkg/standard/sage-x.y.z/ Now you should have SAGE_ROOT/spkg/standard/sage-x.y.z.spkg so you could delete SAGE_ROOT/spkg/standard/sage-x.y.z/ Finally, proceed to build Sage from source. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] How do I add Mercurial patches before Sage built?
On Mar 2, 2010, at 12:03 PM, Dr. David Kirkby wrote: I want to build Sage on 't2', and know I need to apply 3 Mercurial patches to the Sage library - two fix numerical noise issues, the other replaces 'top' by 'prstat'). http://trac.sagemath.org/sage_trac/ticket/8374 http://trac.sagemath.org/sage_trac/ticket/8375 http://trac.sagemath.org/sage_trac/ticket/8391 (all 3 awaiting review by the way). How can I apply those patches before starting to build Sage? At the point the tar file is extracted, I've no 'mercurial' package built, but I do have 'hg' installed on 't2'. There is no 'devel' directory. When you have an install of sage, there's a devel directory right under sage root. I don't think it's there until you build sage. The developers guide should be enough to go from there. I'd like to be able to apply the patches, type $ make testlong and go away and leave it to run. I tried extracting the file spkg/standard/sage-4.3.3.spkg, but could not work out how to apply the 3 Mercurial patches. It should be possible to unpack the spkg, cd into it, run "hg import / path/to/patch" then re-tar the spkg, and then run a make testlong, but I've never done that. I find it much easier to patch in place. (Then again, I want to try it out, not just run tests...) - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] How do I add Mercurial patches before Sage built?
I want to build Sage on 't2', and know I need to apply 3 Mercurial patches to the Sage library - two fix numerical noise issues, the other replaces 'top' by 'prstat'). http://trac.sagemath.org/sage_trac/ticket/8374 http://trac.sagemath.org/sage_trac/ticket/8375 http://trac.sagemath.org/sage_trac/ticket/8391 (all 3 awaiting review by the way). How can I apply those patches before starting to build Sage? At the point the tar file is extracted, I've no 'mercurial' package built, but I do have 'hg' installed on 't2'. There is no 'devel' directory. I'd like to be able to apply the patches, type $ make testlong and go away and leave it to run. I tried extracting the file spkg/standard/sage-4.3.3.spkg, but could not work out how to apply the 3 Mercurial patches. One day I'll get the hang of Mercurial !! Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] proposal to remove dsage from sage
Dag Sverre Seljebotn wrote: > - For running on a real cluster, I believe the approach is wrong. Most > clusters used in academia is run by a professional support staff and > have a sophisticated setup for scheduling jobs. I'd never get DSage set > up correctly on my cluster without pestering a lot of admins. However I > *can* of course integrate Sage with the cluster-provided job scheduling > system in user space if I want to. That's the way to go IMO. Do you mean you can write an interface for, let's say, TorquePBS/Maui submition ? That would be very much useful. I'll send you an invitation to sage-grid mailing list. May be we could elaborate smth interesting for cluster environment. > > Dag Sverre > #Serge -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: ALL doctests pass on Solaris !!!
On 2010-Mar-01 14:42:38 +, "Dr. David Kirkby" wrote: >I've just succeeded in getting all doctests to pass on Solaris. Firstly, congratulations on this. On 2010-Mar-01 19:09:54 +, "Dr. David Kirkby" wrote: >There should be minor differences between Solaris 10 on SPARC and >Solaris 10 on x86. Incorrectly #ifdef'd assembly code might be irritating but at least the assembler will choke on it. More subtle problems will be code that assumes Sun/Solaris means big-endian. >There is quite a difference from Solaris 10 to Open Solaris. The >latter is aimed much more for desktop use. I've found that OpenSolaris feels a lot more like Linux than Solaris does. -- Peter Jeremy pgpLlPIAbQGta.pgp Description: PGP signature
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
On Tue, Mar 2, 2010 at 11:01 AM, Robert Bradshaw wrote: > On Mar 1, 2010, at 4:26 AM, William Stein wrote: > >> Hi, >> >> I've created this trac wiki page with a subset of the 10 most >> important current bug/issues in Sage, according to votes in this >> thread: >> >> http://trac.sagemath.org/sage_trac/wiki/stab1 >> >> These are all bugs/issues that many people care about. None are >> highly specialized. >> >> So if anybody has some time to donate to working on Sage, and you want >> to make an impact that people will definitely appreciate, work on one >> of the bugs listed at http://trac.sagemath.org/sage_trac/wiki/stab1 >> >> After seeing the actual bugs, I no longer see the wisdom of making a >> specific release targeting them. The problem is that they are all >> potentially hard, and there is no telling when they will all be >> resolved. However, listing them all together and seeing that a lot of >> people care about them will help encourage people to work on them. > > Just a thought, would knocking out this important list of bugs be a good > goal for Sage 5.0? > > - Robert That's an AWESOME idea! Plus some coverage goal, e.g., 85%. William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] fractals in sage
Hi, A student of mine is going to add to sage the capability of plotting lots and lots of fractals easily. E.g., sage: fractals.[tab] lots of stuff sage: fractals.julia([params]).show(figsize=10) [up pops a julia set] The trac ticket where this starts is here: http://trac.sagemath.org/sage_trac/ticket/8423 This isn't going to be some complicated fancy object oriented abstract dynamical metaclassed framework. It's just a bunch of functions to draw fractals. And at first it could even be slow (though obviously some cython master will probably clear through it at some point and make everything really fast, without having to change or write any docs). I can imagine that most of the files will consist of examples and docstrings rather than actual code, too. The point of this email: if you like plotting fractals, and have some potentially useful code to contribute, then please post to this thread or http://trac.sagemath.org/sage_trac/ticket/8423 with them.Or if you really want to help, then do so. -- William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Vote on bugs to be fixed for sage-4.4 "stabilization release".
On Mar 1, 2010, at 4:26 AM, William Stein wrote: Hi, I've created this trac wiki page with a subset of the 10 most important current bug/issues in Sage, according to votes in this thread: http://trac.sagemath.org/sage_trac/wiki/stab1 These are all bugs/issues that many people care about. None are highly specialized. So if anybody has some time to donate to working on Sage, and you want to make an impact that people will definitely appreciate, work on one of the bugs listed at http://trac.sagemath.org/sage_trac/wiki/stab1 After seeing the actual bugs, I no longer see the wisdom of making a specific release targeting them. The problem is that they are all potentially hard, and there is no telling when they will all be resolved. However, listing them all together and seeing that a lot of people care about them will help encourage people to work on them. Just a thought, would knocking out this important list of bugs be a good goal for Sage 5.0? - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: ALL doctests pass on Solaris !!!
Dima Pasechnik wrote: hmm, there are sparc solaris machines on skynet; they are much faster than t2... Thank you. That is useful to know. Do you know what is the fastest of the SPARC? I did have an account on there, but seem to have forgotten my password! I believe there is a Blade 2500. I don't know the speed of that particular model, but know the CPUs in a Blade can be either 1.28 or 1.6 GHz. Perhaps there is something faster I don't know about, but a Blade 2500 is a pretty old machine. But it should be two or three times quicker than 't2'. Dave On Mar 2, 2:29 am, Robert Bradshaw wrote: On Mar 1, 2010, at 9:06 AM, Dr. David Kirkby wrote: mhampton wrote: Congratulations, it seems that you have made a great deal of progress on this! -Marshall Yes, congratulations! Thank you Marshall. Hopefully, Solaris can soon become "fully supported" if all tests are passing. As long as the releases are handled carefully, and code not committed that breaks on Solaris, we should be able to get OpenSolaris building. Having a faster machine than 't2' on sage.math would be really nice. It's a real shame, as 't2' is capable of very high performance at low power consumption for the tasks it is designed for, but I find using a 10-year old machine quicker for Sage development. Once OpenSolaris is up and running, we could put it in a VM on boxen, and use it as part of the build farm. Of course that won't be a true Sparc solaris machine, but unless someone has extra money/hardware laying around it'll probably be a more realistic solution that waiting on t2 throughout the whole release management process. - Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Exhibit booth for 2011 joint meetings
On a related note: between now and the 2011 JMM is this summer's International Congress. The information about exhibits is in a PDF downloadable from here: http://www.icm2010.com/exh_manual.asp The smallest booth (6 m^2) runs about $3000, plus $25/day for internet access. My guess is that there aren't going to be nearly enough Sagers who have other reason to make the trip to Hyderabad for a Sage booth to be viable. So far I can think of myself and William. If I'm missing anyone, feel free to counterargue... Kiran On Mar 2, 10:10 am, mhampton wrote: > I've made a wiki page for this, at: > > http://wiki.sagemath.org/jmms2011 > > I took the liberty of adding Karl and Rob to the list, since they > seemed pretty definitive about going. Anyone else who is interested > in helping with the booth please sign up! > > The "call for exhibitors and sponsors" will be in early May according > to the AMS website. > > -Marshall -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Exhibit booth for 2011 joint meetings
I've made a wiki page for this, at: http://wiki.sagemath.org/jmms2011 I took the liberty of adding Karl and Rob to the list, since they seemed pretty definitive about going. Anyone else who is interested in helping with the booth please sign up! The "call for exhibitors and sponsors" will be in early May according to the AMS website. -Marshall -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Questions and proposals for matrices
On Mar 2, 3:39 pm, "Dr. David Kirkby" wrote: > Dima Pasechnik wrote: > > I guess, this: > >http://trac.sagemath.org/sage_trac/ticket/7723 > > "I have not idea when I can get back to this at the moment. Basically > > what has happened is that I bit the bullet and implemented my own > > numerical matrix class hierarchy which is usable without Sage (but > > loosely modeled after it). That ended up giving me the results I > > needed much faster... > > The long-term goal is to perhaps try to merge this back into Sage, > > however as there's no real benefit for my own work in doing that I > > don't really know if or when. > > (Anyone who finds this ticket because they need this functionality are > > welcome to send me an email and check the status.)" > > > Eventually I'm gonna need sparsematricesto play well with cvxopt. > > Just a thought. I've not looked at this thread in any detail, but in some ways > going along with the MATLAB approach might be best. MATLAB has become pretty > popular at numerical stuff (far more than Mathematica). So many users might > know > it better. There is also an Octave interface to Sage - Octave is basically a > MATLAB clone. > > BTW, I do *not* know MATLAB much myself, so can't say how it handles things. > But > perhaps some do. MATLAB is quite popular in engineering, though I have tended > to > avoid it as I knew Mathematica first. Hmm. Not sure if I follow you. Use MATLAB for what? Forgetting about engineering toolboxes etc, the technology of MATLAB is widely available in many other libraries (BLAS/ATLAS, SuiteSparse, ...) and also found in NumPy and SciPy (and, as a yet another implementation, in cvxopt -- in many ways the cvxopt API more closely mirrors MATLAB, but in the end it all boils down to BLAS and one of the common sparse libraries). (Note that all I did in those halfly abandoned tickets was write a wrapper around SciPy matrices to get them into the Sage matrix classes and coercion model. Absolutely no algorithms or technology.) As for the user interface/API of MATLAB, it is horrible and so far removed from what Sage does and stand for that I don't see how it is relevant. If that is what user wants that, the question is: Why use Sage at all, and not just Octave or MATLAB? And indeed, one can already use the Sage notebook to interface with those, so in a sense we already have that. Dag Sverre -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] logarithm of equations
Dear sage-devel Is there any reason to return log(a=b) instead of log(a)=log(b) when we use logarthm on equality? Adding numbers and multiplying numbers work in this way: [ma...@um-bc107 /opt]$ sage -- | Sage Version 4.3.3, Release Date: 2010-02-21 | | Type notebook() for the GUI, and license() for information.| -- sage: eq = exp(x) == exp(x^2) sage: log(eq) # I want x == x^2 log(e^x == e^(x^2)) sage: eq.log()# I want x == x^2 log(e^x == e^(x^2)) sage: eq+4 e^x + 4 == e^(x^2) + 4 sage: eq*8 8*e^x == 8*e^(x^2) sage: eq^2 e^(2*x) == e^(2*x^2) Is there any objection against a change which takes logarihtm (sine, exp, ) of both functions, if used on equality? How to achieve this change? Many thanks Robert -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
On Tue, Mar 2, 2010 at 6:43 AM, Minh Nguyen wrote: > Hi David, > > On Wed, Mar 3, 2010 at 1:32 AM, Dr. David Kirkby > wrote: > > > >> Decide on something, document it, then us all use it. My own preference >> would be to use foobar.x.y.z when a new upstream release is used. Then when >> the first patch is added, the package becomes foobar.x.y.z.p0. > > I thought I made this clear when I documented the procedure for > upgrading/updating spkg's. The relevant section documenting this > procedure is at > > http://www.sagemath.org/doc/developer/patching_spkgs.html#bumping-up-an-spkg-s-version > > As it turns out, my wordings in that section are not clear enough. > Feel free to open a ticket to enhance that section and CC me on it. > What you wrote is already amazingly crystal clear and of course matches exactly with what I do anyways (which is probably what you were recording there). I just didn't know about it, and clearly David didn't either. Minh -- thanks!! -- William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
Hi David, On Wed, Mar 3, 2010 at 1:32 AM, Dr. David Kirkby wrote: > Decide on something, document it, then us all use it. My own preference > would be to use foobar.x.y.z when a new upstream release is used. Then when > the first patch is added, the package becomes foobar.x.y.z.p0. I thought I made this clear when I documented the procedure for upgrading/updating spkg's. The relevant section documenting this procedure is at http://www.sagemath.org/doc/developer/patching_spkgs.html#bumping-up-an-spkg-s-version As it turns out, my wordings in that section are not clear enough. Feel free to open a ticket to enhance that section and CC me on it. -- Regards Minh Van Nguyen -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Questions and proposals for matrices
Dima Pasechnik wrote: I guess, this: http://trac.sagemath.org/sage_trac/ticket/7723 "I have not idea when I can get back to this at the moment. Basically what has happened is that I bit the bullet and implemented my own numerical matrix class hierarchy which is usable without Sage (but loosely modeled after it). That ended up giving me the results I needed much faster... The long-term goal is to perhaps try to merge this back into Sage, however as there's no real benefit for my own work in doing that I don't really know if or when. (Anyone who finds this ticket because they need this functionality are welcome to send me an email and check the status.)" Eventually I'm gonna need sparse matrices to play well with cvxopt. Just a thought. I've not looked at this thread in any detail, but in some ways going along with the MATLAB approach might be best. MATLAB has become pretty popular at numerical stuff (far more than Mathematica). So many users might know it better. There is also an Octave interface to Sage - Octave is basically a MATLAB clone. BTW, I do *not* know MATLAB much myself, so can't say how it handles things. But perhaps some do. MATLAB is quite popular in engineering, though I have tended to avoid it as I knew Mathematica first. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
On Tue, Mar 2, 2010 at 6:32 AM, Dr. David Kirkby wrote: > William Stein wrote: > >>> I think you missed my point there. >>> >>> I was suggesting that if (for example) python 2.6.4.p7 was updated to >>> python >>> 2.6.5, that the patch level went from 7 to 8, so the new package would be >>> python-2.6.5.p8. That way, the patch level gave us some idea of how often >>> packages were updated. >> >> -1 >> >> I didn't imagined you could actually have meant that; thanks for the >> clarification. Alex's remark that the full history is available >> anyways in any spkg is enough. >> >> William >> > > Fair enough. I accept that. > > I think the main point is that whatever is used, should be used > consistently. It is clear Mike and I were using a different method - me > starting a new release as foobar.x.y.z, with mike using foobar.x.y.z.p0. > > Decide on something, document it, then us all use it. My own preference > would be to use foobar.x.y.z when a new upstream release is used. Then when > the first patch is added, the package becomes foobar.x.y.z.p0. > > But I don't particularly care, but it would be nice to know what is > considered the right way. I very much like your suggestion. Let's make it official: Use foobar.x.y.z when a new upstream release is used. Then when the first patch is added, the package becomes foobar.x.y.z.p0. This seems logical to me. William -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
William Stein wrote: I think you missed my point there. I was suggesting that if (for example) python 2.6.4.p7 was updated to python 2.6.5, that the patch level went from 7 to 8, so the new package would be python-2.6.5.p8. That way, the patch level gave us some idea of how often packages were updated. -1 I didn't imagined you could actually have meant that; thanks for the clarification. Alex's remark that the full history is available anyways in any spkg is enough. William Fair enough. I accept that. I think the main point is that whatever is used, should be used consistently. It is clear Mike and I were using a different method - me starting a new release as foobar.x.y.z, with mike using foobar.x.y.z.p0. Decide on something, document it, then us all use it. My own preference would be to use foobar.x.y.z when a new upstream release is used. Then when the first patch is added, the package becomes foobar.x.y.z.p0. But I don't particularly care, but it would be nice to know what is considered the right way. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Questions and proposals for matrices
Burcin Erocal wrote: Hi Dag, On Mon, 1 Mar 2010 23:55:17 -0800 (PST) dagss wrote: What I hope can happen: - The NumPy/SciPy world gets an object oriented matrix library (mine or something else). They won't be adopting Sage soon anyway. - Then, as a step 2, Sage gets a generic numerical matrix class which wraps matrices from this matrix library. One of the things I made my mind up about while working with matrices in Sage is that numerical Sage matrices should have a common base class anyway (rather than being seperated by dense/sparse in the hierarchy). (I'm happy to talk with any students (GSoC?) who might wish to take on this, BTW.) By "this" do you mean the plan you outline above or any other way of integrating your work into Sage? I guess I meant any work in any form that deals with numerical matrices in Sage becoming useful for serious stuff -- I'm open for discussion and participating in submitting what I have, but unfortunately I really can't either be a driving force or do the dirty work (as I tried and failed on the time allotment I have for it, basically) Thinking through it again though, this is not the best starting point for a GSoC project, so in fact I wish you just forget what I said there :-) Dag Sverre -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Update upstream version. Patch levels starts at p0 ???
On Tue, Mar 2, 2010 at 3:22 AM, Dr. David Kirkby wrote: > William Stein wrote: > >>> In some ways, I think it would be better if the patch level was >>> incremented >>> every time a change of any sort was made to a package. One could then see >> >> That is what should definitely be done. If it isn't, then the >> automatic upgrade system wouldn't work, since it would think the >> package was already installed. If you change an spkg, make sure to >> change the name. >> >> >> -- William >> > > I think you missed my point there. > > I was suggesting that if (for example) python 2.6.4.p7 was updated to python > 2.6.5, that the patch level went from 7 to 8, so the new package would be > python-2.6.5.p8. That way, the patch level gave us some idea of how often > packages were updated. -1 I didn't imagined you could actually have meant that; thanks for the clarification. Alex's remark that the full history is available anyways in any spkg is enough. William -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
