Re: [sage-devel] Build did not work 4.3.5 Ubuntu 9.10 (atlas-3.8.3.p12)
On Apr 14, 2010, at 11:12 PM, Bruce Cohen wrote: I have a new machine with Ubuntu 9.10 (32 bit). My first build of Sage (4.3.5) did not work. Here is a 100 line (maybe too many lines, maybe too little) of install.log. Thanks for your help. -Bruce How loaded is your machine? make[3]: *** [build] Error 255 make[3]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' make[2]: *** [build] Error 2 make[2]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' Failed to build ATLAS. ATLAS failed to build for the 1-th time, possibly because of a loaded system, so we will automatically try again up to 4 more times. Waiting 9 minutes... ATLAS failed to build for the 2-th time, possibly because of a loaded system, so we will automatically try again up to 3 more times. Waiting 10 minutes... ATLAS failed to build for the 3-th time, possibly because of a loaded system, so we will automatically try again up to 2 more times. Waiting 10 minutes... ATLAS failed to build for the 4-th time, possibly because of a loaded system, so we will automatically try again up to 1 more times. Waiting 7 minutes... Too many failures to build ATLAS. Giving up! ATLAS seems to be having issues getting reliable timings for its tuning. - 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 To unsubscribe, reply using "remove me" as the subject.
[sage-devel] Build did not work 4.3.5 Ubuntu 9.10 (atlas-3.8.3.p12)
I have a new machine with Ubuntu 9.10 (32 bit). My first build of Sage (4.3.5) did not work. Here is a 100 line (maybe too many lines, maybe too little) of install.log. Thanks for your help. -Bruce euler:~/src/sage-4.3.5> tail -100 install.log make[7]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm' make auxillib zcleanuplib zusergemm make[8]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm' cd /home/bic/src/sage-4.3.5/spkg/build/atlas-3.8.3.p12/ATLAS-build/src/ auxil ; make lib make[9]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/auxil' make[9]: Nothing to be done for `lib'. make[9]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/auxil' cd KERNEL ; make -f zMakefile zlib make[9]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm/KERNEL' gcc -DL2SIZE=4194304 -I/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/include -I/home/bic/src/sage-4.3.5/spkg/ build/atlas-3.8.3.p12/ATLAS-build/../src//include -I/home/bic/src/ sage-4.3.5/spkg/build/atlas-3.8.3.p12/ATLAS-build/../src//include/ contrib -DAdd_ -DF77_INTEGER=int -DStringSunStyle -DATL_OS_Linux - DATL_ARCH_UNKNOWNx86 -DATL_CPUMHZ=1200 -DATL_SSE3 -DATL_SSE2 - DATL_SSE1 -DATL_GAS_x8632 -DATL_UCLEANM -DATL_UCLEANN -DATL_UCLEANK - O -fomit-frame-pointer -fPIC -m32 -c ATL_zupNBmm_b0.c ATL_zupNBmm_b0.c: In function ‘ATL_zpNBmm_b0’: ATL_zupNBmm_b0.c:61: error: ‘else’ without a previous ‘if’ ATL_zupNBmm_b0.c:65: error: ‘else’ without a previous ‘if’ make[9]: *** [ATL_zupNBmm_b0.o] Error 1 make[9]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm/KERNEL' make[8]: *** [zcleanuplib] Error 2 make[8]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm' make[7]: *** [zlib] Error 2 make[7]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/src/blas/gemm' make[6]: *** [zmmlib] Error 2 make[6]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/tune/blas/gemm' make[5]: *** [res/atlas_zdNKB.h] Error 2 make[5]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/tune/blas/gemm' make[4]: *** [/home/bic/src/sage-4.3.5/spkg/build/atlas-3.8.3.p12/ ATLAS-build/tune/blas/gemm/res/atlas_zdNKB.h] Error 2 make[4]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/bin' ERROR 664 DURING CACHE EDGE DETECTION!!. make[4]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/bin' cd /home/bic/src/sage-4.3.5/spkg/build/atlas-3.8.3.p12/ATLAS-build ; make error_report make[5]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' make -f Make.top error_report make[6]: Entering directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' uname -a 2>&1 >> bin/INSTALL_LOG/ERROR.LOG gcc -v 2>&1 >> bin/INSTALL_LOG/ERROR.LOG Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.4.1-4ubuntu9' --with-bugurl=file:///usr/share/doc/gcc-4.4/ README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/ usr --enable-shared --enable-multiarch --enable-linker-build-id --with- system-zlib --libexecdir=/usr/lib --without-included-gettext --enable- threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program- suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-werror --with- arch-32=i486 --with-tune=generic --enable-checking=release -- build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu Thread model: posix gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) gcc -V 2>&1 >> bin/INSTALL_LOG/ERROR.LOG gcc: '-V' option must have argument make[6]: [error_report] Error 1 (ignored) gcc --version 2>&1 >> bin/INSTALL_LOG/ERROR.LOG tar cf error_UNKNOWNx8632SSE3.tar Make.inc bin/INSTALL_LOG/* gzip --best error_UNKNOWNx8632SSE3.tar mv error_UNKNOWNx8632SSE3.tar.gz error_UNKNOWNx8632SSE3.tgz make[6]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' make[5]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build' make[4]: Leaving directory `/home/bic/src/sage-4.3.5/spkg/build/ atlas-3.8.3.p12/ATLAS-build/bin' Error report error_.tgz has been created in your top-level ATLAS directory. Be sure to include this file in any help request. cat: ../../CONFIG/error.txt: No such file or directory cat: ../../CONFIG/error.txt: No such file or directory =2, pf=512, nb=36, mu=1, nu=2 ku=36, ForceFetch=0, ifetch=3 nfetch=1 Performance = 3646.82 (33.10 of copy matmul, 303.90 of clock) make -f Makefile MMinstall pre=z 2>&1 | ./xatlas_tee INST
[sage-devel] Sage Tutorial at Amazon.com
On Wed, Apr 14, 2010 at 7:10 PM, David Joyner wrote: > The createspace server has accepted everything and I received the > proof in the mail a few hours ago. I didn't like a few things, so will > try to tweek the latex source a bit (the bibliography is on p101 > instead of p97, and there was an overfull box on p17 ...) > to fix some minor problems. Hopefully the server will accept the new > pdf file I uploaded and I'll get another proof copy in a week or so > and I can approve that. Thanks. A few days ago I got yet another royalty check (for the Sage Foundation) reporting about 20 sales. So people do regularly buy the printed Tutorial. -- William -- William Stein 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 To unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Sage Tutorial at Amazon.com
The createspace server has accepted everything and I received the proof in the mail a few hours ago. I didn't like a few things, so will try to tweek the latex source a bit (the bibliography is on p101 instead of p97, and there was an overfull box on p17 ...) to fix some minor problems. Hopefully the server will accept the new pdf file I uploaded and I'll get another proof copy in a week or so and I can approve that. On Sat, Apr 10, 2010 at 8:28 AM, David Joyner wrote: > On Sat, Apr 10, 2010 at 7:04 AM, David Joyner wrote: > >> >> >> Just to summarize what I just did: We used to use latex files, now we use >> rest/sphinx. Using >> ./sage -docbuild tutorial latex >> I created the latex files. Then I followed John's suggestions in >> http://www.mail-archive.com/sage-supp...@googlegroups.com/msg10625.html >> to change the pdf to the funny margin size that createspace.com requires. >> Now, it is just a matter of jumping through the createspace hoops. >> >> Should I choose a different cover design? Last time it was a mountain >> on a gray cover. For example, I could try to replace the mountain by >> something >> more sagemath-ish. > > I just submitted the files to the createspace.com server. In a day or > so, it will > tell me whether or not it will reject what I uploaded. If there was no > rejection, I have > to order a proof copy by mail, which will take several more days. Once > that arrives, > I can approve the final version for publication on createspace. I think it > takes > another few weeks to finally percolate up to the amazon.com site. > > BTW, I did choose a new (bluish) cover with one of Marshall's gfan images > for the cover. So the new cover is definitely more mathematical than > the old one. > > >> >> >>> Also, there is no way to remove any old versions. You have to >>> treat each new version of the tutorial as a new book and get a new ISBN. >>> >>> > > -- 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 > -- 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 unsubscribe, reply using "remove me" as the subject. >>> >> > -- 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: Problem with Maxima interface?
On Wed, 14 Apr 2010 at 05:18PM -0700, Nathan Dunfield wrote:
> > Here is a more concise, but essentially equivalent, code snippet which
> > exhibits the problem. Just attach and run "prob()" Again, it takes
> > 10-12 minutes to crash on my MacPro3,1 with 2 Quad-Core Xeon
> > Processors @ 2.8 Ghz, running 10.5.8, with Sage 4.3.2 self-compiled
> > with i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build
> > 5493).
>
> To follow up on myself one last time, here's what appears to be the
> minimal example exhibiting this problem
>
> def prob():
> for i in xrange(100):
> a = var('a')
> eqn = (a - 1)/(a)
> eqn.numerator()
>
> Note: If you run it once and it crashes, and then you run it again (w/
> o quiting Sage) it crashes much faster.
I can confirm that the above function eventually desynchronizes Maxima;
I'm using Sage 4.3.5 with Ubuntu 9.10 on a quad-core Core 2 processor.
This reminds me of a previous Maxima problem that Gonzalo Tornaria
solved -- there, the synchronization with Maxima was getting lost on
certain multi-core CPUs because of something related to switching
between cores. See #5662.
Dan
--
--- Dan Drake
- http://mathsci.kaist.ac.kr/~drake
---
signature.asc
Description: Digital signature
[sage-devel] Re: Problem with Maxima interface?
> Here is a more concise, but essentially equivalent, code snippet which
> exhibits the problem. Just attach and run "prob()" Again, it takes
> 10-12 minutes to crash on my MacPro3,1 with 2 Quad-Core Xeon
> Processors @ 2.8 Ghz, running 10.5.8, with Sage 4.3.2 self-compiled
> with i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build
> 5493).
To follow up on myself one last time, here's what appears to be the
minimal example exhibiting this problem
def prob():
for i in xrange(100):
a = var('a')
eqn = (a - 1)/(a)
eqn.numerator()
Note: If you run it once and it crashes, and then you run it again (w/
o quiting Sage) it crashes much faster.
Best,
Nathan
--
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 unsubscribe, reply using "remove me" as the subject.
[sage-devel] Re: Problem with Maxima interface?
Here is a more concise, but essentially equivalent, code snippet which
exhibits the problem. Just attach and run "prob()" Again, it takes
10-12 minutes to crash on my MacPro3,1 with 2 Quad-Core Xeon
Processors @ 2.8 Ghz, running 10.5.8, with Sage 4.3.2 self-compiled
with i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build
5493).
Best,
Nathan
--- problem code begins -
datum = ([0, 1, 0, 2, 0, 2], [([-1, -2, -1, 1, -1, 0], [1, 2, 1, 0, 1,
0], -1)])
coefficients, raw_natural_gluing_equations = datum
def eval_eqn( (a,b,c), z):
ans = c
for i, z in enumerate(z):
ans *= z**a[i] * (1 - z) ** b[i]
return ans
def first_order_equations():
n = len(coefficients)
a_vars = var(" ".join(["a%d" % i for i in range(n)]))
t = var('t')
base_eqns = raw_natural_gluing_equations
z = [ a * t ** e for a, e in zip(a_vars, coefficients) ]
eqns = [eval_eqn(eqn, z).subs(t=0) for eqn in base_eqns]
R = PolynomialRing(QQ, ['a%d' % i for i in range(n)])
poly_eqns = [ R(e.numerator()) for e in eqns]
def prob():
for i in xrange(100):
first_order_equations()
--
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 unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: code review tools
Speaking of that, why not institute a "program committee" where people volunteer to do reviews before your Sage days? I do a lot of program committee work, which is painful but is a professional "giving back to the community" task. It is always done against a deadline which is a great motivation. Tim Daly Jason Grout wrote: On 04/14/2010 03:04 PM, William Stein wrote: On Wed, Apr 14, 2010 at 12:43 PM, John Cremona wrote: I have been strongly encouraging new students starting out with Sage to make small (initially) patches on their very own ticket, so that they can feel good when these get reviewed positively and then merged. But those same people might take quite a while longer before they feel confident about reviewing others people's tickets. It's usually a long time after one has started submitting papers for publication that one starts to get requests for refereeing other papers -- not that long, but a while. Isn't that similar? Yes. The main intent of what I'm suggesting is that people who are contributing a *lot* of code, but not doing any reviewing, will be very, very strongly encouraged to do more reviewing. Maybe a more balanced system would address the concerns. You get a little karma for posting a patch, a little more karma for posting a patch on a ticket with someone else's patch (because you're probably sort of reviewing their code as you make your patch), and a lot more karma for reviewing a ticket. You'd get a "first-time bonus" karma for posting your first patch. Of course, this also might make it more complicated than it is worth. Jason -- 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 unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: [sage-combinat-devel] Happy Ada Lovelace Day
Hi John, On Thu, Apr 15, 2010 at 5:26 AM, John Cremona wrote: > Thanks for adding my student Charlie. Is there a link to this from > www.sagenb.org? I have added a link to that list. You can find the link at http://www.sagemath.org/links.html -- 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 To unsubscribe, reply using "remove me" as the subject.
[sage-devel] Re: Problem with Maxima interface?
On Apr 14, 2:57 pm, William Stein wrote:
> You should post exact code so that we can replicate your problem.
I've boiled down the problem into the example below. Just attach and
then run "prob()".
One thing to note is that's just doing the exact same thing again and
again, but eventually it up and crashes. On my system, which is
detailed below, it dies after about 10-20 minutes at the 4000ish
iteration.
System details: MacPro3,1 with 2 Quad-Core Xeon Processors @ 2.8 Ghz,
running 10.5.8.
Sage 4.3.2 self-compiled with i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1
(Apple Inc. build 5493)
Thanks,
Nathan
--begin code-
datum = ([0, 1, 0, 2, 0, 2], [([-1, -2, -1, 1, -1, 0], [1, 2, 1, 0, 1,
0], -1), ([2, 0, 0, 0, 0, 0], [0, -1, 0, 0, 0, 0], 1), ([-1, 2, 0, -1,
0, 0], [-1, 0, -1, 1, 0, 0], 1), ([0, 0, 1, 1, 0, -1], [0, -1, 1, -2,
-2, 2], -1), ([0, 0, 0, -1, 2, 1], [0, 0, -1, 1, 0, 0], -1), ([0, 0,
0, 0, -1, 0], [0, 0, 0, 0, 1, -2], -1)])
class Surface():
def __init__(self, datum):
self.Coefficients, self.RawEquations = datum
def eval_eqn( (a,b,c), z):
ans = c
for i, z in enumerate(z):
ans *= z**a[i] * (1 - z) ** b[i]
return ans
class OneCuspedManifold():
def raw_natural_gluing_equations(self, surface):
return surface.RawEquations
def natural_gluing_equations(self, surface):
n = len(surface.Coefficients)
z = var(" ".join(["z%d" % i for i in range(n)]))
return [eval_eqn(eqn, z) for eqn in
self.raw_natural_gluing_equations(surface)]
def first_order_equations(self, surface):
V = [int(e) for e in list(surface.Coefficients)]
n = len(V)
a_vars = var(" ".join(["a%d" % i for i in range(n)]))
t = var('t')
base_eqns = self.raw_natural_gluing_equations(surface)
z = [ a * t ** e for a, e in zip(a_vars, V) ]
eqns = [eval_eqn(eqn, z).subs(t=0) for eqn in base_eqns]
return eqns
def comes_from_an_ideal_point(self, surface):
n = len(surface.Coefficients)
R = PolynomialRing(QQ, ['a%d' % i for i in range(0,n)] + ['b
%d' % i for i in range(0,n)])
eqns = self.first_order_equations(surface)
poly_eqns = [ R(e.numerator() - e.denominator()) for e in
eqns]
def prob():
count = 0
while 1:
M = OneCuspedManifold()
S = Surface(datum)
M.comes_from_an_ideal_point(S)
count += 1
--
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 unsubscribe, reply using "remove me" as the subject.
[sage-devel] Re: code review tools
On 04/14/2010 03:04 PM, William Stein wrote: On Wed, Apr 14, 2010 at 12:43 PM, John Cremona wrote: I have been strongly encouraging new students starting out with Sage to make small (initially) patches on their very own ticket, so that they can feel good when these get reviewed positively and then merged. But those same people might take quite a while longer before they feel confident about reviewing others people's tickets. It's usually a long time after one has started submitting papers for publication that one starts to get requests for refereeing other papers -- not that long, but a while. Isn't that similar? Yes. The main intent of what I'm suggesting is that people who are contributing a *lot* of code, but not doing any reviewing, will be very, very strongly encouraged to do more reviewing. Maybe a more balanced system would address the concerns. You get a little karma for posting a patch, a little more karma for posting a patch on a ticket with someone else's patch (because you're probably sort of reviewing their code as you make your patch), and a lot more karma for reviewing a ticket. You'd get a "first-time bonus" karma for posting your first patch. Of course, this also might make it more complicated than it is worth. Jason -- 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 unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: code review tools
On Wed, Apr 14, 2010 at 12:43 PM, John Cremona wrote: > I have been strongly encouraging new students starting out with Sage > to make small (initially) patches on their very own ticket, so that > they can feel good when these get reviewed positively and then merged. > But those same people might take quite a while longer before they > feel confident about reviewing others people's tickets. > > It's usually a long time after one has started submitting papers for > publication that one starts to get requests for refereeing other > papers -- not that long, but a while. Isn't that similar? > Yes. The main intent of what I'm suggesting is that people who are contributing a *lot* of code, but not doing any reviewing, will be very, very strongly encouraged to do more reviewing. -- William > > On 14 April 2010 20:01, kcrisman wrote: >> >>> > I think something as simple as sorting the "tickets needing review" by >>> > author karma would be useful without being overly complicated or formal. >>> > The >>> >>> Yes, that's exactly what I was thinking of. If somebody referees a >>> lot of patches, then they automatically get singled out as "somebody >>> whose code contributions are extra deserving of reviews". >>> >> >> This seems reasonable, especially if it stays relatively unobtrusive. >> It would be bad to punish those who contribute great patches but only >> have time to contribute, not necessarily review, and could motivate >> reviewers who don't or can't often contribute to critical fixes but >> would like their work added to the base. >> >> In the end, though, one would have to see how it worked. If this >> ordering trumped the current "urgency" ordering and then things that >> were urgent didn't get reviewed, that would be bad, too. >> >>> >> cannot earn review points and cannot get his code in. On the other >>> >> hand, others collect a lot of review points but do not code. So, there >>> >> must be a way to trade points... !? >> >> Everything is fungible, you mean... maybe we could trade them for WoW >> money. Or maybe it could be Sage points, like AMS points, and you >> could use them to get a free copy of Sage. >> >> - kcrisman >> >> -- >> 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 unsubscribe, reply using "remove me" as the subject. >> > > -- > 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 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] Problem with Maxima interface?
On Wed, Apr 14, 2010 at 12:17 PM, Nathan Dunfield wrote: > I'm having the following problem with basic symbolics in Sage 4.3.2. > I create some variables with "var", combine them into rational > functions, then take their numerator and denominator and coerce them > into a PolynomialRing. This works fine most of the time, but very > occasionally (every few 1 usages) it chokes with following error > message: > > TypeError: unable to make sense of Maxima expression > '"__SAGE_SYNCHRO_MARKER_202188656"' in Sage > > If I use "pdb" to go up to frame at the top of the traceback, and > rerun the offending line, it works, as you can see below. > > Sometimes it dies with other message complaining about the syntax of > seeming correct expressions, e.g. > > TypeError: Error executing code in Maxima > CODE: > _tmp_ : -(a0-1)*a1^2*a3$ > Maxima ERROR: > > _tmp_ : -(a0-1)*a1^2*a3$ > stdin:57338284:Incorrect syntax: Illegal use of delimiter ) > (%i832002) > stdin:57338357:Incorrect syntax: Premature termination of input at ;. > (%i832003) > > Any ideas of what's going on here? You should post exact code so that we can replicate your problem. William > > Thanks, > > Nathan > > -- > | Sage Version 4.3.2, Release Date: 2010-02-06 | > | Type notebook() for the GUI, and license() for information. | > -- > sage: attach stavros/__init__.py > sage: %pdb > Automatic pdb calling has been turned ON > sage: test() > --- > TypeError Traceback (most recent call > last) > > /Users/dunfield/work/stavros3/ in () > > /Users/dunfield/work/stavros3/stavros/__init__.py in test() > 226 N = OneCuspedManifold(M) > 227 for S in N.NormalSurfaces: > --> 228 info = N.vertex_surface_info(S) > 229 if info [:-3] == (True, False, False): > 230 print M, N.NormalSurfaces.index(S), info > > /Users/dunfield/work/stavros3/stavros/__init__.py in > vertex_surface_info(self, surface) > 132 n = len(surface.Coefficients) > 133 is_kabaya = min(surface.Coefficients) > 0 > --> 134 is_ideal = self.comes_from_an_ideal_point(surface) > 135 is_isolated = self.vertex_surface_is_isolated(surface) > 136 return surface.BoundarySlope, is_isolated, is_kabaya, > is_ideal > > /Users/dunfield/work/stavros3/stavros/__init__.py in > comes_from_an_ideal_point(self, surface) > 121 R = PolynomialRing(QQ, ['a%d' % i for i in range(0,n)] > + ['b%d' % i for i in range(0,n)]) > 122 eqns = self.first_order_equations(surface) > --> 123 poly_eqns = [ R(e.numerator() - e.denominator()) for e > in eqns] > 124 gens = R.gens_dict() > 125 blow_up_eqns = [ gens["a%d" % i] * gens["b%d" % i] - 1 > for i in range(0, n)] > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/symbolic/ > expression.so in sage.symbolic.expression.Expression.denominator (sage/ > symbolic/expression.cpp:20432)() > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/structure/ > parent.so in sage.structure.parent.Parent.__call__ (sage/structure/ > parent.c:6206)() > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/structure/ > coerce_maps.so in sage.structure.coerce_maps.NamedConvertMap._call_ > (sage/structure/coerce_maps.c:4098)() > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/ > maxima.pyc in _symbolic_(self, R) > 1792 sqrt(2) > 1793 """ > -> 1794 return R(self._sage_()) > 1795 > 1796 def __complex__(self): > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/ > maxima.pyc in _sage_(self) > 1773 from sage.calculus.calculus import > symbolic_expression_from_maxima_string > 1774 #return > symbolic_expression_from_maxima_string(self.name(), > maxima=self.parent()) > > -> 1775 return > symbolic_expression_from_maxima_string(repr(self)) > 1776 > 1777 def _symbolic_(self, R): > > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/calculus/ > calculus.pyc in symbolic_expression_from_maxima_string(x, equals_sub, > maxima) > 1964 return symbolic_expression_from_string(s, syms, > accept_sequence=True) > 1965 except SyntaxError: > -> 1966 raise TypeError, "unable to make sense of Maxima > expression '%s' in Sage"%s > 1967 finally: > 1968 is_simplified = False > > TypeError: unable to make sense of Maxima expression > '"__SAGE_SYNCHRO_MARKER_202188656"' in Sage >> /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/calculus/calculus.py(1968)symbolic_expression_from_maxima_string() > 1967 finally: > -> 1968 is_simplified = False > 1969 > > ipdb> up >> /pkgs/sage-4
Re: [sage-devel] Re: code review tools
I have been strongly encouraging new students starting out with Sage to make small (initially) patches on their very own ticket, so that they can feel good when these get reviewed positively and then merged. But those same people might take quite a while longer before they feel confident about reviewing others people's tickets. It's usually a long time after one has started submitting papers for publication that one starts to get requests for refereeing other papers -- not that long, but a while. Isn't that similar? John On 14 April 2010 20:01, kcrisman wrote: > >> > I think something as simple as sorting the "tickets needing review" by >> > author karma would be useful without being overly complicated or formal. >> > The >> >> Yes, that's exactly what I was thinking of. If somebody referees a >> lot of patches, then they automatically get singled out as "somebody >> whose code contributions are extra deserving of reviews". >> > > This seems reasonable, especially if it stays relatively unobtrusive. > It would be bad to punish those who contribute great patches but only > have time to contribute, not necessarily review, and could motivate > reviewers who don't or can't often contribute to critical fixes but > would like their work added to the base. > > In the end, though, one would have to see how it worked. If this > ordering trumped the current "urgency" ordering and then things that > were urgent didn't get reviewed, that would be bad, too. > >> >> cannot earn review points and cannot get his code in. On the other >> >> hand, others collect a lot of review points but do not code. So, there >> >> must be a way to trade points... !? > > Everything is fungible, you mean... maybe we could trade them for WoW > money. Or maybe it could be Sage points, like AMS points, and you > could use them to get a free copy of Sage. > > - kcrisman > > -- > 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 unsubscribe, reply using "remove me" as the subject. > -- 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: [sage-combinat-devel] Happy Ada Lovelace Day
Thanks for adding my student Charlie. Is there a link to this from www.sagenb.org? John On 14 April 2010 01:15, Minh Nguyen wrote: > Hi Alex, > > On Sat, Apr 10, 2010 at 2:38 AM, Alex Ghitza wrote: > > > >> Two more contributors: > > Thank you for this, Alex. The list has been updated with your suggestions. > > -- > 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 > > To unsubscribe, reply using "remove me" as the subject. > -- 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] Problem with Maxima interface?
I'm having the following problem with basic symbolics in Sage 4.3.2. I create some variables with "var", combine them into rational functions, then take their numerator and denominator and coerce them into a PolynomialRing. This works fine most of the time, but very occasionally (every few 1 usages) it chokes with following error message: TypeError: unable to make sense of Maxima expression '"__SAGE_SYNCHRO_MARKER_202188656"' in Sage If I use "pdb" to go up to frame at the top of the traceback, and rerun the offending line, it works, as you can see below. Sometimes it dies with other message complaining about the syntax of seeming correct expressions, e.g. TypeError: Error executing code in Maxima CODE: _tmp_ : -(a0-1)*a1^2*a3$ Maxima ERROR: _tmp_ : -(a0-1)*a1^2*a3$ stdin:57338284:Incorrect syntax: Illegal use of delimiter ) (%i832002) stdin:57338357:Incorrect syntax: Premature termination of input at ;. (%i832003) Any ideas of what's going on here? Thanks, Nathan -- | Sage Version 4.3.2, Release Date: 2010-02-06 | | Type notebook() for the GUI, and license() for information.| -- sage: attach stavros/__init__.py sage: %pdb Automatic pdb calling has been turned ON sage: test() --- TypeError Traceback (most recent call last) /Users/dunfield/work/stavros3/ in () /Users/dunfield/work/stavros3/stavros/__init__.py in test() 226 N = OneCuspedManifold(M) 227 for S in N.NormalSurfaces: --> 228 info = N.vertex_surface_info(S) 229 if info [:-3] == (True, False, False): 230 print M, N.NormalSurfaces.index(S), info /Users/dunfield/work/stavros3/stavros/__init__.py in vertex_surface_info(self, surface) 132 n = len(surface.Coefficients) 133 is_kabaya = min(surface.Coefficients) > 0 --> 134 is_ideal = self.comes_from_an_ideal_point(surface) 135 is_isolated = self.vertex_surface_is_isolated(surface) 136 return surface.BoundarySlope, is_isolated, is_kabaya, is_ideal /Users/dunfield/work/stavros3/stavros/__init__.py in comes_from_an_ideal_point(self, surface) 121 R = PolynomialRing(QQ, ['a%d' % i for i in range(0,n)] + ['b%d' % i for i in range(0,n)]) 122 eqns = self.first_order_equations(surface) --> 123 poly_eqns = [ R(e.numerator() - e.denominator()) for e in eqns] 124 gens = R.gens_dict() 125 blow_up_eqns = [ gens["a%d" % i] * gens["b%d" % i] - 1 for i in range(0, n)] /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/symbolic/ expression.so in sage.symbolic.expression.Expression.denominator (sage/ symbolic/expression.cpp:20432)() /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/structure/ parent.so in sage.structure.parent.Parent.__call__ (sage/structure/ parent.c:6206)() /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/structure/ coerce_maps.so in sage.structure.coerce_maps.NamedConvertMap._call_ (sage/structure/coerce_maps.c:4098)() /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/ maxima.pyc in _symbolic_(self, R) 1792 sqrt(2) 1793 """ -> 1794 return R(self._sage_()) 1795 1796 def __complex__(self): /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/ maxima.pyc in _sage_(self) 1773 from sage.calculus.calculus import symbolic_expression_from_maxima_string 1774 #return symbolic_expression_from_maxima_string(self.name(), maxima=self.parent()) -> 1775 return symbolic_expression_from_maxima_string(repr(self)) 1776 1777 def _symbolic_(self, R): /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/calculus/ calculus.pyc in symbolic_expression_from_maxima_string(x, equals_sub, maxima) 1964 return symbolic_expression_from_string(s, syms, accept_sequence=True) 1965 except SyntaxError: -> 1966 raise TypeError, "unable to make sense of Maxima expression '%s' in Sage"%s 1967 finally: 1968 is_simplified = False TypeError: unable to make sense of Maxima expression '"__SAGE_SYNCHRO_MARKER_202188656"' in Sage > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/calculus/calculus.py(1968)symbolic_expression_from_maxima_string() 1967 finally: -> 1968 is_simplified = False 1969 ipdb> up > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/maxima.py(1775)_sage_() 1774 #return symbolic_expression_from_maxima_string(self.name(), maxima=self.parent()) -> 1775 return symbolic_expression_from_maxima_string(repr(self)) 1776 ipdb> up > /pkgs/sage-4.3.2/local/lib/python2.6/site-packages/sage/interfaces/
[sage-devel] Re: code review tools
> > I think something as simple as sorting the "tickets needing review" by > > author karma would be useful without being overly complicated or formal. The > > Yes, that's exactly what I was thinking of. If somebody referees a > lot of patches, then they automatically get singled out as "somebody > whose code contributions are extra deserving of reviews". > This seems reasonable, especially if it stays relatively unobtrusive. It would be bad to punish those who contribute great patches but only have time to contribute, not necessarily review, and could motivate reviewers who don't or can't often contribute to critical fixes but would like their work added to the base. In the end, though, one would have to see how it worked. If this ordering trumped the current "urgency" ordering and then things that were urgent didn't get reviewed, that would be bad, too. > >> cannot earn review points and cannot get his code in. On the other > >> hand, others collect a lot of review points but do not code. So, there > >> must be a way to trade points... !? Everything is fungible, you mean... maybe we could trade them for WoW money. Or maybe it could be Sage points, like AMS points, and you could use them to get a free copy of Sage. - kcrisman -- 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 unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: code review tools
On Apr 14, 2010, at 11:09 AM, Robert Miller wrote: That could backfire - people may decide to review tickets they might not otherwise feel confident about reviewing. If I don't feel like reviewing a ticket with high "karma" but I do care about one with low karma, then I would review zero tickets instead of one, and be irritated that I could not help get the code I care about merged. I hope no one's suggesting a system that would prevent tickets with low karma from being reviewed, rather it would just encourage review of higher-karma tickets. - 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 To unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: code review tools
On Wed, Apr 14, 2010 at 11:08 AM, Robert Bradshaw wrote: > On Apr 14, 2010, at 10:52 AM, Harald Schilly wrote: > >> On Apr 14, 6:23 pm, "Dr. David Kirkby" >> wrote: >>> >>> That could backfire - people may decide to review tickets they might not >>> otherwise feel confident about reviewing. > > That's a good point. Fortunately, all the people I've met in the Sage > community only want to let good code it, and hopefully it isn't rigid enough > to provide motivation to cheat the system. > >> You are right, that could be a problem and it's also a "closed game". >> If there are no new tickets with unreviewed code, > > Wow, that'll be a nice day :) > >> a new developer >> cannot earn review points and cannot get his code in. On the other >> hand, others collect a lot of review points but do not code. So, there >> must be a way to trade points... !? > > > I think something as simple as sorting the "tickets needing review" by > author karma would be useful without being overly complicated or formal. The Yes, that's exactly what I was thinking of. If somebody referees a lot of patches, then they automatically get singled out as "somebody whose code contributions are extra deserving of reviews". There are 134 tickets that need review right now. If I were to allocate 30 minutes to reviewing something, it would be great if I could start by reviewing something written by somebody who has lots of review karma. -- William > top karma earner per release could also be announced as part of the release > notes. > > - 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 > > To unsubscribe, reply using "remove me" as the subject. > -- William Stein 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: code review tools
On Apr 14, 2010, at 10:52 AM, Harald Schilly wrote: On Apr 14, 6:23 pm, "Dr. David Kirkby" wrote: That could backfire - people may decide to review tickets they might not otherwise feel confident about reviewing. That's a good point. Fortunately, all the people I've met in the Sage community only want to let good code it, and hopefully it isn't rigid enough to provide motivation to cheat the system. You are right, that could be a problem and it's also a "closed game". If there are no new tickets with unreviewed code, Wow, that'll be a nice day :) a new developer cannot earn review points and cannot get his code in. On the other hand, others collect a lot of review points but do not code. So, there must be a way to trade points... !? I think something as simple as sorting the "tickets needing review" by author karma would be useful without being overly complicated or formal. The top karma earner per release could also be announced as part of the release notes. - 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 To unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] Re: code review tools
>> That could backfire - people may decide to review tickets they might not >> otherwise feel confident about reviewing. If I don't feel like reviewing a ticket with high "karma" but I do care about one with low karma, then I would review zero tickets instead of one, and be irritated that I could not help get the code I care about merged. -- Robert L. Miller http://www.rlmiller.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 To unsubscribe, reply using "remove me" as the subject.
[sage-devel] Re: code review tools
On Apr 14, 6:23 pm, "Dr. David Kirkby" wrote: > That could backfire - people may decide to review tickets they might not > otherwise feel confident about reviewing. You are right, that could be a problem and it's also a "closed game". If there are no new tickets with unreviewed code, a new developer cannot earn review points and cannot get his code in. On the other hand, others collect a lot of review points but do not code. So, there must be a way to trade points... !? I think of something else. Everybody gets 10 points, then you can vote on tickets. And once a ticket is in, you get your points back. That would give a sense which tickets are important. 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 To unsubscribe, reply using "remove me" as the subject.
Re: [sage-devel] code review tools
William Stein wrote: I've also been thinking of instituting a "karma system", where you get Karma for doing reviews. Moreover, people who submit a lot of code for inclusion and don't do reviews... will have the lowest priority for getting their code reviewed. -- William That could backfire - people may decide to review tickets they might not otherwise feel confident about reviewing. But they will choose to review them, in order their own code gets reviewed. I can understand your dilemma, and I don't claim to know any magic answer to it, but I think you should think that idea out carefully first before implementing 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 To unsubscribe, reply using "remove me" as the subject.
[sage-devel] Re: Inserting Images into Notebook - upload dialog
Thanks guys. I eventually did the following combination of my first
attempt and your suggestions.
Upload the image file as people suggested using the data menu.
And then I inserted the image in a text entry box, using the "Insert/
edit image" button, and using just the file name for the URL.
The funny thing is that in my first attepts, I was thinking "I wish
sage had an option to upload data files into the sage server system."
o.O
Joal Heagney
On Apr 13, 9:57 am, Alec Mihailovs wrote:
> On Apr 12, 4:49 pm, William Stein wrote:
>
> > On Monday, April 12, 2010, Alec Mihailovs wrote:
>
> > > from shutil import copy
> > > copy('/home/excetera.png', '.')
>
> > Using DATA explicitly and shutil is not necessary. Just upload the
> > file foo.png as you say, then use it in the tag directly and it
> > should just work.
>
> Yes, if a file is uploaded, then it could be used as html(' src=excetera.png/>')
>
> What I wrote (with shutil, but without DATA), works directly, without
> uploading, and without using html. An interesting thing is that after
> that is done, and theimageis copied to one of cells (but without
> uploading), it still can be used in an html tag from another cell just
> referring to its name - same as if it was uploaded.
>
> Alec
--
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 unsubscribe, reply using "remove me" as the subject.
