[sage-devel] Re: can't handle symmetric functions > 15?
Hello, I figured out the problem and posted a patch at http://trac.sagemath.org/sage_trac/ticket/2839 . It was a very silly mistake that I should have caught the last time; I've included doctests for the issue this time. I've also included a change which speeds up the change of basis for the classical symmetric functions over QQ: Before: sage: time s(p(s([17,11]))) CPU times: user 1252.31 s, sys: 8.24 s, total: 1260.55 s Wall time: 1259.90 s[17, 11] sage: time a = s([10,10]).itensor(s([10,10])) CPU times: user 30.87 s, sys: 0.21 s, total: 31.09 s Wall time: 31.09 After: sage: time s(p(s([17,11]))) CPU times: user 257.11 s, sys: 0.03 s, total: 257.14 s Wall time: 257.15 s[17, 11] sage: time a = s([10,10]).itensor(s([10,10])) CPU times: user 3.60 s, sys: 0.00 s, total: 3.60 s Wall time: 3.60 --Mike On Sun, Apr 6, 2008 at 11:44 AM, mabshoff <[EMAIL PROTECTED]> wrote: > > On Apr 6, 8:32 pm, Nick Alexander <[EMAIL PROTECTED]> wrote: > > On 6-Apr-08, at 11:10 AM, Franco Saliola wrote: > > > > > > > > > > > > > Hello Mike (H), > > > > > > > On Sun, Apr 6, 2008 at 5:46 AM, Mike Hansen <[EMAIL PROTECTED]> wrote: > > > > >> I'm not able to reproduce your bug. Here is what I get: > > > > > I am able to reproduce the bug (on an Intel machine; see below). > > > > >> sage: s = SFASchur(QQ) > > >> sage: p = SFAPower(QQ) > > >> sage: s(p(s([14]))) > > >> s[14] > > >> sage: a = s(p(s([14])))*s([14]) > > >> sage: a > > >> s[14, 14] + s[15, 13] + s[16, 12] + s[17, 11] + s[18, 10] + s[19, > > >> 9] + > > >> s[20, 8] + s[21, 7] + s[22, 6] + s[23, 5] + s[24, 4] + s[25, 3] + > > >> s[26, 2] + s[27, 1] + s[28] > > > > > This is okay. > > > > >> sage: sage: s = SFASchur(QQ) > > >> sage: s([14,14]).itensor(s([17,11])) > > > > > This is not. For example, > > > > > sage: c = s([14,14]).itensor(s([17,11])) > > > sage: c.coefficients()[70] > > > 42204149/896259893760 > > > > I get the same (rational) result as Franco. I am running 'SAGE > > Version 2.11, Release Date: 2008-03-30' on > > > > $ uname -a > > Darwin pv109059.reshsg.uci.edu 8.11.1 Darwin Kernel Version 8.11.1: > > Wed Oct 10 18:23:28 PDT 2007; root:xnu-792.25.20~1/RELEASE_I386 i386 > > i386 > > > > That's an Intel MacBook Pro, Core 2 duo, OS X 10.4.x. > > This seems to be a 32 vs. 64 bit issue. On sage.math: > > -- > | SAGE Version 3.0.alpha1, Release Date: 2008-04-04 | > | Type notebook() for the GUI, and license() for information.| > -- > > sage: s = SFASchur(QQ) > > sage: c = s([14,14]).itensor(s([17,11])) > sage: c.coefficients()[70] > 0 > sage: > Exiting SAGE (CPU time 18m6.83s, Wall time 25m14.11s). > > 18 minutes of CPU time translates to quite a long valgrind time, but > if it is an overflow that won't catch it anyway. > > > Nick > > Cheers, > > Michael > > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] trac is down....
david --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: trac is down....
On Apr 7, 2:25 pm, David Harvey <[EMAIL PROTECTED]> wrote: > david Yeah, ran out of disc space. It is fixed now, but only a question of time until it will happen again. Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: [sage-support] PDE and Finite Element methods
Hector told me (in a separate email) about DOLFIN http://www.fenics.org/wiki/FEniCS_Project which is built on numpy. Although I had trouble installing it, I'm wondering if anyone else on this list has been able to try it out? Cross-posting to sage-devel. On Wed, Apr 2, 2008 at 7:19 PM, Hector Villafuerte <[EMAIL PROTECTED]> wrote: > > Hi, > I wonder what the current situation in SAGE is for dealing with PDE > and methods to solve them numerically, such as say Finite Elements. > > A quick search threw this thread (which I'm afraid is not very conclusive): > > http://groups.google.com/group/sage-devel/browse_thread/thread/15c7e426fc571e26 > > Thanks in advance for any pointers! > -- > Hector > > > > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: [sage-support] PDE and Finite Element methods
On Mon, Apr 7, 2008 at 3:12 PM, David Joyner <[EMAIL PROTECTED]> wrote: > > Hector told me (in a separate email) about DOLFIN > http://www.fenics.org/wiki/FEniCS_Project > which is built on numpy. Although I had trouble installing it, > I'm wondering if anyone else on this list has been able to try it out? Yes, I did. This is the code developed by people at Simula. It works nice, but it's quite difficult to install. I generally prefer smaller tools, if I can get the job done. Ondrej --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
mabshoff wrote: > Hello folks, > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > things are still of alpha quality: > On Fedora 7, 32 bits: sage -t devel/sage/sage/coding/sd_codes.py sh: line 1: 10820 Aborted /home/jaap/downloads/sage-3.0.alpha2/local/bin/python /home/jaap/downloads/sage-3.0.alpha2/tmp/.doctest_sd_codes.py > /tmp/tmpW7L8kg 2> /tmp/tmp_GAAnJ ^[[?1034h A mysterious error (perphaps a memory error?) occurred, which may have crashed doctest. [2.8 s] sage -t devel/sage/sage/rings/polynomial/polynomial_element_generic.pysh: line 1: 19081 Aborted /home/jaap/downloads/sage-3.0.alpha2/local/bin/python /home/jaap/downloads/sage-3.0.alpha2/tmp/.doctest_polynomial_element_generic.py > /tmp/tmp2RCBPK 2> /tmp/tmpIfPmrO ^[[?1034h A mysterious error (perphaps a memory error?) occurred, which may have crashed doctest. I can't reproduce this failures. [EMAIL PROTECTED] sage-3.0.alpha2]$ ./sage -t devel/sage/sage/coding/sd_codes.py sage -t pha2/devel/sage/sage/coding/sd_codes.py [2.2 s] -- All tests passed! Total time for all tests: 2.2 seconds [EMAIL PROTECTED] sage-3.0.alpha2]$ ./sage -t devel/sage/sage/rings/polynomial/polynomial_element_generic.py sage -t pha2/devel/sage/sage/rings/polynomial/polynomial_element_generic.py [2.9 s] -- All tests passed! Total time for all tests: 2.9 seconds Jaap --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] p-adic crash error
Jen Balakrishnan spent time with some of the usual suspects during the
Arizona Winter School tracking down bugs in the p-adics, but more
remain. We've isolated a code snippet that makes sage 2.11 go boom on
multiple platforms:
{{{
sage: R. = QQ[]
sage: K = Qp(11,10)
sage: J. = K.extension(x^30-11)
sage: M. = PowerSeriesRing(J)
sage: S. = QQ[]
sage: xr = O(a^152)*t + (8*a^2 + 10*a^32 + 7*a^62 + 10*a^92 + 7*a^122
+ O(a^152))*t^2 + O(a^154)*t^3 + (2*a^4 + 10*a^64 + 2*a^124 +
O(a^154))*t^4 + O(a^156)*t^5 + (5*a^6 + 2*a^96 + a^126 + O(a^156))*t^6
+ O(a^158)*t^7 + (7*a^8 + 6*a^38 + 8*a^68 + 2*a^98 + 5*a^128 +
O(a^158))*t^8 + O(a^160)*t^9 + (8*a^10 + 10*a^40 + a^70 + 5*a^130 +
O(a^160))*t^10 + O(a^162)*t^11 + (9*a^12 + 7*a^42 + 8*a^72 + 6*a^102 +
9*a^132 + O(a^162))*t^12 + O(a^164)*t^13 + (2*a^14 + 5*a^44 + 3*a^74 +
a^104 + 4*a^134 + O(a^164))*t^14 + O(a^166)*t^15 + (2*a^16 + 5*a^46 +
8*a^76 + 5*a^106 + 7*a^136 + O(a^166))*t^16 + O(a^168)*t^17 + (7*a^18
+ 3*a^48 + 6*a^78 + 9*a^138 + O(a^168))*t^18 + O(a^172)*t^19 + (7*a^50
+ 3*a^80 + 5*a^110 + 5*a^140 + 7*a^170 + O(a^172))*t^20 +
O(a^172)*t^21 + (a^22 + a^52 + 3*a^82 + 3*a^112 + 2*a^142 +
O(a^172))*t^22 + O(a^174)*t^23 + (4*a^24 + 7*a^54 + 9*a^84 + 4*a^114 +
7*a^144 + O(a^174))*t^24 + O(a^176)*t^25 + (3*a^26 + 8*a^56 + 8*a^116
+ 5*a^146 + O(a^176))*t^26 + O(a^178)*t^27 + (2*a^28 + 2*a^58 + 6*a^88
+ a^118 + 10*a^148 + O(a^178))*t^28 + O(a^180)*t^29 + (8*a^30 + 5*a^60
+ 8*a^90 + 5*a^120 + 6*a^150 + O(a^180))*t^30 + O(a^184)*t^31 +
(7*a^62 + 9*a^92 + 2*a^182 + O(a^184))*t^32
sage: yr = xr^2
sage: dtr = xr.derivative()
sage: f_dtr = yr*dtr # boom
FFTRep: inconsistent use
(and then sage exits uncleanly)
}}}
I wasn't able to find a shorter value of xr that reproduces this
(removing the t^32 term alleviates the error).
We've opened ticket #2843 for this.
Kiran
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
On Apr 7, 5:13 pm, Jaap Spies <[EMAIL PROTECTED]> wrote: > mabshoff wrote: > > Hello folks, > > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > > things are still of alpha quality: Hi Jaap, > On Fedora 7, 32 bits: > > sage -t devel/sage/sage/coding/sd_codes.py sh: line 1: 10820 > Aborted /home/jaap/downloads/sage-3.0.alpha2/local/bin/python > /home/jaap/downloads/sage-3.0.alpha2/tmp/.doctest_sd_codes.py > > /tmp/tmpW7L8kg 2> /tmp/tmp_GAAnJ > ^[[?1034h > A mysterious error (perphaps a memory error?) occurred, which may have > crashed doctest. > [2.8 s] > > sage -t devel/sage/sage/rings/polynomial/polynomial_element_generic.pysh: > line 1: 19081 Aborted > /home/jaap/downloads/sage-3.0.alpha2/local/bin/python > /home/jaap/downloads/sage-3.0.alpha2/tmp/.doctest_polynomial_element_generic.py > > /tmp/tmp2RCBPK 2> > /tmp/tmpIfPmrO > ^[[?1034h > A mysterious error (perphaps a memory error?) occurred, which may have > crashed doctest. > > I can't reproduce this failures. This is very, very likely the PolyBoRi issue. The PolyBoRi people gave some pointers how to debug this, so we might have this fixed hopefully soon. Thanks for the build report. > [EMAIL PROTECTED] sage-3.0.alpha2]$ ./sage -t > devel/sage/sage/coding/sd_codes.py > sage -t pha2/devel/sage/sage/coding/sd_codes.py > [2.2 s] > > -- > All tests passed! > Total time for all tests: 2.2 seconds > [EMAIL PROTECTED] sage-3.0.alpha2]$ ./sage -t > devel/sage/sage/rings/polynomial/polynomial_element_generic.py > sage -t pha2/devel/sage/sage/rings/polynomial/polynomial_element_generic.py > [2.9 s] > > -- > All tests passed! > Total time for all tests: 2.9 seconds > > Jaap Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
Installed fine on ubuntu 7.10 amd64. My machine hangs randomly (and
non-reproducibly)
during a sage -testall, apparently only when it encounters maxima. I
have to ctl-c and
restart. However, so far I did get this:
sage -t devel/sage/sage/functions/piecewise.py
**
File "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/tmp/piecewise.py", line 389:
sage: Q = rsf.plot(rgbcolor=(0.7,0.6,0.6), plot_points=40)
Exception raised:
Traceback (most recent call last):
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/doctest.py",
line 1212, in __run
compileflags, 1) in test.globs
File "", line 1, in
Q =
rsf.plot(rgbcolor=(RealNumber('0.7'),RealNumber('0.6'),RealNumber('0.6')),
plot_points=Integer(40))###line 389:
sage: Q = rsf.plot(rgbcolor=(0.7,0.6,0.6), plot_points=40)
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/functions/piecewise.py",
line 798, in plot
return sum([plot(p[1], p[0][0], p[0][1], *args, **kwds ) for p
in self.list()])
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/plot/plot.py",
line 3553, in __call__
G = funcs.plot(*args, **kwds)
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/calculus/calculus.py",
line 914, in plot
y = float(F)
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/calculus/calculus.py",
line 7801, in __float__
return float(maxima(self))
File
"/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/interfaces/maxima.py",
line 1619, in __float__
raise TypeError, "unable to coerce '%s' to float"%repr(self)
TypeError: unable to coerce ''__SAGE_SYNCHRO_MARKER_473778504(1/2)' to float
**
1 items had failures:
1 of 15 in __main__.example_11
***Test Failed*** 1 failures.
On Mon, Apr 7, 2008 at 1:29 AM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
> Hello folks,
>
> this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But
> things are still of alpha quality:
>
> Issue: Invalid read in libgroebner.so (#2822) - this happens
> with each sage session and results on occasional segfautls at
> exit. They look like
>
> *** glibc detected *** corrupted double-linked list:
> 0x00958a60 ***
>
> They are caused by PolyBoRi, but I am unsure at the moment
> if it is a general problem or in our PolyBoRi Wrapper.
>
> Issue: sage-3.0-alpha1 on ppc -- new randstate code doesn't
> work right at all (#2814) - you will see loads of doctest
> failure on PPC OSX since the randgen framework by cwitty has
> some endianess issues
>
> Issue: Linbox build failure on OSX 10.4 intel (#2833) - build
> will fail in OSX 10.4. So far no solution
>
> What is new? Update of Singular, DSage fixes, a LinBox segfault
> has been fixed and the usual set of other improvements.
>
> What is next? gcc 4.3 fixes, the usual set of merges. Alpha3
> should be out in the next 48 hours.
>
> Sources and binaries are in the usual place:
>
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2.tar
>
>
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2-sage.math-only-x86_64-Linux.tar.gz
>
> According to http://trac.sagemath.org/sage_trac/report/13 there
> are 45 tickets with patches - so please do reviews.
>
> Cheers,
>
> Michael
>
> Merged in alpha2:
>
> #358: John Cremona: padic_height_pairing_matrix computes too
> many heights
> #530: Martin Albrecht: leak in Matrix_integer_dense__solve_iml
> exposed by matrix/strassen.pyx
> #2316: Yi Qiang: dsage.start_all() can leave zombie workers
>around
> #2346: Robert Bradshaw: Sage needs a simple api for interaction
>with other applications
> #2497: David Harvey: crash in polynomial remainder
> #2680: Craig Citro: Modular forms for Gamma1(N) have wrong Sturm
>bound
> #2743: Jason Grout: make symbolic equalities and inequalities
>callable
> #2745: Yi Qiang: upgrade twisted to 8.0.1
> #2772: Martin Albrecht: Update Singular to 3-0-4-2
> #2775: Martin Albrecht: multivariate factoring over some rings
>gives incorrect results [this is a limitation of Factory,
>so instead of returning an incorrect result throw an
>exception]
> #2799: Didier Deshommes: matrix's __getitem__ doesn't respect
>slice object's step attribute
> #2804: Clement Pernet: fix ssmod.py failure [linbox related]
> #2805: Emily Kirkman: Add maximal parameter to Graph genus
>computation
> #2806: Michael Abshoff: Sage 3.0.a2: numerical noise in
>sage/misc/prandom.py doctest
> #2807: David Harvey: line 26 of c_lib/src/interrupt.c is wrong
> #2808: Daniel Bump: G2 fundamental weights were the negative of
>
[sage-devel] class variables in cython classes
In trying to unify the linear algebra syntax, I came across the following behavior: sage: a=matrix(2,range(4)) sage: a.nrows() 2 sage: a._nrows --- Traceback (most recent call last) /home/grout/sage/devel/sage-main/sage/misc/ in () : 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no attribute '_nrows' sage: a.__dict__ --- Traceback (most recent call last) /home/grout/sage/devel/sage-main/sage/misc/ in () : 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no attribute '__dict__' I noted that the nrows() function just returned self._nrows. So how come I can't access _nrows? Does it have to do with Cython and inheritance? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] using bitset.pxi in user programs
I love the new bitset.pxi file in sage/misc/. Can I access these functions from a cython file that a user writes (i.e., that is not part of the sage source)? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: class variables in cython classes
On Apr 7, 2008, at 10:07 AM, Jason Grout wrote: > > In trying to unify the linear algebra syntax, I came across the > following behavior: > > > sage: a=matrix(2,range(4)) > sage: a.nrows() > 2 > sage: a._nrows > -- > - > Traceback (most recent > call last) > > /home/grout/sage/devel/sage-main/sage/misc/ in > () > > : > 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no > attribute '_nrows' > sage: a.__dict__ > -- > - > Traceback (most recent > call last) > > /home/grout/sage/devel/sage-main/sage/misc/ in > () > > : > 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no > attribute '__dict__' > > > I noted that the nrows() function just returned self._nrows. So how > come I can't access _nrows? Does it have to do with Cython and > inheritance? Yes, this is a Cython vs. Python issue. a._nrows is literally a c int in the object structure, not a member of a dictionary. In fact, Cython classes don't even have dictionaries. From Cython a._nrows is probably on the order of two or three magnitudes faster than a.nrows() We could declare _nrows and _ncols to be readonly, in which case a __getattr__ (or more technically a property accessor method) method would be created for them. - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: using bitset.pxi in user programs
On Apr 7, 2008, at 10:12 AM, Jason Grout wrote: > > I love the new bitset.pxi file in sage/misc/. Thanks :). > Can I access these > functions from a cython file that a user writes (i.e., that is not > part > of the sage source)? Yes. I think one would have to copy and/or include the file (giving its full path) directly. Currently there's an .h file that's hanging around too (although that will go away now the new version of Cython is included in Sage). - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: class variables in cython classes
Robert Bradshaw wrote: > On Apr 7, 2008, at 10:07 AM, Jason Grout wrote: >> In trying to unify the linear algebra syntax, I came across the >> following behavior: >> >> >> sage: a=matrix(2,range(4)) >> sage: a.nrows() >> 2 >> sage: a._nrows >> -- >> - >> Traceback (most recent >> call last) >> >> /home/grout/sage/devel/sage-main/sage/misc/ in >> () >> >> : >> 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no >> attribute '_nrows' >> sage: a.__dict__ >> -- >> - >> Traceback (most recent >> call last) >> >> /home/grout/sage/devel/sage-main/sage/misc/ in >> () >> >> : >> 'sage.matrix.matrix_integer_dense.Matrix_integer_de' object has no >> attribute '__dict__' >> >> >> I noted that the nrows() function just returned self._nrows. So how >> come I can't access _nrows? Does it have to do with Cython and >> inheritance? > > Yes, this is a Cython vs. Python issue. a._nrows is literally a c int > in the object structure, not a member of a dictionary. In fact, > Cython classes don't even have dictionaries. From Cython a._nrows is > probably on the order of two or three magnitudes faster than a.nrows() > > We could declare _nrows and _ncols to be readonly, in which case a > __getattr__ (or more technically a property accessor method) method > would be created for them. Thanks for the explanation. The issue came up when I wanted to just do M=self.transpose() or M=self, depending on if the user wanted right or left action computations (e.g., right vs. left kernels). However, then calls to M._nrows (which used to be calls to self._nrows) don't work. I'll just set an M_nrows variable to either self._nrows or self._ncols, whichever is needed. That way we still have the order-of-magnitude speedup. Unless someone has a better idea. Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: using bitset.pxi in user programs
Robert Bradshaw wrote: > On Apr 7, 2008, at 10:12 AM, Jason Grout wrote: >> I love the new bitset.pxi file in sage/misc/. > > Thanks :). > >> Can I access these >> functions from a cython file that a user writes (i.e., that is not >> part >> of the sage source)? > > Yes. I think one would have to copy and/or include the file (giving > its full path) directly. Currently there's an .h file that's hanging > around too (although that will go away now the new version of Cython > is included in Sage). How much of a speed penalty do you think there would be in wrapping these functions in a bitset cython class? Or would this slow things down to about the performance of the python set class? Thanks, Jason --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: using bitset.pxi in user programs
On Apr 7, 2008, at 10:36 AM, Jason Grout wrote: > > Robert Bradshaw wrote: >> On Apr 7, 2008, at 10:12 AM, Jason Grout wrote: >>> I love the new bitset.pxi file in sage/misc/. >> >> Thanks :). >> >>> Can I access these >>> functions from a cython file that a user writes (i.e., that is not >>> part >>> of the sage source)? >> >> Yes. I think one would have to copy and/or include the file (giving >> its full path) directly. Currently there's an .h file that's hanging >> around too (although that will go away now the new version of Cython >> is included in Sage). > > How much of a speed penalty do you think there would be in wrapping > these functions in a bitset cython class? Or would this slow things > down to about the performance of the python set class? This was a very good idea. The only reason I didn't do it myself was because the bitset implementation itself took more time than I had anticipated putting into it and I had other things I had to do. It could still be very fast, especially if the methods are cpdef. (It would not be as fast as using bitset.pxi's inline functions directly of course, but sometimes ease of use trumps absolute performance). Testing would be much more natural as well. Currently bitset.pxi assumes you know the size of the bitset at creation time, and doesn't do any bounds checking. I think a class could abstract this and act like an infinite bitset, with higher- order bits being by default zero. - Robert --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: p-adic crash error
I'm back from my three week trip to the west coast and will take a look at this.
David
On Mon, Apr 7, 2008 at 11:16 AM, Kiran Kedlaya <[EMAIL PROTECTED]> wrote:
>
> Jen Balakrishnan spent time with some of the usual suspects during the
> Arizona Winter School tracking down bugs in the p-adics, but more
> remain. We've isolated a code snippet that makes sage 2.11 go boom on
> multiple platforms:
> {{{
> sage: R. = QQ[]
> sage: K = Qp(11,10)
> sage: J. = K.extension(x^30-11)
> sage: M. = PowerSeriesRing(J)
> sage: S. = QQ[]
> sage: xr = O(a^152)*t + (8*a^2 + 10*a^32 + 7*a^62 + 10*a^92 + 7*a^122
> + O(a^152))*t^2 + O(a^154)*t^3 + (2*a^4 + 10*a^64 + 2*a^124 +
> O(a^154))*t^4 + O(a^156)*t^5 + (5*a^6 + 2*a^96 + a^126 + O(a^156))*t^6
> + O(a^158)*t^7 + (7*a^8 + 6*a^38 + 8*a^68 + 2*a^98 + 5*a^128 +
> O(a^158))*t^8 + O(a^160)*t^9 + (8*a^10 + 10*a^40 + a^70 + 5*a^130 +
> O(a^160))*t^10 + O(a^162)*t^11 + (9*a^12 + 7*a^42 + 8*a^72 + 6*a^102 +
> 9*a^132 + O(a^162))*t^12 + O(a^164)*t^13 + (2*a^14 + 5*a^44 + 3*a^74 +
> a^104 + 4*a^134 + O(a^164))*t^14 + O(a^166)*t^15 + (2*a^16 + 5*a^46 +
> 8*a^76 + 5*a^106 + 7*a^136 + O(a^166))*t^16 + O(a^168)*t^17 + (7*a^18
> + 3*a^48 + 6*a^78 + 9*a^138 + O(a^168))*t^18 + O(a^172)*t^19 + (7*a^50
> + 3*a^80 + 5*a^110 + 5*a^140 + 7*a^170 + O(a^172))*t^20 +
> O(a^172)*t^21 + (a^22 + a^52 + 3*a^82 + 3*a^112 + 2*a^142 +
> O(a^172))*t^22 + O(a^174)*t^23 + (4*a^24 + 7*a^54 + 9*a^84 + 4*a^114 +
> 7*a^144 + O(a^174))*t^24 + O(a^176)*t^25 + (3*a^26 + 8*a^56 + 8*a^116
> + 5*a^146 + O(a^176))*t^26 + O(a^178)*t^27 + (2*a^28 + 2*a^58 + 6*a^88
> + a^118 + 10*a^148 + O(a^178))*t^28 + O(a^180)*t^29 + (8*a^30 + 5*a^60
> + 8*a^90 + 5*a^120 + 6*a^150 + O(a^180))*t^30 + O(a^184)*t^31 +
> (7*a^62 + 9*a^92 + 2*a^182 + O(a^184))*t^32
> sage: yr = xr^2
> sage: dtr = xr.derivative()
> sage: f_dtr = yr*dtr # boom
> FFTRep: inconsistent use
> (and then sage exits uncleanly)
> }}}
> I wasn't able to find a shorter value of xr that reproduces this
> (removing the t^32 term alleviates the error).
>
> We've opened ticket #2843 for this.
>
> Kiran
>
>
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
The following tests failed:
sage -t devel/sage/sage/functions/piecewise.py
sage -t devel/sage/sage/dsage/tests/testdoc.py
sage -t devel/sage/sage/combinat/cartan_matrix.py
sage -t devel/sage/sage/matrix/action.pyx
sage -t devel/sage/sage/categories/category_types.py
sage -t devel/sage/sage/schemes/hyperelliptic_curves/kummer_surface.py
sage -t devel/sage/sage/misc/sage_timeit.py
sage -t devel/sage/sage/calculus/functions.py
sage -t devel/sage/sage/plot/plot3dsoya_wrap.py
sage -t devel/sage/sage/server/notebook/interact.py
Total time for all tests: 4749.8 seconds
Posted test.log to
http://sage.math.washington.edu/home/wdj/patches/test.log
On Mon, Apr 7, 2008 at 12:24 PM, David Joyner <[EMAIL PROTECTED]> wrote:
> Installed fine on ubuntu 7.10 amd64. My machine hangs randomly (and
> non-reproducibly)
> during a sage -testall, apparently only when it encounters maxima. I
> have to ctl-c and
> restart. However, so far I did get this:
>
> sage -t devel/sage/sage/functions/piecewise.py
> **
> File "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/tmp/piecewise.py", line 389:
> sage: Q = rsf.plot(rgbcolor=(0.7,0.6,0.6), plot_points=40)
> Exception raised:
> Traceback (most recent call last):
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/doctest.py",
> line 1212, in __run
> compileflags, 1) in test.globs
> File "", line 1, in
> Q =
> rsf.plot(rgbcolor=(RealNumber('0.7'),RealNumber('0.6'),RealNumber('0.6')),
> plot_points=Integer(40))###line 389:
> sage: Q = rsf.plot(rgbcolor=(0.7,0.6,0.6), plot_points=40)
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/functions/piecewise.py",
> line 798, in plot
> return sum([plot(p[1], p[0][0], p[0][1], *args, **kwds ) for p
> in self.list()])
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/plot/plot.py",
> line 3553, in __call__
> G = funcs.plot(*args, **kwds)
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/calculus/calculus.py",
> line 914, in plot
> y = float(F)
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/calculus/calculus.py",
> line 7801, in __float__
> return float(maxima(self))
> File
> "/home/wdj/wdj/sagefiles/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/interfaces/maxima.py",
> line 1619, in __float__
> raise TypeError, "unable to coerce '%s' to float"%repr(self)
> TypeError: unable to coerce ''__SAGE_SYNCHRO_MARKER_473778504(1/2)' to
> float
> **
> 1 items had failures:
>1 of 15 in __main__.example_11
> ***Test Failed*** 1 failures.
>
>
>
> On Mon, Apr 7, 2008 at 1:29 AM, mabshoff
> <[EMAIL PROTECTED]> wrote:
> >
> > Hello folks,
> >
> > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But
> > things are still of alpha quality:
> >
> > Issue: Invalid read in libgroebner.so (#2822) - this happens
> > with each sage session and results on occasional segfautls at
> > exit. They look like
> >
> > *** glibc detected *** corrupted double-linked list:
> > 0x00958a60 ***
> >
> > They are caused by PolyBoRi, but I am unsure at the moment
> > if it is a general problem or in our PolyBoRi Wrapper.
> >
> > Issue: sage-3.0-alpha1 on ppc -- new randstate code doesn't
> > work right at all (#2814) - you will see loads of doctest
> > failure on PPC OSX since the randgen framework by cwitty has
> > some endianess issues
> >
> > Issue: Linbox build failure on OSX 10.4 intel (#2833) - build
> > will fail in OSX 10.4. So far no solution
> >
> > What is new? Update of Singular, DSage fixes, a LinBox segfault
> > has been fixed and the usual set of other improvements.
> >
> > What is next? gcc 4.3 fixes, the usual set of merges. Alpha3
> > should be out in the next 48 hours.
> >
> > Sources and binaries are in the usual place:
> >
> >
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2.tar
> >
> >
> http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2-sage.math-only-x86_64-Linux.tar.gz
> >
> > According to http://trac.sagemath.org/sage_trac/report/13 there
> > are 45 tickets with patches - so please do reviews.
> >
> > Cheers,
> >
> > Michael
> >
> > Merged in alpha2:
> >
> > #358: John Cremona: padic_height_pairing_matrix computes too
> > many heights
> > #530: Martin Albrecht: leak in Matrix_integer_dense__solve_iml
> > exposed by matrix/strassen.pyx
> > #2316: Yi Qiang: dsage.start_all() can leave zombie workers
> >around
> > #2346: Robert Bradsh
[sage-devel] Re: p-adic crash error
On 07/04/2008, David Roe <[EMAIL PROTECTED]> wrote:
>
> I'm back from my three week trip to the west coast and will take a look at
> this.
I didn't realise that p-adics were coast-sensitive!
John
>
> David
>
>
> On Mon, Apr 7, 2008 at 11:16 AM, Kiran Kedlaya <[EMAIL PROTECTED]> wrote:
> >
> > Jen Balakrishnan spent time with some of the usual suspects during the
> > Arizona Winter School tracking down bugs in the p-adics, but more
> > remain. We've isolated a code snippet that makes sage 2.11 go boom on
> > multiple platforms:
> > {{{
> > sage: R. = QQ[]
> > sage: K = Qp(11,10)
> > sage: J. = K.extension(x^30-11)
> > sage: M. = PowerSeriesRing(J)
> > sage: S. = QQ[]
> > sage: xr = O(a^152)*t + (8*a^2 + 10*a^32 + 7*a^62 + 10*a^92 + 7*a^122
> > + O(a^152))*t^2 + O(a^154)*t^3 + (2*a^4 + 10*a^64 + 2*a^124 +
> > O(a^154))*t^4 + O(a^156)*t^5 + (5*a^6 + 2*a^96 + a^126 + O(a^156))*t^6
> > + O(a^158)*t^7 + (7*a^8 + 6*a^38 + 8*a^68 + 2*a^98 + 5*a^128 +
> > O(a^158))*t^8 + O(a^160)*t^9 + (8*a^10 + 10*a^40 + a^70 + 5*a^130 +
> > O(a^160))*t^10 + O(a^162)*t^11 + (9*a^12 + 7*a^42 + 8*a^72 + 6*a^102 +
> > 9*a^132 + O(a^162))*t^12 + O(a^164)*t^13 + (2*a^14 + 5*a^44 + 3*a^74 +
> > a^104 + 4*a^134 + O(a^164))*t^14 + O(a^166)*t^15 + (2*a^16 + 5*a^46 +
> > 8*a^76 + 5*a^106 + 7*a^136 + O(a^166))*t^16 + O(a^168)*t^17 + (7*a^18
> > + 3*a^48 + 6*a^78 + 9*a^138 + O(a^168))*t^18 + O(a^172)*t^19 + (7*a^50
> > + 3*a^80 + 5*a^110 + 5*a^140 + 7*a^170 + O(a^172))*t^20 +
> > O(a^172)*t^21 + (a^22 + a^52 + 3*a^82 + 3*a^112 + 2*a^142 +
> > O(a^172))*t^22 + O(a^174)*t^23 + (4*a^24 + 7*a^54 + 9*a^84 + 4*a^114 +
> > 7*a^144 + O(a^174))*t^24 + O(a^176)*t^25 + (3*a^26 + 8*a^56 + 8*a^116
> > + 5*a^146 + O(a^176))*t^26 + O(a^178)*t^27 + (2*a^28 + 2*a^58 + 6*a^88
> > + a^118 + 10*a^148 + O(a^178))*t^28 + O(a^180)*t^29 + (8*a^30 + 5*a^60
> > + 8*a^90 + 5*a^120 + 6*a^150 + O(a^180))*t^30 + O(a^184)*t^31 +
> > (7*a^62 + 9*a^92 + 2*a^182 + O(a^184))*t^32
> > sage: yr = xr^2
> > sage: dtr = xr.derivative()
> > sage: f_dtr = yr*dtr # boom
> > FFTRep: inconsistent use
> > (and then sage exits uncleanly)
> > }}}
> > I wasn't able to find a shorter value of xr that reproduces this
> > (removing the t^32 term alleviates the error).
> >
> > We've opened ticket #2843 for this.
> >
> > Kiran
> >
> >
> > >
> >
>
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
On Apr 6, 2008, at 22:29 , mabshoff wrote: > > Hello folks, > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > things are still of alpha quality: > Sources and binaries are in the usual place: > > http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage-3.0.alpha2.tar 10.5.2 (Dual Quad Xeon, "-j6") Build succeeded, test had 1 failure (the known prandom problem): real82m35.203s user73m5.825s sys 23m21.640s ... SAGE build/upgrade complete! -- The following tests failed: sage -t devel/sage/sage/misc/prandom.py Total time for all tests: 3236.6 seconds The detail: ** sage -t devel/sage/sage/misc/prandom.py File "/Users/tmp/sage-3.0.alpha2/tmp/prandom.py", line 241: sage: [gauss(0, 100) for i in range(3)] Expected: [24.916051749154448, -62.992720615792727, -8.1993122536718097] Got: [24.916051749154448, -62.992720615792727, -8.1993122536718115] ** 1 items had failures: 1 of 4 in __main__.example_13 ***Test Failed*** 1 failures. For whitespace errors, see the file /Users/tmp/sage-3.0.alpha2/ tmp/.doctest_prandom.py [4.4 s] 10.4.11 (Core 2 Duo, "-j2"): Build failed, as others have seen. Full log is at sage.math.washington.edu:~justin/logs/3.0.A2.install.log should you want to check it. -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds If you're not confused, You're not paying attention --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
On Apr 7, 9:31 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote: > On Apr 6, 2008, at 22:29 , mabshoff wrote: > > > > > Hello folks, > > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But > > things are still of alpha quality: > > Sources and binaries are in the usual place: > > >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage... > > 10.5.2 (Dual Quad Xeon, "-j6") > Build succeeded, test had 1 failure (the known prandom problem): > real 82m35.203s > user 73m5.825s > sys 23m21.640s > ... > SAGE build/upgrade complete! > > -- > The following tests failed: > > sage -t devel/sage/sage/misc/prandom.py > Total time for all tests: 3236.6 seconds > > The detail: > > ** > sage -t devel/sage/sage/misc/prandom.py > File "/Users/tmp/sage-3.0.alpha2/tmp/prandom.py", line 241: > sage: [gauss(0, 100) for i in range(3)] > Expected: > [24.916051749154448, -62.992720615792727, -8.1993122536718097] > Got: > [24.916051749154448, -62.992720615792727, -8.1993122536718115] > > ** > 1 items had failures: > 1 of 4 in __main__.example_13 > ***Test Failed*** 1 failures. > For whitespace errors, see the file /Users/tmp/sage-3.0.alpha2/ > tmp/.doctest_prandom.py > [4.4 s] Thanks Justin, this is now #2848. Patch coming up in a minute or two. > 10.4.11 (Core 2 Duo, "-j2"): > Build failed, as others have seen. Full log is at > sage.math.washington.edu:~justin/logs/3.0.A2.install.log > should you want to check it. Yeah, that one will be a pain to fix unless Cement does it :) > -- > Justin C. Walker, Curmudgeon-At-Large > Institute for the Absorption of Federal Funds Cheers, Michael > > If you're not confused, > You're not paying attention huh? > --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: Sage 3.0.alpha2 released
Build report: on this machine:
Linux host-57-71 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC
2007 x86_64 x86_64 x86_64 GNU/Linux
with gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) it builds
fine and testall passes except for these:
sage -t devel/sage/sage/dsage/tests/testdoc.py
sage -t devel/sage/sage/tests/benchmark.py
Details:
{{{
sage -t devel/sage/sage/dsage/tests/testdoc.py
**
File "/home/jec/sage-3.0.alpha2/tmp/testdoc.py", line 13:
sage: a.wait(timeout=30)
Exception raised:
Traceback (most recent call last):
File "/home/jec/sage-3.0.alpha2/local/lib/python2.5/doctest.py",
line 1212, in __run
compileflags, 1) in test.globs
File "", line 1, in
a.wait(timeout=Integer(30))###line 13:
sage: a.wait(timeout=30)
File
"/home/jec/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py",
line 862, in wait
time.sleep(1.0)
File
"/home/jec/sage-3.0.alpha2/local/lib/python2.5/site-packages/sage/dsage/interface/dsage_interface.py",
line 858, in handler
raise RuntimeError('Maximum wait time exceeded.')
RuntimeError: Maximum wait time exceeded.
**
File "/home/jec/sage-3.0.alpha2/tmp/testdoc.py", line 14:
sage: a
Expected:
5
Got:
No output yet.
**
File "/home/jec/sage-3.0.alpha2/tmp/testdoc.py", line 46:
sage: reactor.callFromThread(reactor.stop)
Expected nothing
Got:
[DSage] Closed connection to localhost
**
File "/home/jec/sage-3.0.alpha2/tmp/testdoc.py", line 47:
sage: d._dsage_thread.join()
Expected:
[DSage] Closed connection to localhost
Got nothing
**
1 items had failures:
4 of 23 in __main__.example_0
***Test Failed*** 4 failures.
For whitespace errors, see the file
/home/jec/sage-3.0.alpha2/tmp/.doctest_testdoc.py
[80.4 s]
exit code: 1024
--
}}}
but the second one worked when I tried it again!
John
On 07/04/2008, mabshoff <[EMAIL PROTECTED]> wrote:
>
>
>
> On Apr 7, 9:31 pm, "Justin C. Walker" <[EMAIL PROTECTED]> wrote:
> > On Apr 6, 2008, at 22:29 , mabshoff wrote:
> >
> >
> >
> > > Hello folks,
> >
> > > this is Sage 3.0.alpha2. Up to now we closed 111 tickets. But
> > > things are still of alpha quality:
> > > Sources and binaries are in the usual place:
> >
>
> > >http://sage.math.washington.edu/home/mabshoff/release-cycles-3.0/sage...
>
> >
> > 10.5.2 (Dual Quad Xeon, "-j6")
> > Build succeeded, test had 1 failure (the known prandom problem):
> > real82m35.203s
> > user73m5.825s
> > sys 23m21.640s
> > ...
> > SAGE build/upgrade complete!
> >
> > --
> > The following tests failed:
> >
> > sage -t devel/sage/sage/misc/prandom.py
> > Total time for all tests: 3236.6 seconds
> >
> > The detail:
> >
> > **
> > sage -t devel/sage/sage/misc/prandom.py
> > File "/Users/tmp/sage-3.0.alpha2/tmp/prandom.py", line 241:
> > sage: [gauss(0, 100) for i in range(3)]
> > Expected:
> > [24.916051749154448, -62.992720615792727, -8.1993122536718097]
> > Got:
> > [24.916051749154448, -62.992720615792727, -8.1993122536718115]
> >
> > **
> > 1 items had failures:
> > 1 of 4 in __main__.example_13
> > ***Test Failed*** 1 failures.
> > For whitespace errors, see the file /Users/tmp/sage-3.0.alpha2/
> > tmp/.doctest_prandom.py
> > [4.4 s]
>
>
> Thanks Justin, this is now #2848. Patch coming up in a minute or two.
>
>
> > 10.4.11 (Core 2 Duo, "-j2"):
> > Build failed, as others have seen. Full log is at
> >sage.math.washington.edu:~justin/logs/3.0.A2.install.log
> > should you want to check it.
>
>
> Yeah, that one will be a pain to fix unless Cement does it :)
>
>
> > --
> > Justin C. Walker, Curmudgeon-At-Large
> > Institute for the Absorption of Federal Funds
>
>
>
> Cheers,
>
> Michael
>
>
> >
> > If you're not confused,
> > You're not paying attention
>
>
> huh?
>
>
> >
> >
>
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~
[sage-devel] Re: hyperlinks for Colloquy users
Works great for me on a ppc (G4) 10.4.11 mac. Thanks, those little things can make a quite a difference! -Marshall Hampton On Apr 4, 12:22 pm, David Harvey <[EMAIL PROTECTED]> wrote: > Hi all, > > This message is for Sage developers who use theColloquyIRC chat > client. > > I have patchedColloquyso that text like "#1234" gets hyperlinked to > the sage trac server. > > Here is the patch file, which should get applied to the file Panels/ > JVDirectChatPanel.m in the root of thecolloquytree (you can get the > original source via svn from the maincolloquyweb site): > >http://math.harvard.edu/~dmharvey/sage-colloquy.patch > > Also I made a binary. I think I made it Universal. But really I have > no idea what I'm doing, since I don't really know how to use XCode, > but it seems to work for me (OSX 10.4.11, intel): > >http://math.harvard.edu/~dmharvey/Colloquy.app.zip > > david --~--~-~--~~~---~--~~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-devel] Re: hyperlinks for Colloquy users
On Mon, 07 Apr 2008 at 04:47PM -0700, mhampton wrote: > > I have patchedColloquyso that text like "#1234" gets hyperlinked to > > the sage trac server. Another thing that everyone can do is set up a Firefox "Quick Search" so that you can just type something like "sagetrac 1234" in the location bar and it takes you to that ticket. Look in the Quick Searches folder under the bookmarks menu and copy one of the pre-made searches; you'll need to use "http://sagetrac.org/sage_trac/ticket/%s"; in the location field, and then add "sagetrac" (or whatever you like) for the keyword. You can get the same sort of thing in Safari, too: http://purefiction.net/keywurl/ Dan -- --- Dan Drake <[EMAIL PROTECTED]> - KAIST Department of Mathematical Sciences --- http://math.kaist.ac.kr/~drake signature.asc Description: Digital signature
[sage-devel] trouble running n() on matrices
Hello all, I'm running into problems with coercing to complexes or reals in matrices: sage: d = matrix([[3, 0],[0,sqrt(2)]]) sage: b = matrix([[1, -1], [2, 2]]) sage: e = b * d * b.inverse(); e [1/sqrt(2) + 3/2 3/4 - 1/(2*sqrt(2))] [3 - sqrt(2) 1/sqrt(2) + 3/2] and when I try to run n() on the matrix e, I get: sage: e.n() # or n(e) [snip] : unable to coerce to a ComplexNumber but I can run n() on all the entries of e: sage: n(e[0,0]) 2.20710678118655 sage: n(e[1,0]) 1.58578643762690 sage: n(e[1,1]) 2.20710678118655 sage: n(e[0,1]) 0.396446609406726 Also, I can't run .n() on the matrix b, even though it's an integer matrix! sage: parent(b) Full MatrixSpace of 2 by 2 dense matrices over Integer Ring sage: b.n() [same as before] : unable to coerce to a ComplexNumber Yikes! It can't coerce integers into complexes! But in other situations, there's no trouble: sage: n(5) 5.00 sage: parent(sqrt(2)) Symbolic Ring sage: n(sqrt(2)) 1.41421356237310 It seems clear that when I have a matrix with expressions like "1/sqrt(2) + 3/2" and I run n() on it, I want the obvious floating point approximations. Am I going about this wrong? Is this not a correct use of matrices? Or is it a coercion bug? Any help is much appreciated. Dan -- --- Dan Drake <[EMAIL PROTECTED]> - KAIST Department of Mathematical Sciences --- http://math.kaist.ac.kr/~drake signature.asc Description: Digital signature
