I think most time is spend in the is_zero() method for a symbolic
expression, and that the reassignments you refer to are largely irrelevant.
The thing is that it can cost a lot of time to decide whether, for example
sin(x)cos(x) - sin(2x)/2
is equal to zero, because there is so many things to
Op zaterdag 22 juni 2013 20:48:38 UTC+2 schreef William het volgende:
>
> For his conscientious and technically excellent work as Sage release
> manager, and his significant contributions to the Sage library, Jeroen
> Demeyer is awarded the 2013 Spies Prize.
>
> Gefeliciteerd Jeroen, helemaal ve
Hi everyone,
I just parallelized a for loop in a way that may be generally useful, and
I'm wondering whether I should write an addition to sage.parallel. It's
possible that this has been done already and in much better ways than my
own, so I'd be very happy to hear your opinions.
I had a for l
Op vrijdag 21 juni 2013 12:02:19 UTC+2 schreef Matthieu Deneufchâtel het
volgende:
>
> I created a sandbox, modified the file free_monoid_element.py then rebuilt
> the Sage library (see below) but the function I added is not known:
> sage: M=FreeMonoid(3,'x,y,z')
> sage: a = M.an_element()
> sage
Op maandag 22 april 2013 14:57:17 UTC+2 schreef Timo Kluck het volgende:
>
> No, it's about publishing a recent version of sage in a PPA (or in the app
> store) for ubuntu.
>
I should add: but this is not something I'm actually working on, it's
just what t
Op maandag 22 april 2013 14:52:15 UTC+2 schreef Felix Salfelder het
volgende:
>
> > I was
> > thinking of the idea of having sage-specific deb packages for sage's
> > foreign (often patched) modules. So maybe sage-gap, sage-maxima, et
> cetera,
> > which would install into /opt/sage.
>
> is t
> debian has already packages for most of the foreign packages, and this
> is totally unrelated to sage. what i need is just packages for the core
> modules (currently the directories in /src). my proposal
> is to handle all modules (foreign or not) alike, and add build systems
> where missin
Op maandag 22 april 2013 09:57:19 UTC+2 schreef Felix Salfelder het
volgende:
>
> do you see disadvantages in treating sage parts as modules?
>
> maybe it doesnt matter much, whether c_lib and scripts are in the same
> module or not, for distribution purposes it makes sense to have
> python-sa
Op dinsdag 12 maart 2013 14:24:02 UTC+1 schreef kcrisman het volgende:
>
>
> This also came up on a Facebook post with regard to the following
> (somewhat simplified):
>
> sage: var('x,y')
> (x, y)
> sage: A = vector([x])
> sage: B = vector([y])
> sage: A == B
> False
>
> I think it's possible f
Op dinsdag 12 maart 2013 13:23:20 UTC+1 schreef Jan Groenewald het volgende:
>
> sage: x == x
> x == x
> sage: x == 3
> x == 3
> sage: x=3
> sage: x == 3
> True
> sage: x == x
> True
>
> This one is only confusing in an interactive session. Sage defers checking
an expression for validity (and ca
Op dinsdag 12 maart 2013 13:18:43 UTC+1 schreef Jesus Torrado het volgende:
>
> On Tuesday, March 12, 2013 12:52:39 PM UTC+1, Harald Schilly wrote:
> If I may, I would suggest to implement, up to some point, symbolic tensor
> calculus, e.g. along the lines Mathematica does since v9:
> http://www.
Op zondag 10 maart 2013 19:40:41 UTC+1 schreef mmarco het volgende:
>
>
> > * noncommutative / supercommutative variables in expressions, (say pq -
> qp
> > = i)
>
> That is already supported in g-algebras. Look for the documentation of
> FreeAlgebra.g_algebra
>
> That looks great! It would b
Op vrijdag 8 maart 2013 10:43:43 UTC+1 schreef mmarco het volgende:
>
> IIRC, the call for projects of Google summer of code was last year
> around march or april. Should we start to get prepared for this?
>
> I think you're right that we should. One thing that I would like to have
in Sage is be
Op donderdag 7 maart 2013 20:04:56 UTC+1 schreef Robert Bradshaw het
volgende:
>
> There are several python-as-a-shell options out there, it would make
> sense to look at several and pick one.
>
> I agree. This plumbum was pointed out to me after I posted by own clumsy
attempt to the python-ide
Op woensdag 6 maart 2013 16:46:08 UTC+1 schreef Jeroen Demeyer het volgende:
>
> On 2013-03-06 16:23, Timo Kluck wrote:
> > you can
> > suddenly mix all that piping with with dictionaries, or any
> > other things in which python is superior to bash.
> This would pr
Op woensdag 6 maart 2013 15:06:08 UTC+1 schreef Jeroen Demeyer het volgende:
>
> On 2013-03-06 15:01, Timo Kluck wrote:
> > so that we could
> > start using Python scripts in many places were we use shell scripts now.
> > Think the packaging system
> We can't
Dear Sage enthusiasts,
I found this very interesting python package:
http://plumbum.readthedocs.org/en/latest/
I prefer Python for scripting in general, but in some cases a shell script
is just easier, especially if you want to call out to command line
utilities, pipe their output, et cetera.
Op maandag 4 maart 2013 22:36:33 UTC+1 schreef luisfe het volgende:
>
> Hi,
>
> Can any one enlight me about what is going on here?
>
> {{{
> sage: t=(1,2,3)
> sage: type(t)
> tuple
> sage: len(t)
> 3
> sage: len(t)=4
> sage: t
> t
> sage: type(t)
> sage.symbolic.expression.Expression
> }}}
>
It go
Op zondag 3 maart 2013 19:59:25 UTC+1 schreef leif het volgende:
>
> Timo Kluck wrote:
> > This target BlockDegLexOrderTest.o does not seem to be built at all in
> > the `sage -i` case, so it doesn't fail either. Is there something in the
> > environment that cont
If I install only
that one manually, the rest seems to work (I still have to run sage -t to
make sure).
> Francois
>
> On 4/03/2013, at 7:12, "Timo Kluck" >
> wrote:
>
>
> Op zondag 3 maart 2013 18:35:36 UTC+1 schreef François het volgende:
>>
Op zondag 3 maart 2013 18:35:36 UTC+1 schreef François het volgende:
>
> I know you have heard of lmona.de from Burcin. One of the thing that made
> lmona.de possible is the work of me and Christopher on the sage-on-gentoo
> overlay. Basically you are trying to duplicate our work that is already
Hi,
I'm hoping a polybori expert can quickly spot the difference between two
builds I'm doing of the spkg. I'm looking into how difficult it would be to
wrap the spkg system by Gentoo's portage for dependency resolution. (Hint:
it doesn't seem to be extremely difficult, this is the only thing I
Op woensdag 27 februari 2013 20:19:32 UTC+1 schreef Simon King het volgende:
>
> Hi Nils,
>
> On 2013-02-27, Nils Bruin > wrote:
>
> > Do we really want to test our random number generators for
> > deterministic behaviour? If so, the test should probably at least set
> > the seed prior to testi
Hi there,
I'm looking for someone who's familiar with Polybori to have a quick look
at the following ticket:
http://trac.sagemath.org/sage_trac/ticket/13767
The issue is that we're upgrading boost, and apparently, its random number
generator has slightly changed. Therefore, we have some failing
Op donderdag 17 januari 2013 13:30:45 UTC+1 schreef Dima Pasechnik het
volgende:
>
> No, not really. The bug fixes produced included
>
> * unmerging a particular commit in Maxima master,
> (by providing a corresponding patch in spkg),
> and this was purely Sage-specific.
> And for this
Op woensdag 16 januari 2013 12:51:29 UTC+1 schreef Snark het volgende:
>
> Le 16/01/2013 11:24, Volker Braun a �crit :
> > On Wednesday, January 16, 2013 9:49:22 AM UTC, Timo Kluck wrote:
> >
> > And then it would be nice if we'd distribute two tarbal
Op woensdag 16 januari 2013 11:37:17 UTC+1 schreef Felix Salfelder het
volgende:
>
> Hi there.
>
> The configuration item RootDir has a special meaning. If set, all paths
> in Dir:: will be relative to RootDir, even paths that are specified
> absolutely. So, for instance, if RootDir is set to /
Op woensdag 16 januari 2013 11:24:19 UTC+1 schreef Volker Braun het
volgende:
>
> On Wednesday, January 16, 2013 9:49:22 AM UTC, Timo Kluck wrote:
>
>> And then it would be nice if we'd distribute two tarballs for downstream
>> to package, the one depending on th
Op woensdag 16 januari 2013 04:17:48 UTC+1 schreef Michael Orlitzky het
volgende:
>
>
> Gentoo: emerge sage
> Fedora: yum install sage
> Debian: apt-get install sage
> Ubuntu: apt-get install sage
> Mac: port install sage
> FreeBSD: pkg install subversion
> ...
>
>
> And then it wou
Op woensdag 16 januari 2013 08:43:15 UTC+1 schreef Snark het volgende:
>
> Le 15/01/2013 23:28, Volker Braun a �crit :
>
> (1) Any patch to upstream should be forwarded upstream.
>
> (2) If upstream doesn't have a good build system, provide one, and don't
> forget (1).
>
> This is of course t
Op dinsdag 15 januari 2013 17:01:09 UTC+1 schreef Burcin Erocal het
volgende:
>
> On Tue, 15 Jan 2013 10:27:38 -0500
>
> Keshav, Jordi and many others have pointed these out before, but
> our main problem seems to be:
>
> - we are not really using a DVCS
> - the build system is showing its l
Op vrijdag 11 januari 2013 21:27:17 UTC+1 schreef Nils Bruin het volgende:
>
>
> Isn't the real bug here that Matrix uses a much too heavy device to
> keep track of a boolean flag (mutability=true/false)? Spinning this
> off into a full-blown python class is just ludicrous for something as
> fun
Op vrijdag 11 januari 2013 14:27:43 UTC+1 schreef David Loeffler het
volgende:
>
> I'm keen to keep Matrix_integer_2x2 as a subclass of Matrix. I'd have said
> that doing it any other way is likely to cause lots of obscure bugs (since
> developers will quite naturally assume that Matrix_xxx is
Op vrijdag 11 januari 2013 13:41:42 UTC+1 schreef David Loeffler het
volgende:
>
>
> > I think the reason for subclassing in this case is code-reuse. But
> that's in itself a dangerous thing to do if we change the class' internal >
> behavior by this much. People changing the code for Matrix_den
Op vrijdag 11 januari 2013 11:16:07 UTC+1 schreef David Loeffler het
volgende:
>
>
> So I think it's acceptable if Matrix_integer_2x2 doesn't implement
> everything in the Sage matrix specification,
>
I almost agree. I think that it would be acceptable to raise a
NotImplementedError for some me
Hi,
Also, it seems that
hg.sagemath.org/extcode-main
hg.sagemath.org/scripts-main
are actually the same repository. That can't be right.
Timo
Op donderdag 6 december 2012 09:19:31 UTC+1 schreef Keshav Kini het
volgende:
>
> On Wed, Dec 5, 2012 at 11:19 PM, Minh Nguyen
> >
> wrote:
> > Hi K
Op donderdag 29 november 2012 14:17:49 UTC+1 schreef Andrea Lazzarotto het
volgende:
> They could just call a different executable with a script that intercepts
the output and then parses it.
Yes, I suggested the same thing. My point was that I'm not entirely sure
that the technical detail of li
Op donderdag 29 november 2012 10:45:37 UTC+1 schreef Andrea Lazzarotto het
volgende:
>
> 2012/11/29 mhampton >
>
>> "So in Mathematica 9, one thing we’ve added is built-in integration
>> with the R statistics language." -- that's interesting. I think R has
>> really won in the realm of advanced
Op zondag 25 november 2012 02:09:46 UTC+1 schreef Keshav Kini het volgende:
>
> Charles Bouillaguet > writes:
> > Hi all,
> >
> > It would probably be safer to check if there are local change to the
> sage library repos before applying the upgrade, and the upgrade process
> should complain if
Op woensdag 28 november 2012 05:44:06 UTC+1 schreef kcrisman het volgende:
>
> Sorry, what I mean is that the standard spkg would remain the same, and
> the optional one would be the one you created and which would have
> instructions to overwrite anything from the standard spkg, as well as of
>
Op woensdag 28 november 2012 03:48:11 UTC+1 schreef kcrisman het volgende:
>
>
>>
>> One is an updated Boost library (standard spkg), and the other is an
>> update to polymake (optional spkg). I've had to upload them to my own
>> server because of the filesize limit on trac. It would be nice if s
Hi,
These two spkg updates need review:
http://trac.sagemath.org/13767
http://trac.sagemath.org/13768
One is an updated Boost library (standard spkg), and the other is an update
to polymake (optional spkg). I've had to upload them to my own server
because of the filesize limit on trac. It woul
Hi Jan,
You're talking about building debian packages, right? Maybe it's helpful if
you have a look at pbuilder and pbuilder-dist. Those tools allow you to
build packages for other versions of Debian and Ubuntu than the machine
you're building on. Then you don't need to have dedicated installs
Op donderdag 8 november 2012 10:36:51 UTC+1 schreef John Cremona het
volgende:
>
> Either I am doing something wrong or a simple operation which should
> be fast is in fact very slow, but I do not know why.
>
> If V,W are vector spaces over QQ, subspaces of the same ambient
> space, then V.sum
Op vrijdag 26 oktober 2012 01:52:53 UTC+2 schreef François het volgende:
>
>
> Well there is definitely something funny in that config.log. You said you
> patched ecm could we know what you patched?
>
> Yes. To be clear: I patched it to *fix* the build error, the error is not
caused by the patc
Op donderdag 25 oktober 2012 23:50:52 UTC+2 schreef François het volgende:
>
> On Thu, 25 Oct 2012 08:21:16 Timo Kluck wrote:
> I'll have to look at configure.ac to understand the logic but it looks
> quite messy. You are using gcc 4.6.3 on lubuntu x86_64.
> I see that yo
> We need the config.log file which would be in spkg/build/ecm-xxx/src
> That's where we can really dissect what's gone wrong.
>
Thanks for replying. Here it is: http://paste.ubuntu.com/1305118/
Best, Timo
--
You received this message because you are subscribed to the Google Groups
"sage-d
ckage
compiles without problems if I modify spkg-install to clear the CFLAGS
variable before configuring.
Has anyone else seen this behaviour?
Best regards, Timo Kluck
[1] snippet from build log
---
Settings from SAGE_LOCAL/include/gmp.h:
CC=gcc -std=gnu99
CFLAGS=-O2 -m64 -march=k8 -mtune
Op vrijdag 19 oktober 2012 20:06:02 UTC+2 schreef Volker Braun het volgende:
>
> The problem is that
> * Sage and your system come with libppl
> * gcc links with ppl
> * the system and Sage versions of ppl conflict
>
> You can try to compile with
>
> SAGE_INSTALL_GCC=no make
>
Thanks, that
use both a system copy and a sage
copy of the library libgmp are linked (see the snippet below).
Has anyone seen this before? Is there a workaround?
Thanks and best regards,
Timo Kluck
--
gcc -O0 -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual
-Wstrict-prototypes -W
missing-prototypes -Wmiss
Op vrijdag 19 oktober 2012 01:30:07 UTC+2 schreef Dima Pasechnik het
volgende:
>
> On Thursday, 18 October 2012 20:01:51 UTC+8, Jeroen Demeyer wrote:
>>
>> On 2012-10-18 11:20, Timo Kluck wrote:
>> > This ticket [1] adds a %prun directive for profiling to the notebo
been automatically included before will
not prevent it from being included now?
Thanks and best regards,
Timo Kluck
[1] http://trac.sagemath.org/sage_trac/ticket/5814
[2] http://www.sagemath.org/mirror/src/changelogs/sage-5.3.txt
--
You received this message because you are subscribed to the Google G
Hi,
Could someone reopen this ticket [1] and set it to needs review? I either
don't have permissions or I'm an idiot with trac. It was closed because we
thought it should be handled in the notebook, but it turns out it doesn't.
Thanks and regards,
Timo
[1] http://trac.sagemath.org/sage_trac/t
Best regards,
Timo Kluck
--
--
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
Op vrijdag 3 augustus 2012 07:42:10 UTC+2 schreef Nils Bruin het volgende:
>
> in which case one can avoid using the temporary file altogether by
> doing
>
> import cProfile,pstats
> s=pstats.Stats(cProfile.Profile().run(cmd))
>
> It makes you wonder why cProfile.run has its current interface
> Why should one want to turn a Python function (or method) into a
> symbolic function? I guess one couldn't do calculus (differentiate,
> integrate) the resulting symbolic function, or can one? So, beyond
> calculus, what can one do with a symbolic function that can't be done
> with a Python
Sorry, I didn't realize that. Here's the code.
---
def symbolic_function(variables, *args, **kwds):
def result(f):
def evalf_func(self,x,parent=None):
if parent == None:
return f(x)
else:
return parent(f(x))
return functio
thods,
etc, but it seems possible.
I can probably produce a patch for this, but I would like some feedback
first.
Best regards,
Timo Kluck
--
--
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...@googlegroup
Thanks Jeroen. I'm looking forward to that work coming together.
Best regards, Timo
Op vrijdag 3 augustus 2012 12:31:37 UTC+2 schreef Jeroen Demeyer het
volgende:
>
> On 2012-08-03 12:20, Timo Kluck wrote:
> > Hi all,
> >
> > I currently have a tarball inst
not clear to me, however, how to build sage from the result of
hg clone http://hg.sagemath.org/sage-main
>From the errors I'm getting, the ./install script seems to require
environment variables like SAGE_LOCAL and include files in
SAGE_LOCAL/include, and maybe more.
Best regards,
Timo
60 matches
Mail list logo
