-
-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New interface with OEIS #10358
Comments
comment:2
Crap, this is a dup of #10056 |
comment:3
Hi, the aim of #10056 was to migrate every url in sage that was dealing with Sloane's database at once (not only I added the more atomic functions in
I don't really know what to do with the broken functions:
Also, maybe all those functions should be renamed by replacing sloane by oeis ? This may be too early since i guess most people know more about Sloane than about oeis. In such a case, what is the procedure/convention to ensure backward compatibility ? At the end, we could have a daily crontab to check when the oeis changes its html template, and adapt the parsers accordingly. Better, we could ask them to provide an online standard query system, but if i understand a discussion in the nmbrthry mailing-list, this may not be their whish. Ciao, |
comment:6
Salut Thierry, Rather than having a bunch of functions to return the various pieces of a Sloane result, there could be a single object from which one could query the pieces via methods. Something like:
Actually, Anders Claesson [1] had implemented a prototype of this feature during FPSAC'09, and his demo was quite cool. I guess he would agree to give his code away for someone else to finalize it and merge it into Sage. But maybe that should be the topic of a separate ticket. |
comment:10
By the way, if you need to play with OEIS now, here is the current version of the patch in preparation, on sage-combinat: http://combinat.sagemath.org/patches/file/0506836c7c66/sloane_new_website_parsers-tm.patch The methods still parse the new website correctly, but i didn't put everything in a single class yet as Nicolas suggested. |
comment:11
Oh, no particular hurry. I just happened to notice OEIS was broken, and was surprised to find that this ticket was closed, so I asked leif to reopen it. Glad to hear there is a patch in the works. If possible could you post it here once in a while? As the ticket hadn't been changed for 9 months I thought nobody was working on it. Thanks! |
Changed keywords from none to Cernay2012 |
comment:13
Thierry, can you upload your patch here? Was it ready? Sébastien |
comment:14
See also #13884, though it should be dealt with here. And FYI, we would want to make sure that this also works:
Which of course it should once this is done, but wanted to point it out since it's in a different file. |
comment:15
6 months old question left unanswered.. Time for a ping Nathann |
comment:16
http://combinat.sagemath.org/patches/log/tip/sloane_new_website_parsers-tm.patch Nothing happened for two years, and the patch is still sitting in the combinat queue without being posted on trac. |
comment:17
"The Sage-Combinat experience" So, should we set this ticket to Nathann |
comment:18
Hi, sorry for the delay, the version on the combinat queue is not the good one, during the Cernay combinat days in last february (less than one year!), i build a new class named oeis, that allows to get all kind of information from the oeis db (cross references, web links, ...). I upload a temporary version here so that you can try it, but the documentation is not finished, and non backward-compatible changes may still appear. Thierry |
comment:48
Patchbots are sometimes dumb. Let us try again to teach them ! apply trac_10358-oeis-tm.patch,trac_10358-oeis-review_1-tm.patch,trac_10358-oeis-review_2-tm.patch,trac_10358-oeis-review_3-nc-tm.patch |
comment:49
Almost good ... Let me try again apply trac_10358-oeis-tm.patch,trac_10358-oeis-review_1-tm.patch,trac_10358-oeis-review_2-tm.patch,trac_10358-oeis-review_3-nc-tm.patch |
comment:50
pfff. Last try apply only trac_10358-oeis-tm.patch,trac_10358-oeis-review_1-tm.patch,trac_10358-oeis-review_2-tm.patch,trac_10358-oeis-review_3-nc-tm.patch |
comment:51
ok, it was failing because the patchbots do not like invisible characters (and neither do I). This should work: apply trac_10358-oeis-tm.patch trac_10358-oeis-review_1-tm.patch trac_10358-oeis-review_2-tm.patch trac_10358-oeis-review_3-nc-tm.patch |
Attachment: trac_10358-oeis-review_3-nc-tm.patch.gz Tested on 5.12 |
Dependencies: #15245 |
comment:53
This needs to be rebased to #15245. |
rebased after #15245 |
This comment has been minimized.
This comment has been minimized.
comment:54
Attachment: trac_10358-oeis-tm_rebase.patch.gz The rebase is a shift in sage/matrix/matrix2.pyx apply trac_10358-oeis-tm_rebase.patch trac_10358-oeis-review_1-tm.patch trac_10358-oeis-review_2-tm.patch trac_10358-oeis-review_3-nc-tm.patch |
comment:55
The patches apply now. |
Merged: sage-5.13.beta2 |
comment:57
Joy, joy, joy is all around us! Hail to Thierry, Hail to Nathann! |
comment:58
I use this closed ticket to touch the interested people. In March 2017 I got:
and now I get with Sage 8.3:
I have two questions:
|
comment:59
Replying to @zimmermann6:
The
You can get help about
You can see that there is a Also, OEIS will only send the 100 first results even if you do:
This is why there is a |
comment:60
Thierry, thank you for your answer. Of course I had tried
thus the documentation seems to differ from the code. Should I open a new ticket for that? |
The sloane_find command, which parses output of a webpage, is broken for years due to the Sloane sequence webpage being rewritten. It silently always finds nothing.
The aim of this ticket is to propose a new interface with OEIS http://oeis.org/
Apply:
Depends on #15245
CC: @sagetrac-sage-combinat @williamstein @kini @jpflori @sagetrac-chrisjamesberg @VivianePons
Component: combinatorics
Keywords: Cernay2012 days49
Author: Thierry Monteil
Reviewer: Nathann Cohen
Merged: sage-5.13.beta2
Issue created by migration from https://trac.sagemath.org/ticket/10358
The text was updated successfully, but these errors were encountered: