On Feb 4, 9:49 pm, William Stein wrote:
> There are numerous packages for Mathematica for doing tensor calculus.
> I can't comment on whether or not they are "easily usable" (is any
> interesting mathematics or physics "easy"?).
Hrm, well, one could drive the proverbial truck through that
openi
On Thu, Feb 4, 2010 at 8:49 PM, William Stein wrote:
> On Thu, Feb 4, 2010 at 6:13 PM, Dox wrote:
>> Hi people!
>> As some of you may know I'm a physicist. One of my complains to
>> Mathematica is the lack of an easily usable tensor package, specially
>> for those (like me) interested in General
On Thu, Feb 4, 2010 at 6:13 PM, Dox wrote:
> Hi people!
> As some of you may know I'm a physicist. One of my complains to
> Mathematica is the lack of an easily usable tensor package, specially
> for those (like me) interested in General Relativity calculations.
>
> Does a package like that exist
On Feb 3, 11:33 pm, Dr David Kirkby wrote:
>
> Than you for finding this error John. It's strange, I never se this on
> Solaris myself, though William says he has seen it before on Linux.
> IHopefully, this bug can be squashed, though it is not as serious as
> the one which is stopping Sage buildi
> It also says it needs Cmake
Cmake 2.4.8 is actually a current experimental spkg, but Dionysos says
it needs 2.6 or above.
--
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 o
>
> Anyway. I really think Sage could use more topology related tools. And
> since Dionysos comes with Python bindings, I think it would be a nice
> project to combine with Sage.
>
Dionysos apparently needs Boost 1.36 or greater, but we ship 1.34
(again, just according to http://www.sagemath.org/p
>
> If you have an spkg foo and type
>
> sage -f -m foo.spkg
>
> then it will not be deleted from spkg/build/ after the install completes.
Yes, robertwb had privately told me that before. I was thinking that
it might be worth having this happen in *all* builds from scratch, so
that one might
Hi David,
On Fri, Feb 5, 2010 at 12:29 PM, Dr. David Kirkby
wrote:
> Should I reopen #3381 for this, or create a new bug report?
Please open a new ticket. A golden rule is to refrain from re-opening
a ticket that is already closed.
--
Regards
Minh Van Nguyen
--
To post to this group, send
Dr. David Kirkby wrote:
I raised this issue back in 2008
http://trac.sagemath.org/sage_trac/ticket/3381
that R needs a powerful version of iconv - the one supplied by Sun is
not sufficiently powerful. This is documented in the 'R Installation and
Administration' manual.
http://cran.r-projec
I raised this issue back in 2008
http://trac.sagemath.org/sage_trac/ticket/3381
that R needs a powerful version of iconv - the one supplied by Sun is not
sufficiently powerful. This is documented in the 'R Installation and
Administration' manual.
http://cran.r-project.org/doc/manuals/R-admin
Robert Bradshaw wrote:
Does this look right?
http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch
Yes. Looks like another thing coming from Solaris having a non-optimal
literal value for e (exp(1), decimal floating point literals, etc.). I'd
much rather fix
Maybe I should not talk because I have no idea on how CodeMirror and
BeSpin work, but I would say that I'd think more than twice before
choosing CodeMirror instead of BeSpin, for this reason:
1) BeSpin is anyway sponsored (or at least hosted) by Mozilla, which
is a fairly decent guarantee of mid-te
Hi!
On 4 Feb., 21:18, Mike Hansen wrote:
...
> On a less direct note, from scanning the conversation Simon links to,
> the construction he describes is not the Rips complex, but rather the
> Cech complex (which is defined as the nerve of the collection of
> discs). In persistent homology Rips com
On Fri, 5 Feb 2010 08:34:03 +1100, Minh Nguyen wrote:
> In the past [1] I expressed an interest in maintaining a "conservative
> release". That was before I realized that release management is a
> full-time job. Looking back, it's really is a full-time job. Perhaps
> not to other people. But I gue
On Feb 4, 11:15 pm, Harald Schilly wrote:
> hg qseries should list two applied patches now!
sorry, i mean hg qapplied
--
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
On Feb 4, 10:01 pm, ross k wrote:
> So do we...?
> 1) download the mpmath-0.14.spkg via the link
> 2) cd $SAGE_ROOT
> 3) ./sage -f mpmath-0.14.spkg
yes - and look out for compile errors, strange warnings, ...
> 4) ./sage -hg qimport
> http://trac.sagemath.org/sage_trac/attachment/ticket/8159/mp
On 4-Feb-10, at 1:34 PM, Minh Nguyen wrote:
Hi David,
On Thu, Feb 4, 2010 at 8:10 PM, Dr. David Kirkby
wrote:
Comments ?
In the past [1] I expressed an interest in maintaining a "conservative
release". That was before I realized that release management is a
full-time job. Looking back,
Hi David,
On Thu, Feb 4, 2010 at 8:10 PM, Dr. David Kirkby
wrote:
> Comments ?
In the past [1] I expressed an interest in maintaining a "conservative
release". That was before I realized that release management is a
full-time job. Looking back, it's really is a full-time job. Perhaps
not to o
2010/2/4 kcrisman :
>
>
>> >> I strongly support this. Judging by how solid my tests are with
>> >> 4.3.2
>> >> already, the 4.3.2 release will definitely be happening this
>> >> Saturday.
>> >> I'm highly impressed with how efficiently Minh is handling the
>> >> 4.3.2
>> >> release cycle.
>>
>>
> >> I strongly support this. Judging by how solid my tests are with
> >> 4.3.2
> >> already, the 4.3.2 release will definitely be happening this
> >> Saturday.
> >> I'm highly impressed with how efficiently Minh is handling the
> >> 4.3.2
> >> release cycle.
>
> >>> I would really like
Minh Nguyen wrote:
Hi David,
On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby
wrote:
Does this look right?
http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch
I think you know this already, but it doesn't hurt to explicitly say
so here. The commit must be
On Feb 4, 2010, at 1:02 PM, Minh Nguyen wrote:
Hi David,
On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby
wrote:
Does this look right?
http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch
I think you know this already, but it doesn't hurt to explicitly sa
Hi David,
On Fri, Feb 5, 2010 at 7:34 AM, Dr. David Kirkby
wrote:
> Does this look right?
>
> http://trac.sagemath.org/sage_trac/attachment/ticket/8185/8185-numerical-noise.patch
I think you know this already, but it doesn't hurt to explicitly say
so here. The commit must be on one line. That
So to test this do we download and install the spkg to sage.4.3.2.rc0,
apply the patch and do all doctests?
(Sorry about this but is the following right? - until I review a few
more tickets Im going to ask if Im doing the right thing at this low
level.
So do we...?
1) download the mpmath-0.14.spk
On Feb 4, 2010, at 12:34 PM, Dr. David Kirkby wrote:
Robert Bradshaw wrote:
On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote:
I created a patch to fix a numerical noise issue.
Expected:
0.85914091422952255
Got:
0.85914091422952277
http://trac.sagemath.org/sage_trac/ticket/8185
After
Robert Bradshaw wrote:
On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote:
I created a patch to fix a numerical noise issue.
Expected:
0.85914091422952255
Got:
0.85914091422952277
http://trac.sagemath.org/sage_trac/ticket/8185
After doing this, I realised I'd put too many dots on the
Em 3 de fevereiro de 2010 19:00, Paulo César Pereira de Andrade
escreveu:
> On Jan 13, 8:08 am, François Bissey wrote:
>> On Wed, 13 Jan 2010 22:35:16 Craig Citro wrote:
>>
>> > > If you work on getting this merged upstream as a bug that's a good
>> > > selling point for us. We can produce a patc
-- Forwarded message --
From: Dmitriy Morozov
Date: Thu, Feb 4, 2010 at 11:48 AM
Subject: Re: [sage-devel] Rips complex in Sage?
To: Mike Hansen
Cc: sage-devel
Excerpts from Mike Hansen's message of Thu Feb 04 14:24:54 -0500 2010:
>On Thu, Feb 4, 2010 at 6:10 AM, Simon King wr
On Feb 4, 2010, at 12:03 PM, Dr. David Kirkby wrote:
I created a patch to fix a numerical noise issue.
Expected:
0.85914091422952255
Got:
0.85914091422952277
http://trac.sagemath.org/sage_trac/ticket/8185
After doing this, I realised I'd put too many dots on the end, so
instead of the
To answer the original question, the logic seems to be as follows:
- For a major new feature, or if a year has passed, update x.
- If we know of a significant feature that's going to be merged in
ahead of time, update y.
- Otherwise, update z.
- Bugfix only, release x.y.z.w.
Anyone is welcome
You can edit the patch with a text editor if it is as trivial as this.
And when you upload it again, you can opt to replace the earlier
patch with the same name.
John
On 4 February 2010 20:03, Dr. David Kirkby wrote:
> I created a patch to fix a numerical noise issue.
>
> Expected:
> 0.85914
I created a patch to fix a numerical noise issue.
Expected:
0.85914091422952255
Got:
0.85914091422952277
http://trac.sagemath.org/sage_trac/ticket/8185
After doing this, I realised I'd put too many dots on the end, so instead of the
two needed, I'd put three.
0.85914091422952...
On
On Thu, Feb 4, 2010 at 6:10 AM, Simon King wrote:
> Hi!
>
> At
> http://groups.google.com/group/sage-support/browse_thread/thread/edcd7dc0e8be9aa5
> Eli posed a problem that -- as much as I understand -- can be tackled
> using the Rips complex. A quick search suggests that it is not
> provided by
Hello,
On Thu, Feb 4, 2010 at 8:55 AM, javier wrote:
> the latest gets to print down the "computing Killing form" print, and
> exits without any error and without saving any files.
>
> Is it possible to do the above with @parallel? I have tried looking
> for documentation for that decorator, but
Hello,
On Thu, Feb 4, 2010 at 8:44 AM, Dr. David Kirkby
wrote:
> but want to produce a proper Mercurial patch, rather than one using 'diff'.
> What directory should I be in when I try to use Mercurial? (I'm using it
> from inside Sage this time, rather than a copy of Mercurial installed on the
>
On Thu, Feb 4, 2010 at 12:29 PM, Harald Schilly wrote:
> Hi, I think for testing it would be best if there is an
> mpmath-0.14.spkg ... That ensures that we all test exactly the same
> configuration and it avoids errors that might happen after testing
> when packing it together in an spkg.
>
> I c
John Cremona wrote:
Surely almost all Sage releases contain major new functionality!
That's true.
Personally I think an occasional bug-fix-only release would be useful. Where a
release is planned to be a bug fix only. Even if they are very occasional, like
every 6 months.
Those 6-monthly
Surely almost all Sage releases contain major new functionality!
Except very occasionally a release is followed by a quick emergency
bug fix. And also rather occasionally there is a huge new feature.
Thus I would expect that
* most releases sage-x.y.z would increment y and reset z (to 0, or 1).
>From the sage prompt use hg_sage.status() to see which files have
changed, hg_sage.diff() to see the diffs, hg_sage.ci() to check them
in (which will show you the diffs again) and hg_sage.export() to
export the patch.
Before the last step amke sure that you have a (small) .hgrc file in
your home
William Stein wrote:
2010/2/3 Dima Pasechnik :
William,
can I steal/clone your Sage installation there?
Thanks!
The sage-4.3.2.alpha0 was built with GCC-4.4.2. Now GCC-4.4.3 is
installed on there, so got to start from scratch.
If you believe that you need to start from scratch, then perhaps
Hi all,
gotta do some computations involving a really big matrix, and need to
save each row in a different file (matrix is too big to fit in
memory). SInce every row can be computed independently I have tried to
parallelize the computation. First, this is my original computation of
the matrix (for
I've noted there is some numerical noise on
sage/calculus/functional.py
when run on a couple of SPARCs.
File
"/export/home/drkirkby/sage-4.3.0.1/devel/sage-main/build/sage/calculus/functional.py",
line 195:
sage: float(area)
Expected:
0.85914091422952255
Got:
0.85914091422952277
Harald,
I've fixed it, I think, and posted a patch on the corresponding
ticket.
That was a simple linking of dynamic libs issue.
If you like I can take over the package - but I appreciate the
feedback on the patch,
one way or another.
Best,
Dmitrii
On Feb 4, 9:22 pm, Harald Schilly wrote:
> On T
Harald Schilly wrote:
...and to come back on topic: looking back, i think the best version
number for Sage were the release dates (back in the early 0.x time).
Today, a "-MM" string would be nice (adding a .1 if there is a
second release in the same month).
H
I can't say I agree with that
On Feb 4, 4:02 pm, ross k wrote:
> I recently attended an in-house promotion of the latest "major"
> release of Matlab and I cant tell you how underwhelmed I was ...
That sounds extremely boring. I think matlab's success is that they
started very early and listened closely what the users needed -
ross k wrote:
David
(It sounded like you were a bit discouraged and I hope this doesnt
sound condescending but...)
No. I realise I am in a minority among Sage developers. I suspect my views might
be a bit less of a minority on sage-support. But even there, I expect they will.
You were righ
Dr. David Kirkby wrote:
I'm just running the test suite of Sage 4.3.0.1 on 't2'. This was not
compiled on 't2', but on an old SPARC of mine. It is failing at this test.
Has anyone got a build on 't2' they have created on 't2', and can
confirm whether or not it passes or fails.
sage -t "deve
David
(It sounded like you were a bit discouraged and I hope this doesnt
sound condescending but...)
You were right to query - I believe we should always think it is
legitimate to query how we might be able to do things be better.
But now that we've had that discussion and its seems like things w
I'm just running the test suite of Sage 4.3.0.1 on 't2'. This was not compiled
on 't2', but on an old SPARC of mine. It is failing at this test.
Has anyone got a build on 't2' they have created on 't2', and can confirm
whether or not it passes or fails.
sage -t "devel/sage-main/build/sage/lf
On Jan 28, 10:03 pm, Nils Bruin wrote:
> On Jan 28, 1:01 pm, Mike Hansen wrote:
> > You can easily createSVGplots as it is now:
> > sage: p = plot(x^2, -2, 2)
> > sage: p.save('xsquared.svg')
> Interesting. In firefox 3.5.2, this actually does not work in the
> notebook:
What happens if you add
> But even in a university environment, some people want something that does not
> change as often. I'm not the first to make this point, and I doubt I'd be the
> last. Perhaps asking on sage-support might have given a different view, as
> that
> would more likely to reach users who are not devel
Hi!
At
http://groups.google.com/group/sage-support/browse_thread/thread/edcd7dc0e8be9aa5
Eli posed a problem that -- as much as I understand -- can be tackled
using the Rips complex. A quick search suggests that it is not
provided by Sage.
Is there a sufficiently free (licence-wise etc) piece of
All tests pass on 64-bit ubuntu except
sage -t -long devel/sage/sage/plot/plot3d/plot_field3d.py
but that passes when I re-try it.
All pass on 32-but Suse.
John
On 4 February 2010 12:46, mhampton wrote:
> All tests pass on my intel mac running 10.4.11.
>
> -Marshall
>
> --
> To post to this g
The squashfs files are now uploaded to here:
http://boxen.math.washington.edu/home/frank/sagemath/squashfs/
Frank Polte
--
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 optio
William Stein wrote:
2010/2/4 Dr. David Kirkby :
ross k wrote:
I know this subject is a contentious one so Ill just make a quick comment...
It would however mean that people that wanted a stable release to install on
a server they can't change every couple of weeks, would chose an X.Y.1, or
a
On Thu, Feb 4, 2010 at 14:15, Dima Pasechnik wrote:
> While trying to upgrade the cvxopt package for Sage to version 1.1.2
> of cvxopt,...
Hi, I'm the one who created this spkg and i've already tweaked the
setup.py with various levels of success. The older spkg (from before
1.0) already had two d
everywhere you link against blas or lapack in the setup.py script, I would
also link against gfortran.
Joachim
On Thu, Feb 4, 2010 at 2:15 PM, Dima Pasechnik wrote:
> While trying to upgrade the cvxopt package for Sage to version 1.1.2
> of cvxopt, one encounters a build problem; more precisely
While trying to upgrade the cvxopt package for Sage to version 1.1.2
of cvxopt, one encounters a build problem; more precisely, it's a
runtime error that comes from the dynamic library cholmod.so missing
a symbol.
I gather it had to be linked with against an appropriate Fortran
library (libgfortra
2010/2/4 Dr. David Kirkby :
> ross k wrote:
>>
>> I know this subject is a contentious one so Ill just make a quick comment...
>>
>>> It would however mean that people that wanted a stable release to install on
>>> a server they can't change every couple of weeks, would chose an X.Y.1, or
>>> an X.
All tests pass on my intel mac running 10.4.11.
-Marshall
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-dev
ross k wrote:
I know this subject is a contentious one so Ill just make a quick comment...
It would however mean that people that wanted a stable release to install on
a server they can't change every couple of weeks, would chose an X.Y.1, or
an X.Y.2, safe in the knowledge that it should be qu
Alex Ghitza wrote:
On Thu, 04 Feb 2010 09:10:25 +, "Dr. David Kirkby"
wrote:
It seems to me that Sage version numbers follow the rule, that when last digit
in X.Y.Z get to 2, then Y is incremented. That is some logic I guess, but it is
not a sensible one. (I think this is a case of Mathe
Hi, I think for testing it would be best if there is an
mpmath-0.14.spkg ... That ensures that we all test exactly the same
configuration and it avoids errors that might happen after testing
when packing it together in an spkg.
I created one here: (it's just an export from the svn trunk and two
ne
On Thu, 4 Feb 2010 16:02:52 +1100, Minh Nguyen wrote:
> Please test and report all problems.
Here are three reports:
- ONE --
OS version: Arch Linux
Machine name: artin
Architecture: Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz
32/64 bit: 32 bit
On Thu, 04 Feb 2010 09:10:25 +, "Dr. David Kirkby"
wrote:
> It seems to me that Sage version numbers follow the rule, that when last
> digit
> in X.Y.Z get to 2, then Y is incremented. That is some logic I guess, but it
> is
> not a sensible one. (I think this is a case of Mathematicians
I know this subject is a contentious one so Ill just make a quick comment...
> It would however mean that people that wanted a stable release to install on
> a server they can't change every couple of weeks, would chose an X.Y.1, or
> an X.Y.2, safe in the knowledge that it should be quite stable,
Dr. David Kirkby wrote:
Personally I feel having something like
Sage 4.0.0 - major new release. Sometime really great has happened. Be
prepared for some bugs (remember gcc 4.0.4 ?)
Sorry, that was supposed to be:
Sage 4.0.0 - major new release. Something really great has happened. Be
prepar
It seems to me that Sage version numbers follow the rule, that when last digit
in X.Y.Z get to 2, then Y is incremented. That is some logic I guess, but it is
not a sensible one. (I think this is a case of Mathematicians at work)
Would it not be more appropriate to have some logic to the versi
Mercurial queues are great, as I am just beginning to see.
Thanks for sharing.
Dmitrii
On Feb 4, 3:03 am, bump wrote:
> > make a new patch replacing the present one?
> > --- I have trouble understanding how to do this in mercurial.
> > Do I backout my previous patch and make a new one? (I tr
69 matches
Mail list logo
