On Mon, Jul 25, 2011 at 4:42 PM, John H Palmieri wrote:
> The patches at http://trac.sagemath.org/sage_trac/ticket/6495 should speed
> up building the reference manual. On sage.math, applying the patches made
> the build time for the html version go from just under 18 minutes to 2.5
> minutes, wi
On Jul 25, 4:39 pm, John H Palmieri wrote:
> To the Sage developers:
>
> There are 220 tickets on trac needing review right now. Please review some
> of them!
John, thanks very much for putting out the call and reminding folks
about reviews. At least 16 of those tickets waiting for reviews are
There seem to be two issues here.
1. It would be nice for Pari to get credit when Pari is used, even if
the
user gave credit to Sage.
and
2. (Bill Hart's assertion) that citing an algorithm that you haven't
studied
is like citing a paper you haven't read.
Regarding item 1. If you accept code und
Hi Bill,
let me comment on the "how to cite individual Sage components" topic.
On 26 Jul., 00:18, Bill Hart wrote:
> * Citing a Number Theory package you know nothing about in published
> research is about as dubious as citing a paper you have never read.
> Unless you are prepared to read the co
The patches at http://trac.sagemath.org/sage_trac/ticket/6495 should speed
up building the reference manual. On sage.math, applying the patches made
the build time for the html version go from just under 18 minutes to 2.5
minutes, with similar speed-ups for the pdf version. It also allows you t
Can we please be more precise and scientific when discussing this
important issue. I find it confusing to try to think about the many
issues raised without some precision.
Some trivialities first. Please take care to distinguish:
* finding a bug in Pari and contributing a bug report
* finding a b
Thanks! 11468 fixed the leak. While I was at it I gave 11495 a positive
review also.
On Mon, Jul 25, 2011 at 1:19 AM, Jean-Pierre Flori wrote:
> I tested your function on my Sage 4.7.alpha? install with 11468 (not
> 14468...) and 11495 and I do not seem tp get the leak:
> sage: leak()
> 0.46875
>
On Jul 25, 2011, at 3:12 PM, Jason Grout wrote:
> On 7/24/11 4:08 AM, Ivan Andrus wrote:
>> On Jul 24, 2011, at 6:15 AM, Jason Grout wrote:
>>> On 7/23/11 2:50 PM, Ivan Andrus wrote:
Dear Sage iPhone users,
>>>
>>> Have you thought about using sagemath.org:5467 ? Two students and
>>> I have
On 07/20/11 13:26, Burcin Erocal wrote:
>
> If you are adding tests only for integration, starting a new file
> sage/symbolic/tests.py might be better.
>
> ...
>
> Don't forget to mention the ticket number in the test.
>
How's this looking?
--
To post to this group, send an email to sage-dev
On Mon, Jul 25, 2011 at 4:16 PM, Jeroen Demeyer wrote:
> On 2011-07-25 15:40, John Cremona wrote:
>> A second point Karim made is that he would like to see more more cases
>> (currently: 0) in which a deficiency in a part of Pari used by Sage
>> -- for example, some number field functionality --
On 2011-07-25 15:40, John Cremona wrote:
> A second point Karim made is that he would like to see more more cases
> (currently: 0) in which a deficiency in a part of Pari used by Sage
> -- for example, some number field functionality -- was fixed by
> contributions to Pari itself, rather than by a
On Jul 25, 2011, at 12:31 AM, Rado wrote:
> I do have some other specific questions that might be easier to answer:
>
> - Where should I host the source code? as part of Sage or separately e.g. on
> bitbucket?
>
> Sagenb is on google code. It makes sense to have a separate project for the
> ap
I had an interesting conversation with Karim Belabas, lead developer
of the Pari project (which Sage relies on for many things, including
most number field functionality). I specifically asked him how he saw
the Sage/Pari relationship. I have CC'ed him to this email, and hope
that if there is any
On 7/24/11 4:08 AM, Ivan Andrus wrote:
On Jul 24, 2011, at 6:15 AM, Jason Grout wrote:
On 7/23/11 2:50 PM, Ivan Andrus wrote:
Dear Sage iPhone users,
I finally took the time to fix the icons on the iPhone app I've
been working on so that I'm not completely embarrassed by them.
For those that w
Thank you for the help. This is now #11624.
Martin
On 25 Jul., 14:31, Nicolas Borie wrote:
> Le lundi 25 juillet 2011 à 04:47 -0700, Martin Raum a écrit :
>
> > Hello all,
>
> Hello Martin,
>
> > I happened to think about Sidon g-sets and to do some computations I
> > implemented a recursive enu
On 7/24/11 3:31 PM, Rado wrote:
That's a really tricky question, probably people will have to play with
it for a bit before they realize what will work best. I would leave it
as a work in progress ;) One thing that comes to mind is having a "close
the matching paren or quote" button (like CTRL+
Le lundi 25 juillet 2011 à 04:47 -0700, Martin Raum a écrit :
> Hello all,
Hello Martin,
> I happened to think about Sidon g-sets and to do some computations I
> implemented a recursive enumeration of such sets. Clearly, this would
> go into the combinatorics tree. I am not an expert in combinato
Hello all,
I happened to think about Sidon g-sets and to do some computations I
implemented a recursive enumeration of such sets. Clearly, this would
go into the combinatorics tree. I am not an expert in combinatorics.
Since the code doesn't seem to fit in any of the files in sage/
combinat, pleas
Le dimanche 24 juillet 2011 à 15:38 -0700, Dima Pasechnik a écrit :
> On Sunday, 24 July 2011 22:37:05 UTC+1, Rafael T wrote:
>
> The gap-system already has the ability to work with Coxeter
> groups:
> http://www.gap-system.org/Gap3/Manual3/C075S005.htm Maybe I
>
I tested your function on my Sage 4.7.alpha? install with 11468 (not
14468...) and 11495 and I do not seem tp get the leak:
sage: leak()
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
0.46875
Ticket 11521 which seems to be nothing but 715 looks similar, but does
not seem related.
You could also try applying 14468 and 11495 (patches but no reviews
yet, one is just a very old bug which has been unfortunately rolled
back).
They affect multi polynomial rings used by elliptic curves.
Final
I just found the following memory leak:
def leak():
K. = NumberField(x^2 - x - 1)
m = get_memory_usage()
for n in xrange(10):
E = EllipticCurve(K, [3,4,5,6,7])
if n % 1000 == 0:
print get_memory_usage() - m
sage: leak()
0.0
0.5
1.0
1.0
1.5
2.0
2.0
2.5
3
22 matches
Mail list logo