On Sat, 20 Jan 2007 03:46:47 -0800, Jaap Spies <[EMAIL PROTECTED]> wrote:
> Nick Alexander wrote:
>> May I suggest that sloane_functions be split into pieces, perhaps one
>> sequence per file?  It takes for ever to run the tests, and it's
>> just... bulky.  Too big.
>>
> All tests passed!
> Total time for all tests: 10.5 seconds

When I sent my previous email I forgot one thing Nick might have meant.
Say you want to doctest just the docs for one sequence.  If it is in
its own file, then it will take only 2 seconds say (instead of 10.5,
then 20, then 30...).

> But you are right. There are 125k sequences in the OEIS, growing with a rate
> of ten to twenty a day, not all very interesting, but anyway.
> When sloane_functions.py grows with 10 sequences a day we will never catch up!

I think yours and Nick's work on Sloane sequences in SAGE is extremely valuable
for SAGE even if you never get more than 1% coverage.  It motivates development
of other code that is needed to compute the sequences, which is good for helping
the development of SAGE.

Is there any way to see which sequences in OEIS are the most "popular", i.e.,
are the top results for queries?

> You can cut down on doctesting, not on examples because of the educational 
> impact.
> Users of the OEIS are probably occasional SAGE users, so examples and code
> inspection are important features.
>
> For the moment I think it is best to concentrate on sequences with the 
> keywords
> 'core' and 'nice' (or 'hard'!).
>
> One sequence per file? There are groups of sequences built around a theme 
> (recurrence, etc.),
> or depending on some other sequence. Will it be possible to group sequence

It makes sense to build the implementations around themes.

>> Also, do we envision the network code in databases/sloan eventually
>> being unified with the sloane_functions code?
>>
>
> This seems a good idea. For a sequence not implemented yet, switch to the
> Internet or the database to give some information: name, numbers and a link
> to the OEIS.

Yes.

Someone clever could even make

    sloane.A949832   (something where nothing has been implemented)

dynamically generates an object that looks up online or in a local database
the description and some terms.  This would be done by overloading __getattr__,
I think.

William

--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---

Reply via email to