On Jul 31, 4:27 pm, Mitesh Patel wrote:
> You could try using sage.misc.citation.get_systems:
>
> sage: var('n, k');
> sage: sum(1 / sum(k, k, 1, n), n, 1, infinity)
> 2
> sage: from sage.misc.citation import get_systems
> sage: get_systems('sum(1 / sum(k, k, 1, n), n, 1, infinity)')
> ['MPFI', 'g
On 2 August 2010 00:26, Mitesh Patel wrote:
>> Searching Sage trac for road maps and meta-tickets, I find
>>
>> http://trac.sagemath.org/sage_trac/wiki/CategoriesRoadMap
>> http://trac.sagemath.org/sage_trac/wiki/SageCombinatRoadMap
>> http://trac.sagemath.org/sage_trac/wiki/GraphTheoryRoadmap
>>
Hej All,
I started developing for sage not so long ago and I wonder if there
are some good coding practices / conventions for dealing with global
functions and attributes which have the same name and also do the same
thing. An example of such a global function / atribute combination:
sage: sqrt(3
Hello all,
Although I'm certainly not competent in elliptic curves, I spent some
time trying to identify this bug more precisely, and I believe the
problem stems from Dp_valued_series; could someone help us identify
which of these two outputs is correct? More details can be found on
the trac page
On 08/01/2010 05:23 PM, Mitesh Patel wrote:
> On 08/01/2010 12:06 PM, Dr. David Kirkby wrote:
>> Just to recap, my status for builds of Sage on Solaris are:
>>
>> * 32-bit SPARC on t2. Works perfect, though #9657 means Sage does not
>> build with gcc 4.5.0 and I doubt it will build with gcc 4.5.1.
Hi Dima,
I don't have any experience with making a clones from/within a system-
wide install. Normally, I have not tried to place it anywhere in
particular, that all just happens. So if $SAGE_ROOT is my working
directory, I just use
./sage -clone xxx
and end up with a new directory
$SAGE_ROOT
On 08/01/2010 12:06 PM, Dr. David Kirkby wrote:
> Just to recap, my status for builds of Sage on Solaris are:
>
> * 32-bit SPARC on t2. Works perfect, though #9657 means Sage does not
> build with gcc 4.5.0 and I doubt it will build with gcc 4.5.1. That's a
> very simple patch I'd like to get mer
Hej all,
Tnx for the explanation. I went for option number 1. It was a lot of
coppy pasting, I see why the author chose his solution.
While I was at it I also added a doctest for each of the functions
since this was lacking. And I also found a small bug in the original
code which made the ceil fu
On 2010-08-01 23:08, William Stein wrote:
> If you're working on this code, make sure to define a __hash__ method
> for ideals.
This can be done independently of this discussion, I created #9666 and
can do this.
For the moment, I will leave __repr__ alone. I think we should really
have a clear id
On Sun, Aug 1, 2010 at 1:54 PM, Jeroen Demeyer wrote:
> Hello sage-devel,
>
> I think we should think about NumberFieldFractionalIdeal.__repr__(),
> i.e. how to print an ideal in a number field. Right now, we actually
> check whether the ideal is principal (and then use a generator to print
> the
Hello sage-devel,
I think we should think about NumberFieldFractionalIdeal.__repr__(),
i.e. how to print an ideal in a number field. Right now, we actually
check whether the ideal is principal (and then use a generator to print
the ideal). This is very slow, especially with proof=True. I see
se
On Sun, Aug 1, 2010 at 11:47 AM, Harald Schilly
wrote:
> On Aug 1, 8:07 pm, Fredrik Johansson
> wrote:
>> sage -clone new_branch takes 15 minutes on my "fast" laptop (and about
>> twice that time on my slow laptop).
>
> That's the reason why I never clone and just use mercurial queues (and
> also
On Aug 1, 8:07 pm, Fredrik Johansson
wrote:
> sage -clone new_branch takes 15 minutes on my "fast" laptop (and about
> twice that time on my slow laptop).
That's the reason why I never clone and just use mercurial queues (and
also never do hg checkins). When the queue is empty I can always check
Hi,
sage -clone new_branch takes 15 minutes on my "fast" laptop (and about
twice that time on my slow laptop). Nearly all that time (~14 minutes)
is spent rebuilding the entire documentation. The documentation
shouldn't change when a fresh clone is created, and Sphinx supports
updating only change
I have written to FSF. So far, only an automated reply, giving the
case number:
"Your request has
been assigned an ID of [gnu.org #599076]."
We'll see...
Best,
Dima
On Jul 31, 1:54 am, Alex Ghitza wrote:
> On Fri, 30 Jul 2010 08:43:03 -0700, William Stein wrote:
> > On Friday, July 30, 2010, Dr
If I'm not mistaken, there are still issues with people having to download Sage
source code when their CPUs are older than what Sage was compiled with. I see
someone had a Solaris issue the other day, as his processor was older than the
processor on which I'd built Sage.
I asked on the gcc-hel
SINGULAR /
Development
A Computer Algebra System for Polynomial Computations / version
3-1-0
0<
by: G.-M. Greuel, G. Pfister, H. Schoenemann\ Mar 2009
FB Mathematik der Univer
On Jul 31, 4:27 pm, Mitesh Patel wrote:
> You could try using sage.misc.citation.get_systems:
>
> sage: var('n, k');
> sage: sum(1 / sum(k, k, 1, n), n, 1, infinity)
> 2
> sage: from sage.misc.citation import get_systems
> sage: get_systems('sum(1 / sum(k, k, 1, n), n, 1, infinity)')
> ['MPFI', 'g
Hi Dusan,
On 1 Aug., 11:35, Dušan Orlović wrote:
> we get f=y*I.0 -2*y^3*I.1 -x*I.2 = x*y^2
> We CAN reduce f on [x*y^3, 2*x^2 + x*y, 3*x*y, 2*y^2] to zero because
> f = y * (3*x*y) - x * (2*y^2) .
No, we can't.
You have shown that f belongs to the ideal generated by [x*y^3, 2*x^2
+ x*y, 3*x*y,
Hello sage-devel,
At present, the error catching mechanism from PARI is rather bad: you
get exceptions like
Traceback (most recent call last):
...
PariError: (15)
I would like to change this (and created ticket #9640). When looking
into this issue, I realize it would make sense to add a gener
Hi Simon,
please do this by hand.
for I=R*(4*x^2*y^2+2*x*y^3+3*x*y, 2*x^2+x*y, 2*y^2)
we get f=y*I.0 -2*y^3*I.1 -x*I.2 = x*y^2
We CAN reduce f on [x*y^3, 2*x^2 + x*y, 3*x*y, 2*y^2] to zero because
f = y * (3*x*y) - x * (2*y^2) .
So this gives that [x*y^3, 2*x^2 + x*y, 3*x*y, 2*y^2] is Groebner ba
sage-mode.el won't load unless help-mode.el is loaded first. Otherwise
emacs complains about a button type definition based on 'help-xref
supertype.
>From sage-mode.el lines 1167 to 1170:
--8<---cut here---start->8---
(define-button-type 'help-sage-function-def
22 matches
Mail list logo
