flipper77 wrote:So far, the "b3s23/C1" census has accumulated almost 300 million soup results in just a little over 3 days, I'm amazed.
And there's just been an overnight explosion to 429 million soups. It's very fortunate that I decided to use 64-bit integers for everything, now that we have too many blocks and blinkers for (signed) 32-bit integers:
http://catagolue.appspot.com/census/b3s23/C1/xp2
flipper77 wrote:I have a minor suggestion for apgsearch that's not terribly important: have it find what version is available online, and if it doesn't match the version you have, it prompts you to go to the appropriate location to download the latest version if you want to get it.
Agreed. It would be nice to auto-update, but Golly imposes an annoying security restriction to prevent one script from executing another.
I hope those soups get moved over to the b3s23/C1 census eventually, but I wouldn't know if that's possible.
It's possible, but I would have to write another servlet to accomplish that.
Meanwhile, the actual b3s23/D4_+4 census has found a genuinely new (i.e. not featured in jslife) p30 shuttle hassler:
http://catagolue.appspot.com/object/xp3 ... 0103/b3s23
Nathaniel wrote:I don't have much else to say, but I'm finally running some soups now.
Thanks! I've seen you appear to be using a quad-core processor, so you're generating plenty of results!
Nathaniel wrote:One question: are the URLs (like
http://catagolue.appspot.com/object/xq3 ... dhb5/b3s23) fairly stable, or might they change in the coming weeks? I'd like to add some of them as external links in the wiki.
Yes, the /object and /census links are stable (the pages themselves may be updated to include more information, but the URLs will remain the same). The /haul endpoints, on the other hand, are likely to be cleaned periodically when I need more room in the Datastore. In particular, there's a 1GB free limit, of which I'm about 1% of the way to reaching, beyond which I would need to pay for extra storage (still very cheap, but nonzero).
Although I may need to enable billing long before then, not due to the storage but rather the amount of load on the server (Catagolue is already really close to the daily limits for read/write operations and CPU time).