[sage-devel] Any chance of access to OS X which defaults to 32-bit ?
Is there anyone that can provide me access to a OS X machine which defaults to building 32-bit executable, but can build 64-bit executables? Ideally a machine that has been used to compile 64-bit executables of Sage. There's a lot of code in Sage which has something like this in it: if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then # OS X 64-bit hacks on OS X fi In Numpy, there's a 64-bit hack which looks pretty alful to me. # numpy's distutils is buggy and runs a conftest without # taking CFLAGS into account. With 64 bit OSX this results # in *boom* if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then echo "64 bit MacIntel: copying fake gcc" rm $SAGE_LOCAL/bin/gcc cp gcc_fake $SAGE_LOCAL/bin/gcc chmod 755 $SAGE_LOCAL/bin/gcc fi then later this fake gcc gets deleted. if [ `uname` = "Darwin" -a "$SAGE64" = "yes" ]; then echo "64 bit MacIntel: deleting fake gcc" rm $SAGE_LOCAL/bin/gcc fi I think a much simpler solution is just to set CC="gcc -m64" export CC and that's it. No messing around with fake gccs. But I'd like access to an OS X machine which defaults to 32-bit, but can build 64-bit, in order that I can test this. Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Help us test Cython?
Hi all, So we're currently working on a long-overdue release of Cython with all kinds of snazzy new features. However, our automated testing system seems to keep turning up sporadic segfaults when running the sage doctest suite. This is obviously bad, but we're having a hard time reproducing this -- they seem to be *very* occasional failures while starting up sage, and thus far the only consistent appearance has been *within* our automated testing system (hudson). We've got a pile of dumped cores, which have mostly led us to the conclusions that (1) the problem occurs at a seemingly random point, so we should suspect some sort of memory corruption, and (2) sage does a *whole* lot of stuff when it starts up. ;) So we'd love to see if other people see these same failures. Anyone want to try out the new cython? You can grab all the files you need here: http://sage.math.washington.edu/home/craigcitro/cython-0.13-beta/ There's a new spkg and 6 patches against the sage library. You can add the patches, sage -i the spkg, and then do a sage -ba, and voila! you should have a sage running the bleeding edge cython. (If that doesn't build, it means I forgot some patch somewhere -- there's a working sage-4.4.4 with the new cython in /scratch/craigcitro/cy-work/fcubed on sage.math if anyone wants to root around.) After that, run the full test suite as many times as you're willing, hopefully with and without parallel doctesting (i.e. sage -tp). Then let us know what you turn up -- lots of random failures, or does everything pass? Points for machines we can ssh into and generated core files (ulimit -c unlimited), and even more points for anyone seeing consistent/repeatable failures. I'd also be very interested of reports that you've run the test suite N times with no failures. -cc -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: multivariate power series with rmpoly
Hi, I think both the links are pointing to the same patch, which I've been working on recently--thanks for taking a look! To get the patch from trac to work, I think you need to use mercurial; there are some instructions in the sage developer guide, but in case you don't feel like going through all that I've put the two files online at http://www.math.uga.edu/~njohnson/sage-code/multi_power_series_ring.py and http://www.math.uga.edu/~njohnson/sage-code/multi_power_series_ring_element.py It should work to just read them into a sage session, but let me know if you have trouble. The times for your code look great! If I understand correctly, the left column is from the trac patch, the middle is your code in python, and the right is your code modified to run in sage. I suspect that if you run all the tests on the same machine, the timings for your code will look even better, but maybe you could let us know if that's not the case. Could your code extend to work over other base rings? For those interested, the email link from Mario's first post contains timing comparisons between the trac patch and magma, with the general conclusion that the trac patch performs better than Magma in several cases, especially when the total degree is larger than a few hundred. -Niles -- 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] Report from useR! 2010
On Wed, Jul 28, 2010 at 11:55 AM, kcrisman wrote: > Dear all, > > I recently got back from useR! 2010, the R user conference. This was > the second time the conference was held in the US, this time at NIST > (a government agency in suburban DC). > > The most important thing for Sage folks is probably the talk I gave: > http://www.sagenb.org/home/pub/2270/ The reception was very positive, > and I hope that will lead to some future collaboration, or at the very > least higher awareness of Sage in the R community. They really liked > interacts - no surprise - and that it was painless to download R > packages, even in the notebook! So good results - especially > considering I was only there for 24 hours. > > However, there were some very intriguing things I gleaned from the > various talks and the overall atmosphere. I'll try to summarize these > below. > > ++ > > First, the community was clearly a community, and a large and healthy > one. There were probably 400-500 attending from all over the world, > from government, industry, health fields, corporations, analytics, and > of course academia, though this last was not even a plurality, I > think. People knew each other, and many were people *not* in the > academy who were connected to R via R user groups (see > http://blog.revolutionanalytics.com/local-r-groups.html), which > apparently are pretty common and for which people actually get > together to learn about R and socialize on a regular basis. > > And on the plus side, long-time users agreed that 10 years ago R was > pretty small, and now it's just been exploding. So I think it is > quite likely "the time is right" for other open source solutions of > the third wave (or whichever wave this is). What else can Sage do to > promote community outside of the Sage Days type participants? Let's start users groups! For the first year of Sage development, I actually was very active in the Boston (and San Diego) Python user groups, and gave a lot of talks about Sage. Those people were great. Maybe the time is right (and ripe). > > ++ > > Second, there was some very frank discussion of R's shortcomings (as > good as it is) which might be relevant to Sage - sometimes making Sage > look ahead of the curve, other places not. I'll try to categorize > them. > > 1. The corporate perspective. Essentially, many people made the point > (including from Merck, P&G, Ancestry.com, and Facebook) that R is > great, but concerns about tech support, varying stability of packages, > integration with MS Office, etc. yield many companies to have R under > the hood but not in interactions with VPs or other end users. One big > solution to that is that several companies have started up to offer > supported R solutions, either to train new users or to provide > specific commercial support to specific versions of R. They are > apparently doing well! > > I see this as relevant to Sage in a number of ways, but certainly when > it comes to potential engineering users and schools hesitant to/unable > to set up their own Sage servers. Big +1. > > 2. Speed and scalability. These are of course related to the previous > one from the org perspective, but also bring technical challenges. In > particular, several people mentioned in talks that R needs to be much > more scalable to HUGE data sets, performance needs to improve, and R > is slow. There were several things in the works with this last > thing - include something like Cython, and others not - and there is > also work on things like using multiple cores *intelligently* (since > it slows some stuff down a lot) and enabling arbitrary size input by > avoiding memory, etc. Performance issues are important in real-time > environments. > > Several people were very interested in Cython when I pointed it out, > and I think we are ahead because Python has some parallelization > stuff, right? But it was clear that this kind of thing is a big issue > in the big picture. Cython kicks aRse speedwise. And at least Python *has* threads -- even with the GIL it can be much better than R for dealing with IO -- at least that's how it appeared from a paper I read on difficulties of using R for some realtime trading. > 3. Don't be too clever. This was less often mentioned, but the sense > was that R is so good for graphics and visualization that sometimes > things are too informative, and post-processing is needed for the end > user. > > I don't think this happens with graphics per se in Sage, but sometimes > it is true that things get clever in Sage too, I suspect. Any > examples of end users being confounded by this? > > ++ > > Finally, there was a good talk by an R blogger about promotion in > general and blogging in particular. See for example > http://www.r-bloggers.com/ > . I think that especially Fredrik, Minh, and Martin have done a good > job with this, but we can do more. In retrospect, the little Sage > stickers at the Joint Meetings were just this sort of t
Re: [sage-devel] ALGLIB spkg is released (second version)
On Thu, Jul 29, 2010 at 10:25 AM, Sergey Bochkanov wrote: > Hello, Carl. > > Here is some documentation about Python-ALGLIB interface (called > X-interface in this document): > > http://www.alglib.net/share/2010-07-26-alglib-for-sage/x-interface.pdf Thanks. > It is very short, but should give a hint about meaning of all these > functions, expectations, functionality and etc. It describes functions > which are located in the _alglib.py unit. > > I'll add more information and some case studies later, but I thin > kthat it is better to post early than to post later :) Sure; unfortunately, I probably won't be able to work on this until Monday. Carl -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: multivariate power series with rmpoly
Hi! On 30 Jul., 01:03, Bill Hart wrote: > The original Sage code from the googlegroups/trac message you link to > doesn't seem to work in current sage any more. I couldn't find a > multivariable power series ring in the reference manual either, but > may not have been looking hard enough. I think multivariate power series are not in Sage, yet. But there is a trac ticket, and the code seems to provide very good timings (but needs some polishing): http://trac.sagemath.org/sage_trac/ticket/1956 It is an old ticket, but the patch is quite recent (and it reminds me that I wanted to review it, so, thank you...) Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: multivariate power series with rmpoly
The original Sage code from the googlegroups/trac message you link to
doesn't seem to work in current sage any more. I couldn't find a
multivariable power series ring in the reference manual either, but
may not have been looking hard enough.
Doing these computations in Sage generically, seems to take forever.
Actually the raising to the power takes no time, but the inverse
doesn't seem to know what it's doing.
However Pari does them instantly, and we have Pari in Sage. (But I
only checked the first benchmark in the list and that Pari gave the
right answer for it.)
I don't know if Pari does series reversion or not. I couldn't see it
in the help menu, though I also didn't look hard.
How do the timings for your code compare to Magma. I was confused
about the benchmarks you gave, and couldn't tell which ones were from
your code and which were from elsewhere. I see three columns of
timings. Which ones are yours? I think the first column is from an old
version of Sage as reported on Trac, right? But I didn't understand
the other columns.
I'm curious how you are getting good timings in Pure python? Is it a
new/clever algorithm? How does it fare for longer power series? Are
there even good algorithms that are asymptotically fast for these
sorts of problems? And can some of these be reduced to ordinary
multivariate polynomial computations?
Bill.
On 29 July, 15:26, mario wrote:
> Hello,
> I started rmpoly (http://code.google.com/p/rmpoly/),
> a pure Python library for multivariate polynomials and power series on
> QQ.
>
> I tried the benchmarks on series truncated with the total degree
> inhttp://www.mail-archive.com/sage-t...@googlegroups.com/msg42090.html
> MPowerSeriesRing (MSR) with Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
> rmpoly with Intel Core2 Quad Q8200 2.33GHz
> Python2.7, gmpy.mpq (left), Sage 4.0.1, Rational (right)
>
> seconds
> MSR rmpoly expression
> 3.18 0.58 1.24 (1 + 2*a + 3*b + 4*d + L(0).O(16))^-5
> 0.02 0.01 0.01 (1 + a^3 + b^3 + c^4 + d^4 + L(0).O(15))^-20
> 0.16 0.07 0.12 (-1/6*b^6*d^14 - 1/9*a^4*b^10*c^4*d^12 +...+
> L(0).O(50))^20
> 12.7 0.57 1.21 (1 + 1/2*a + 3*b + 4*a*b + ... + Z(0).O(30))^-20
> 0.05 0.001 0.002 (1+a^14*b^9+8/3*a^22*b^11-...+Z(0).O(51))^-20
> 1.9 0.4 1.03 (1 + a + b + a*b + a^2 + b^2 + Z(0).O(30))^-20
> 2.78 0.42 1.09 (1 + a + 2*b - a*b + 3*a^2 - b^2 + Z(0).O(30))^-20
> 3.14 0.42 1.10 (1+a+12*b-10*a*b+13*a^2-7*b^2+Z(0).O(30))^-20
>
> I do not know how to get and run the code multi_power_series from
> trac,
> so I put the times for MPowerSeriesRing from the link above.
>
> The Sage version of rmpoly is obtained essentially replacing int with
> Integer in the Python version. Here is the code for the first
> benchmark
>
> load "rmpoly.sage"
> rp = RPoly(['d','c','b','a'], 10,Rational,'grlex')
> d,c,b,a = rp.gens()
>
> # (1 + 2*a + 3*b + 4*d + L(0).O(16))^-5
> p = 1 + 2*a + 3*b + 4*d
> n = 16
> # n grlex order the variable _t carries the total degree
> p = p.series_inversion('_t',n)
> p = p.pow_trunc(5,'_t',n)
> print p
>
> Notice that the Python version of rmpoly is faster than its Sage
> version.
> I guess that cythonizing rmpoly.sage it would become roughly as
> fast as the Python version.
>
> rmpoly deals also with series with O(a^na*b*nb*c^nc*d^nd)
> e.g. with p.pow_trunc(k,['a','b','c','d'],[na,nb,nc,nd])
> It has multivariate series reversion: here is an example
>
> rp = RPoly(['w','z','y','x'],10,Rational)
> w,z,y,x = rp.gens()
> p = x*(2 + y^2 + z) + x^2*(1+y+z^6) + x^6*(5+y^6+z)
> n = nx=ny=nz=7
> p1 = p.series_reversion2('x',nx,['y','z'],[ny,nz],'w')
>
> # check that p in x=p1 is equal to w + O(w^nx*y^ny*z^nz)
> sb = Subs(rp,rp,{'x':p1})
> p2 = sb.subs_trunc(p,['w','y','z'],[nx,ny,nz])
> assert p2 == w
>
> The reversion takes 0.7s
>
> I would like to know if there is an interest in including
> rmpoly.sage in Sage as a possible way of computing with power series
>
> Mario
--
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] can sage -testall use threads?
On 07/29/2010 11:19 AM, kcrisman wrote: > That is, without setting NUM_THREADS or something. I tried > > ./sage -testall -p 8 > > but I just get lots of error messages in addition to my test output. > I guess I have the same question about sage -tnew as well. The 'sage -testall' and 'sage -tnew' operators invoke the scripts SAGE_LOCAL/bin/sage-maketest SAGE_LOCAL/bin/sage-test-new respectively. To run the tests, both scripts use 'sage -t', which calls the serial doctest runner SAGE_LOCAL/bin/sage-test Moreover, sage-test-new does not pass along command-line arguments. But it would be useful to generalize. I've opened http://trac.sagemath.org/sage_trac/ticket/9642 -- 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] domains for variables
sorry, wrong list.
Am 30.07.2010 00:01, schrieb Johannes:
> Hi list,
> i try to solve a linear equation in ZZ in the variables w_i:
>
> sage: variables = [var("w" + str(i),domain=ZZ)for i in range(s.nvertices())]
> sage: eq
> (w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3)
> sage: result
> [w0 == 15/2*r548, w1 == 5*r548, w2 == 3/2*r548, w3 == r548]
>
> up to here it's ok, but now im lookin for the smalest integer r548 > 0
> solving this equatoins. in other words, the smalest r548 such that every
> wi is in ZZ.
> How can i do this?
>
> Johannes
>
>
--
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] domains for variables
Hi list,
i try to solve a linear equation in ZZ in the variables w_i:
sage: variables = [var("w" + str(i),domain=ZZ)for i in range(s.nvertices())]
sage: eq
(w0 + w1 + w2 - 14*w3, w1 + 2*w2 - 8*w3, 2*w2 - 3*w3)
sage: result
[w0 == 15/2*r548, w1 == 5*r548, w2 == 3/2*r548, w3 == r548]
up to here it's ok, but now im lookin for the smalest integer r548 > 0
solving this equatoins. in other words, the smalest r548 such that every
wi is in ZZ.
How can i do this?
Johannes
--
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: new keywords for limit()
> > > > [X] minus/plus > > > > > [X] '-'/'+' > > > > > [ ] below/above > > > > > [X] left/right > > > > > [ ] from_left/from_right > > > > My votes are the same as Rob's. > > Also my votes are the same as Rob's :) > Ditto. 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
[sage-devel] Re: new keywords for limit()
On 29 čnc, 18:39, Jason Grout wrote: > On 7/29/10 9:22 AM, Rob Beezer wrote: > > > I'm going to undiplomatically poison the well as I'll be offline for > > the next few days. I like minus/plus and '-'/'+' as a package, like > > left/right, and would not miss below/above. With good documentation, > > I'm less concerned about clutter. > > > [X] minus/plus > > > [X] '-'/'+' > > > [ ] below/above > > > [X] left/right > > > [ ] from_left/from_right > > My votes are the same as Rob's. Also my votes are the same as Rob's :) Robert Marik > > Thanks, > > 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
[sage-devel] Re: new keywords for limit()
> > Burcin, earlier you said that there wouldn't be any tab completion for > "from_left" and "from_right." Why is that? Does this have to do with > my patch or how Sage handles tab completion? Is the default syntax > for a given command the only one that shows up for tab completion? > I think (I may be misinterpreting) that the point was sage: lim[tab] won't give you the various options, and sage: lim(f,x=c,dir=[tab] doesn't work as Sage is currently constructed. Someone would have to look at sage: lim? which perhaps is the best result in any case :) - 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
[sage-devel] wiki syntax in notebook?
Please forgive my ignorance is this is a stupid question. When creating worksheets in a Sage notebook, I often find myself wishing that I could type text in the tinyMCE editor using wiki-syntax (any would do fine) instead of using the current editor and occasionally having to go to the HTML view and then searching the web for HTML syntax that I can never remember. Is this possible? Is it desirable? It sure seems like it would be easier and faster, but perhaps I don't know what I'm talking about (probably). Dana -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: new keywords for limit()
> > [X] minus/plus > > > [X] '-'/'+' > > > [ ] below/above > > > [X] left/right > > > [ ] from_left/from_right > > My votes are the same as Rob's. Ditto. Burcin, earlier you said that there wouldn't be any tab completion for "from_left" and "from_right." Why is that? Does this have to do with my patch or how Sage handles tab completion? Is the default syntax for a given command the only one that shows up for tab completion? FWIW, I don't think anyone that already understands one-sided limits would be confused by using "left" instead of "from_left". My original choice in syntax was motivated by students that are learning one-sided limits for the very first time. I've had plenty of students confused (albeit only briefly) about what the notation of one-sided limits really means. I'm not advocating sticking with my original choice of keywords, but rather just explaining my initial point of view. Thanks for all the discussion! (I never thought such a small thing would generate so much discussion.) Dana -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: sage -clone failing with "...untrusted file/user..." message
Part 3, point #3 at http://hub.opensolaris.org/bin/view/Community+Group+on/2008080405 says: "you can put a [trusted] section into your own .hgrc" Not a good solution universally, but maybe it will make a clone happen for you? On Jul 29, 8:11 am, Dima Pasechnik wrote: > I tried on couple of other systems, and got pretty much the same > problem. > All is needed is to be logged in as an ordinary user, different from > the one owning the sage > installation. The following is on my laptop (sage install owned by > dima, and logged in as guest) > > gu...@pasechnik1:~/test$ sage -clone test > Now cloning the current Sage library branch... > hg clone sage sage-test > Not trusting file /usr/local/src/sage/sage-4.5.1/devel/sage-main/.hg/ > hgrc from untrusted user dima, group dima > abort: Permission denied: sage-test > Error cloning > ... > > Dima > > On Jul 28, 7:57 pm, Rob Beezer wrote: > > > I just saw this yesterday. I had installed Sage from source as a > > normal user (myself), but then began messing around while in a shell > > as root (oops). If I recall right, the first thing I did was > > > hg qinit > > > and then as a result several files had their ownership change to root > > and I started to see the "Not trusting..." message. When I restored a > > few files to the right ownership (fncache being one) all was well and > > the message went away. > > > Maybe poke around in devel/sage/.hg and see who owns what? > > > Rob > > > On Jul 28, 5:07 am, Dima Pasechnik wrote: > > > > Dear all, > > > any idea what to do with this: > > > > d...@sage:/scratch/dima$ sage -clone testcvxopt > > > Now cloning the current Sage library branch... > > > hg clone sage sage-testcvxopt > > > Not trusting file /usr/local/sage/devel/sage-main/.hg/hgrc from > > > untrusted user mvngu, group mvngu > > > abort: Permission denied: sage-testcvxopt > > > Error cloning > > > > real 0m0.091s > > > user 0m0.070s > > > sys 0m0.010s > > > d...@sage:/scratch/dima$ > > > > Thanks, > > > Dima -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Are these bugs?
In characteristic 0 are there problems: sage: T=SR(pAdicField(5)(1/3)) sage: T.pyobject() 2 + 3*5 + 5^2 + 3*5^3 + 5^4 + 3*5^5 + 5^6 + 3*5^7 + 5^8 + 3*5^9 + 5^10 + 3*5^11 + 5^12 + 3*5^13 + 5^14 + 3*5^15 + 5^16 + 3*5^17 + 5^18 + 3*5^19 + O(5^20) (fair enough - it just gets wrapped) sage: T=SR(pAdicField(5)['x']([1/3])) sage: T.pyobject() [same thing sage: T=SR(pAdicField(5)['x']([1/3,1])) TypeError: [sic -- really just a blank type-error] sage: f=(exp(SR(pAdicField(5)(1/3))*x+x^2)+exp(RR(1.0)*x^2)).diff() sage: f(x=5) 10*e^25 + 2 + 4*5 + 4*5^2 + 3*5^3 + 2*5^4 + 3*5^5 + 4*5^6 + 4*5^7 + 5^9 + 3*5^10 + 2*5^11 + 3*5^13 + 2*5^14 + 4*5^15 + 5^16 + 2*5^17 + 4*5^19 + O(5^20) -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: Are these bugs?
On Jul 29, 9:51 am, Simon King wrote: > 4) > sage: SR(p) > BOOM shouldn't there at least be some consistency in the *characteristic* of the symbolic ring? I can see how someone might want to make a "symbolic ring of characteristic p", but mixing different characteristics can't possibly lead to good things. sage: T=exp(SR(GF(5)['x']([1,2,3])))+exp(SR(GF(7)['x']([3,6]))) sage: T.operands()[0].operands()[0].operands()[1].pyobject().parent() Finite Field of size 7 sage: T.operands()[1].operands()[0].operands()[1].pyobject().parent() Finite Field of size 5 sage: T(x=1) 10.1073379273897 sage: D=T.diff(x) sage: D(x=1) TypeError: unsupported operand parent(s) for '*': 'Finite Field of size 5' and 'Real Field with 53 bits of precision' so, regarding 4) I'd say the bug is that not more things say BOOM. Incidentally, number fields also do no coerce into SR: sage: K.=NumberField(x^2+3) sage: SR(K['y']([1,2,r+1])) TypeError: unsupported operand parent(s) for '*': [...] so that non-primitive finite fields do not coerce into SR is at least consistent with that. -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] ALGLIB spkg is released (second version)
Hello, Carl. Here is some documentation about Python-ALGLIB interface (called X-interface in this document): http://www.alglib.net/share/2010-07-26-alglib-for-sage/x-interface.pdf It is very short, but should give a hint about meaning of all these functions, expectations, functionality and etc. It describes functions which are located in the _alglib.py unit. I'll add more information and some case studies later, but I thin kthat it is better to post early than to post later :) -- With best regards, Sergey mailto:sergey.bochka...@alglib.net -- 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] Are these bugs?
Hi! While trying to answer some post on sage-support I found the following four problems. Definitions: sage: R. = GF(2^4) sage: P. = R[] sage: C = [t, t + 1, t^3 + t + 1, t^3 + 1, t^3 + t^2] sage: p = P(C) Do you agree that these are bugs? 1) When doing P?, the documenation of P.__call__ is included. But of course, P.__call__ is generic, so it doesn't say anything specific. Wouldn't it be better to include the documentation of P._element_constructor_ instead? 2) sage: P? TESTS: sage: from sage.rings.polynomial.polynomial_ring import PolynomialRing_field as PRing sage: R = PRing(QQ, 'x'); R Univariate Polynomial Ring in x over Rational Field sage: type(R.gen()) sage: R = PRing(QQ, 'x', sparse=True); R Sparse Univariate Polynomial Ring in x over Rational Field sage: type(R.gen()) sage: R = PRing(CC, 'x'); R Univariate Polynomial Ring in x over Complex Field with 53 bits of precision sage: type(R.gen()) etc. This is not really a documentation. 3) P._element_constructor_? does not mention that one can call P with a list of coefficients (as I did above in the definition of the polynomial p). 4) sage: SR(p) BOOM Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Re: new keywords for limit()
On 7/29/10 9:22 AM, Rob Beezer wrote: I'm going to undiplomatically poison the well as I'll be offline for the next few days. I like minus/plus and '-'/'+' as a package, like left/right, and would not miss below/above. With good documentation, I'm less concerned about clutter. [X] minus/plus [X] '-'/'+' [ ] below/above [X] left/right [ ] from_left/from_right My votes are the same as Rob's. Thanks, 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
[sage-devel] Re: new keywords for limit()
I'm going to undiplomatically poison the well as I'll be offline for the next few days. I like minus/plus and '-'/'+' as a package, like left/right, and would not miss below/above. With good documentation, I'm less concerned about clutter. [X] minus/plus [X] '-'/'+' [ ] below/above [X] left/right [ ] from_left/from_right Rob -- 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] can sage -testall use threads?
That is, without setting NUM_THREADS or something. I tried ./sage -testall -p 8 but I just get lots of error messages in addition to my test output. I guess I have the same question about sage -tnew as well. Thanks, - 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
[sage-devel] Re: new keywords for limit()
A rough summary so far. Correct me if you think I have not read comments correctly. Status quo is below/above and minus/plus and a patch to add from_left/from_right. * left/right is preferable to from_left/from_right * a suggestion to deprecate below/above, with no objections, and some support * support for '-'/'+', maybe augmenting minus/plus as "shortcuts" of a sort (modulo keyboard dashes/hyphens/etc) And a chance to vote. Mark exactly those options you would like to see as the complete set of possibilites for the 'dir' keyword on limit(). Not marking is tantamount to not adding it, or deprecating it if it already exists. Remember, the original motivation for this thread was to "not clutter things up by supporting many different ways of doing the same thing." [ ] minus/plus [ ] '-'/'+' [ ] below/above [ ] left/right [ ] from_left/from_right -- 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: new keywords for limit()
I suppose python takes care of this, or else the minus sign would cause some issues. For future reference to those who write LaTeX, you can use various hyphens depending on whether or not you want line-breaking. (I.e., so "line-breaking" can or cannot be split between lines at the hyphen.) I've tested this a bunch. They all look the same in the charter font I use, but U+002D (from my keyboard) will break after (except when placed after a number), U-2014 will break both before and after, and U+2011 will not break at all. Jason On Thu, Jul 29, 2010 at 1:51 AM, Jason B Hill wrote: > > > > +1 on the '+' and '-'. If we had that syntax, that's what I'd teach my >> > students to use since they'd already be using it in the classroom. >> > > I'm +1 here too. I'm just paranoid and wondering if non-English/American > keyboard layouts will provide one of the 9+ unicode hyphen characters that > isn't identical to my American "-". (Some hyphens are breaking, some > aren't... etc. Various keyboard layouts reflect the language's usage.). Is > this an issue? > > 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
[sage-devel] Re: sage -clone failing with "...untrusted file/user..." message
I tried on couple of other systems, and got pretty much the same problem. All is needed is to be logged in as an ordinary user, different from the one owning the sage installation. The following is on my laptop (sage install owned by dima, and logged in as guest) gu...@pasechnik1:~/test$ sage -clone test Now cloning the current Sage library branch... hg clone sage sage-test Not trusting file /usr/local/src/sage/sage-4.5.1/devel/sage-main/.hg/ hgrc from untrusted user dima, group dima abort: Permission denied: sage-test Error cloning ... Dima On Jul 28, 7:57 pm, Rob Beezer wrote: > I just saw this yesterday. I had installed Sage from source as a > normal user (myself), but then began messing around while in a shell > as root (oops). If I recall right, the first thing I did was > > hg qinit > > and then as a result several files had their ownership change to root > and I started to see the "Not trusting..." message. When I restored a > few files to the right ownership (fncache being one) all was well and > the message went away. > > Maybe poke around in devel/sage/.hg and see who owns what? > > Rob > > On Jul 28, 5:07 am, Dima Pasechnik wrote: > > > > > Dear all, > > any idea what to do with this: > > > d...@sage:/scratch/dima$ sage -clone testcvxopt > > Now cloning the current Sage library branch... > > hg clone sage sage-testcvxopt > > Not trusting file /usr/local/sage/devel/sage-main/.hg/hgrc from > > untrusted user mvngu, group mvngu > > abort: Permission denied: sage-testcvxopt > > Error cloning > > > real 0m0.091s > > user 0m0.070s > > sys 0m0.010s > > d...@sage:/scratch/dima$ > > > Thanks, > > Dima -- 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] multivariate power series with rmpoly
Hello,
I started rmpoly (http://code.google.com/p/rmpoly/),
a pure Python library for multivariate polynomials and power series on
QQ.
I tried the benchmarks on series truncated with the total degree in
http://www.mail-archive.com/sage-t...@googlegroups.com/msg42090.html
MPowerSeriesRing (MSR) with Intel(R) Xeon(R) CPU X7460 @ 2.66GHz
rmpoly with Intel Core2 Quad Q8200 2.33GHz
Python2.7, gmpy.mpq (left), Sage 4.0.1, Rational (right)
seconds
MSR rmpoly expression
3.18 0.58 1.24 (1 + 2*a + 3*b + 4*d + L(0).O(16))^-5
0.02 0.01 0.01 (1 + a^3 + b^3 + c^4 + d^4 + L(0).O(15))^-20
0.16 0.07 0.12 (-1/6*b^6*d^14 - 1/9*a^4*b^10*c^4*d^12 +...+
L(0).O(50))^20
12.7 0.57 1.21 (1 + 1/2*a + 3*b + 4*a*b + ... + Z(0).O(30))^-20
0.05 0.001 0.002 (1+a^14*b^9+8/3*a^22*b^11-...+Z(0).O(51))^-20
1.9 0.4 1.03 (1 + a + b + a*b + a^2 + b^2 + Z(0).O(30))^-20
2.78 0.42 1.09 (1 + a + 2*b - a*b + 3*a^2 - b^2 + Z(0).O(30))^-20
3.14 0.42 1.10 (1+a+12*b-10*a*b+13*a^2-7*b^2+Z(0).O(30))^-20
I do not know how to get and run the code multi_power_series from
trac,
so I put the times for MPowerSeriesRing from the link above.
The Sage version of rmpoly is obtained essentially replacing int with
Integer in the Python version. Here is the code for the first
benchmark
load "rmpoly.sage"
rp = RPoly(['d','c','b','a'], 10,Rational,'grlex')
d,c,b,a = rp.gens()
# (1 + 2*a + 3*b + 4*d + L(0).O(16))^-5
p = 1 + 2*a + 3*b + 4*d
n = 16
# n grlex order the variable _t carries the total degree
p = p.series_inversion('_t',n)
p = p.pow_trunc(5,'_t',n)
print p
Notice that the Python version of rmpoly is faster than its Sage
version.
I guess that cythonizing rmpoly.sage it would become roughly as
fast as the Python version.
rmpoly deals also with series with O(a^na*b*nb*c^nc*d^nd)
e.g. with p.pow_trunc(k,['a','b','c','d'],[na,nb,nc,nd])
It has multivariate series reversion: here is an example
rp = RPoly(['w','z','y','x'],10,Rational)
w,z,y,x = rp.gens()
p = x*(2 + y^2 + z) + x^2*(1+y+z^6) + x^6*(5+y^6+z)
n = nx=ny=nz=7
p1 = p.series_reversion2('x',nx,['y','z'],[ny,nz],'w')
# check that p in x=p1 is equal to w + O(w^nx*y^ny*z^nz)
sb = Subs(rp,rp,{'x':p1})
p2 = sb.subs_trunc(p,['w','y','z'],[nx,ny,nz])
assert p2 == w
The reversion takes 0.7s
I would like to know if there is an interest in including
rmpoly.sage in Sage as a possible way of computing with power series
Mario
--
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] is this kind of license Sage-compatible?
On Thursday, July 29, 2010, Dima Pasechnik wrote: > I guess it boils down to whether "should" means "must" here, or not. > Are there any means to decide, any precedents? > > (I can also contact authors and ask whether they might soften the > language...) Yes and you should definitely write to the FSF. > > Thanks, > Dima > > > On Jul 28, 9:43 pm, William Stein wrote: >> On Wed, Jul 28, 2010 at 11:30 AM, David Joyner wrote: >> > On Wed, Jul 28, 2010 at 12:46 PM, William Stein wrote: >> >> On Wed, Jul 28, 2010 at 8:52 AM, David Joyner wrote: >> >>> I think this is basically a modified BSD license, which is GPL >> >>> compatible. >> >> >> It has an additional condition that is not in the GPL: "Any >> >> publication resulting from research that made use of >> >> this software should cite this document." This might make it non-GPL >> >> compatible. >> >> > I view that as more of a request (as in "here is how to >> > cite DSDP...") than a legal requirement, but maybe I'm wrong. >> >> If it is a request, it's fine. If it is a legal requirement, then it >> definitely renders the software GPL-incompatible. >> If it's a legal requirement, then it is kind of similar to the >> "advertising must explicitly cite this component" clause of the >> original non-GPL-compatible BSD license. >> >> -- William >> >> >> >> >> >> >> >> >> William >> >> >>> On Wed, Jul 28, 2010 at 11:29 AM, Dima Pasechnik >> >>> wrote: >> http://www.mcs.anl.gov/hs/software/DSDP/Copyright.txt >> >> (C) COPYRIGHT 2004 UNIVERSITY OF CHICAGO >> >> This program discloses material protectable under copyright laws of >> the United States. >> Permission to copy and modify this software and its documentation is >> hereby granted, provided that this notice is retained thereon and on >> all copies or >> modifications. The University of Chicago makes no representations as >> to the suitability >> and operability of this software for any purpose. It is provided "as >> is"; without >> express or implied warranty. Permission is hereby granted to use, >> reproduce, prepare >> derivative works, and to redistribute to others, so long as this >> original copyright notice >> is retained. Any publication resulting from research that made use of >> this software >> should cite this document. >> >> [ truncated - there is more stuff...] >> >> Thanks, >> Dima >> >> -- >> 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 >> athttp://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 >> >>> athttp://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 >> >> athttp://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 >> > athttp://groups.google.com/group/sage-devel >> > URL:http://www.sagemath.org >> >> -- >> William Stein >> Professor of Mathematics >> University of Washingtonhttp://wstein.org > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- 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
[sage-devel] Re: is this kind of license Sage-compatible?
I guess it boils down to whether "should" means "must" here, or not. Are there any means to decide, any precedents? (I can also contact authors and ask whether they might soften the language...) Thanks, Dima On Jul 28, 9:43 pm, William Stein wrote: > On Wed, Jul 28, 2010 at 11:30 AM, David Joyner wrote: > > On Wed, Jul 28, 2010 at 12:46 PM, William Stein wrote: > >> On Wed, Jul 28, 2010 at 8:52 AM, David Joyner wrote: > >>> I think this is basically a modified BSD license, which is GPL compatible. > > >> It has an additional condition that is not in the GPL: "Any > >> publication resulting from research that made use of > >> this software should cite this document." This might make it non-GPL > >> compatible. > > > I view that as more of a request (as in "here is how to > > cite DSDP...") than a legal requirement, but maybe I'm wrong. > > If it is a request, it's fine. If it is a legal requirement, then it > definitely renders the software GPL-incompatible. > If it's a legal requirement, then it is kind of similar to the > "advertising must explicitly cite this component" clause of the > original non-GPL-compatible BSD license. > > -- William > > > > > > > > >> William > > >>> On Wed, Jul 28, 2010 at 11:29 AM, Dima Pasechnik > >>> wrote: > http://www.mcs.anl.gov/hs/software/DSDP/Copyright.txt > > (C) COPYRIGHT 2004 UNIVERSITY OF CHICAGO > > This program discloses material protectable under copyright laws of > the United States. > Permission to copy and modify this software and its documentation is > hereby granted, provided that this notice is retained thereon and on > all copies or > modifications. The University of Chicago makes no representations as > to the suitability > and operability of this software for any purpose. It is provided "as > is"; without > express or implied warranty. Permission is hereby granted to use, > reproduce, prepare > derivative works, and to redistribute to others, so long as this > original copyright notice > is retained. Any publication resulting from research that made use of > this software > should cite this document. > > [ truncated - there is more stuff...] > > Thanks, > Dima > > -- > 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 > athttp://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 > >>> athttp://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 > >> athttp://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 > > athttp://groups.google.com/group/sage-devel > > URL:http://www.sagemath.org > > -- > William Stein > Professor of Mathematics > University of Washingtonhttp://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: Wrong symbolic sum
On 07/29/10 02:12 PM, kcrisman wrote: I will point out, though, that you clearly *do* use Maxima, since you tried to do this in Sage, which uses Maxima heavily. One of the things Sage has gotten a lot better about is acknowledging use of all the many high-quality components, so let's all try to do a better job reporting things upstream. I know it's annoying - I have personally shoved off many matplotlib reports to Jason - but in the long run it will benefit Sage a lot if more of us get known upstream. - kcrisman As noted before, I'd like to see reporting bugs upstream as a necessary requirement for getting a positive review on tickets. It seems to me only a small percentage of bugs do get reported upstream. Making it mandatory, unless there is a very good reason for not doing so, would be sensible to me. In other words, authors of tickets should be able to show evidence where the bug was reported, who to and on what date. Reviers should not give a positive review until the ticket has a link to a bug report, or clear information about how it was reported. Obviously the above only applies to upstream bugs Dave -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Anyone know about this?
Apparently there is a new Sage forum (and other open source math software fora) out there, perhaps sponsored by whoever does Scilab: http://www.equalis.com/forums/posts.asp?topic=119819&; - 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
[sage-devel] Re: "is" and python integers
> > For me, I use "is" when comparing with None, and if I specifically want > *True* or *False* (e.g., if I don't want the empty list to count as False). > Yes, these were the sorts of situations I encountered. - 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
[sage-devel] Re: Two questions about sliders in interacts
Great, these are now #9638 and #9639. - kcrisman On Jul 29, 2:32 am, Jason Grout wrote: > On 7/28/10 11:31 AM, Harald Schilly wrote: > > > On Jul 28, 6:07 pm, kcrisman wrote: > >> 1) Endpoint markers for the sliders. > > > I think that was already requested some time ago, I'm not sure, and I > > think that's quite important. Something else I heard was to be able to > > change the color - i.e. to match it with the color of a plotted line. > > Both of those are great ideas and should be put up on trac. Hopefully, > there will be lots of development of the notebook and interacts in the > next few years, so we'll have a chance to really polish these things and > implement all of these great ideas. > > Thanks, > > 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
[sage-devel] Re: Wrong symbolic sum
On Jul 29, 3:38 am, Henryk Trappmann wrote: > On Jul 28, 5:47 pm, Burcin Erocal wrote: > > > Can you open a ticket about these problems with the binomial (including > > the "either m or x-m must be an integer" error mentioned in kcrisman's > > message? > > The bug in maxima for the evaluation of the sum should also be a > > separate ticket. > > I opened the 3 trac tickets: > #9633 > #9634 > #9635 Thanks. > However I neither know nor use Maxima, so I dont feel assigned to file > the bug to Maxima. This is now Maxima bug 3036579. I will point out, though, that you clearly *do* use Maxima, since you tried to do this in Sage, which uses Maxima heavily. One of the things Sage has gotten a lot better about is acknowledging use of all the many high-quality components, so let's all try to do a better job reporting things upstream. I know it's annoying - I have personally shoved off many matplotlib reports to Jason - but in the long run it will benefit Sage a lot if more of us get known upstream. - kcrisman - 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
[sage-devel] Re: Problems with TestSuite
Hi Simon and Florent, Let me answer you both in one post, since I think your solutions might be related. I agree with Simon that this is the offending line: tester.assert_(isinstance(self, self.parent().category().element_class)) Now, by adding the line Element = DifferentialForm to my parent class as Florent suggested, I tried to make it so that element_class refers to DifferentialForm. However, the assert still fails. Is there an example of a minimal code using the categories framework that I could adapt? I tried to find out where the problem might be by trying a standard type of element, but these problems persist: sage: u = polygen(QQ) sage: isinstance(u, u.parent().category().element_class) False In the meantime, I see that SteenrodAlgebra has also this problem Any ideas? All the best, Joris On 29 jul, 11:32, Florent Hivert wrote: > > everything works well (no output), but when I run F._test_elements() I > > get an error in ... _test_category(). The precise error is listed > > below, but the traceback tells me that the problem arose in > > element.pyx: > > > if not is_extension_type(self.__class__): > > # For usual Python classes, that should be done with > > # standard inheritance > > tester.assert_(isinstance(self, > > self.parent().category().element_class)) > > > Did I mess up with my use of the sage categories somewhere? Any help > > would be much appreciated, and I can readily supply additional > > information. > > Did you tell the parent what is the class of its elements ? Specifically when > creating a parent with the category framework you need either to write > > class MyParentClass(...): > ... > class Element(...): > ... > > Or else > > class MyElementClass(...): > ... > class MyParentClass(...): > ... > Element = MyElementClass > > Then the category framework create for you a dynamic class called > > MyParentClass.element_class > > Hope this helps, > > Cheers, > > Florent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
[sage-devel] Anyone updating spkg/standard/deps?
There are two very minor issues with the spkg/standard/deps file. Both are "cosmetic", in the sense they don't change the build order of any packages, but both will add a bit of clarity to the file. 1) R depends on Fortran, though that is not very clear. http://trac.sagemath.org/sage_trac/ticket/9464 Fortran is a dependency of lapack, lapack is a dependency of atlas, and atlas is a dependency of R. So fortran should always get installed before R. It's a bit convoluted though. 2) SAGETEX does not show a dependency on BASE, whereas every other package does. Again its implied by a chain, and somewhat less convoluted than the R/Fortran issue. http://trac.sagemath.org/sage_trac/ticket/9637 I'm not going to create new versions of deps, when there are tons more floating around just now. I think it will just make things even more complex. But if anyone is updating deps, those two are zero-risk changes and just add a bit of clarity. Just make a note on the ticket at #9637 -- 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] Problems with TestSuite
> everything works well (no output), but when I run F._test_elements() I > get an error in ... _test_category(). The precise error is listed > below, but the traceback tells me that the problem arose in > element.pyx: > > if not is_extension_type(self.__class__): > # For usual Python classes, that should be done with > # standard inheritance > tester.assert_(isinstance(self, > self.parent().category().element_class)) > > Did I mess up with my use of the sage categories somewhere? Any help > would be much appreciated, and I can readily supply additional > information. Did you tell the parent what is the class of its elements ? Specifically when creating a parent with the category framework you need either to write class MyParentClass(...): ... class Element(...): ... Or else class MyElementClass(...): ... class MyParentClass(...): ... Element = MyElementClass Then the category framework create for you a dynamic class called MyParentClass.element_class Hope this helps, Cheers, Florent -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
Re: [sage-devel] Re: new keywords for limit()
> +1 on the '+' and '-'. If we had that syntax, that's what I'd teach my > > students to use since they'd already be using it in the classroom. > I'm +1 here too. I'm just paranoid and wondering if non-English/American keyboard layouts will provide one of the 9+ unicode hyphen characters that isn't identical to my American "-". (Some hyphens are breaking, some aren't... etc. Various keyboard layouts reflect the language's usage.). Is this an issue? 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
[sage-devel] Re: Wrong symbolic sum
On Jul 28, 5:47 pm, Burcin Erocal wrote: > Can you open a ticket about these problems with the binomial (including > the "either m or x-m must be an integer" error mentioned in kcrisman's > message? > The bug in maxima for the evaluation of the sum should also be a > separate ticket. I opened the 3 trac tickets: #9633 #9634 #9635 However I neither know nor use Maxima, so I dont feel assigned to file the bug to Maxima. -- 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: can't -sdist a -bdist copy of Sage
For the record, I have a proposed solution for this at #9614. Dan -- --- Dan Drake - http://mathsci.kaist.ac.kr/~drake --- signature.asc Description: Digital signature
Re: [sage-devel] Cached function decorator interferes with documentation
On Wed, Jul 28, 2010 at 10:56 PM, Rob Beezer wrote: > It would appear that the �...@cached_function decorator prevents the > decorated function from appearing in the HTML reference manual. > Evidence is > > sage.functions.special.maxima_function() > sage.structure.dynamic_class.dynamic_class_internal() > sage.graphs.graph_latex.setup_latex_preamble() > > The �...@options decorator doesn't seem to have the same effect, for > example > > sage.graphs.generic_graph.graphplot() > > comes through into the documentation just fine. > > I couldn't find anything in Trac about this. Are there examples where > a cached function survives into the documentation? Thoughts on a > cause or a solution? Lazy imports do this: http://hg.sagemath.org/sage-main/file/426be7b253ad/sage/misc/lazy_import.py On that note, #8456 - enhancements to lazy import, is still in need of a review. -- 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: new keywords for limit()
On Wed, Jul 28, 2010 at 11:30 PM, Jason Grout wrote: > On 7/27/10 12:23 PM, D.C. Ernst wrote: > >> I'm not particularly in love with "from_*" and I am certainly >> agreeable to changing it (as suggested earlier or otherwise). Can we >> use the symbols "+" and "-"? This most closed mimics the standard >> notation and is concise. Thoughts? >> > > > +1 on the '+' and '-'. If we had that syntax, that's what I'd teach my > students to use since they'd already be using it in the classroom. '+'1, we're getting closer... :) - 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
