This is a page I put together inspired by schickel's AllSeq.txt, combined with the fact that finding a recent copy was a pain in the butt. This is supposed to make things easier (including easier sorting and data mining). This uses Syd's wonderful Factor DataBase to get FDB's last known information about an Aliquot sequence. As such, if a worker hasn't updated the DB in a while or the DB has errors in a sequence, well... there's not much I can do about it.
whose work I found thanks to StackOverflow. DataTables in turn depends on
It's got some awesome features: you can do multi-column sorts by clicking the primary column, and then shift-clicking the secondary columns (in order of priority); it sorts the table quickly, thanks to deferred rendering (meaning the sorted data is only rendered as you scroll). This latter feature is why hitting Page Down repeatedly causes lag. Some potential uses of the multi-sort include finding the shortest sequence of size 111, or all sequences with size < 115 with a certain driver. I also encourage you to use the search/filter feature (one of my favorite uses is searching by name), or the exclusion checkboxes.
If you find a sequence you would like to extend, you should reserve it in MersenneForum.org's Aliquot sequence reservations thread; That's the source for the reservations shown in this table. Also note that if the sequence is less than 10,000, there's a good chance it's being worked on by Christophe Clavier. All such reservation requests should be emailed to him. Also keep in mind that his work may not be in the FDB (and thus not in this table). Sequences between 10,000 and 100,000 should also be checked further at MersenneForum, because this range was worked on by Clifford Stern. See this MF thread for more details about or to ask about the status of sequences in these ranges.
If you'd like to have the basic information available in the old AllSeq.txt format (to e.g. perform an analysis with grep, etc.), you can find that here.
To keep load on the FDB to a minimum, the Python script which makes this page is intended to update 55 sequences per hour, meaning no sequence should be more than a week out of date. Each sequence lists the date it was last updated. Each update is run at 7 past the hour, but the page won't actually change until a few minutes after that (depending on the FDB). To further reduce FDB load, the script queries the FDB ID of the last unfactored line from the previous update. Only if that line is factored does the script actually request the much heavier sequence status page.
Drivers and guides: I wrote a short Python module, based on the definitions and notes from Clifford Stern's Analysis page, in order to classify the sequences in the table. The only exception to Clifford's definitions I use is to present the power of two as a "guide" if a "proper" guide is lacking. The guide column does show proper drivers, though there is a checkbox to exclude sequences controlled by a driver (as well as a box to exclude sequences with a (pesky) 3 in them). The class shown is exactly the "class" described by Clifford in his page.
At kar_bon's suggestion, the script now also records the FDB ID of the last line, to try and detect merges. The main drawback is that a merged sequence could advance between getting the info for one branch and the info of the other, meaning that such a merge would go undetected. The merge detection script is run once a day, so theoretically if everyone does updates only once a day, no merges will be missed. (On the other hand, I certainly don't follow that rule :P)
At fivemack's suggestion, the script now also tracks the last time a sequence was lengthened. If, at the current update, a sequence is longer than at the previous update, the "Recent Progress" column displays the total increase in length. If a sequence has not been extended, then the date of the last extension is shown. (The FDB doesn't seem to have recorded dates before 2011-03-17.)
As you've probably noticed, this table is also capable of reading the current reservations from the lead post of the reservations thread; the time reported is the last edit date of that post. The reservations are all updated every hour, unlike the sequences themselves.
I'm also working on a statistics page based on the data in the table. Check back every so often for new features.
If you want to request a feature, report a bug, offer an idea for the stats page, or otherwise discuss the table, please use this MF thread.
I also borrowed some of PrimeNet's table formatting.
All times are UTC. Reservations are as of 27 Apr 17 18:32.
These sequences are currently broken: none currently.
|Sequence||Size||Index||Hidden ID||Guide||Known Factors||Cofactor Size||Class||Last Updated||Recent Progress||Reservation||Hidden Driver Bool|