[sage-devel] Re: Checking new code with an entire database (isogenies)

2009-09-22 Thread J. Cooley
Hi Tim, Thanks for the response, > You'll probably want to use an iterator instead. It should be much > less memory-intensive. Additionally, ``xrange``s are especially > optimized for iteration. > > database = CremonaDatabase().iter(xrange(1, 130001)) Yes, the code I wrote took a really long ti

[sage-devel] Re: Checking new code with an entire database (isogenies)

2009-09-17 Thread Tim Dumol
Hey Jenny, I thought I could chip in. On Sep 17, 8:28 pm, "J. Cooley" wrote: > Hi William, > > Thank you for all the information. I have spent time this morning > going through it all, the alarm thing is really useful ~ I also > discovered Ctl-C, which seems to be quite handy! (I am REALLY new

[sage-devel] Re: Checking new code with an entire database (isogenies)

2009-09-17 Thread J. Cooley
Hi William, Thank you for all the information. I have spent time this morning going through it all, the alarm thing is really useful ~ I also discovered Ctl-C, which seems to be quite handy! (I am REALLY new to this! John had shown me, but I forgot.) >   * check out the @parallel decorator  (not

[sage-devel] Re: Checking new code with an entire database (isogenies)

2009-09-16 Thread William Stein
On Wed, Sep 16, 2009 at 9:05 AM, J. Cooley wrote: > > Hi, > > I've written with my supervisor some code that computes the isogeny > class of a curve over QQ. I would like to check it with the entire > Cremona database overnight, but I'm not sure how to do that! > > To do it case by case I would d