Catagolue Discussion Thread

[Hdjensofjfnen]

The new hauls to X3VI are NOT fake. I just connected about 30 4-core computers at my school to apgsearch.

"We just got these a few months ago! How can they be so slow already?"

[Moosey]

The new hauls to X3VI are NOT fake. I just connected about 30 4-core computers at my school to apgsearch.

"We just got these a few months ago! How can they be so slow already?"

Yeah, some staff at a certain school are gonna be very mad when they figure out what happened

Fortunately schools seem to think that they have somehow blocked anything that doesn't have to do with their curriculum so they don't check what you're doing on their computers

[testitemqlstudop]

The new hauls to X3VI are NOT fake. I just connected about 30 4-core computers at my school to apgsearch.

"We just got these a few months ago! How can they be so slow already?"

Yeah, some staff at a certain school are gonna be very mad when they figure out what happened

Fortunately schools seem to think that they have somehow blocked anything that doesn't have to do with their curriculum so they don't check what you're doing on their computers

The teachers let me.

[Moosey]

Whenever I upload soups to b2i34c6cen7c8s2-i3-q4c5a6e8/1x256 I get the following "error message":

Code: Select all

1414328 soups completed.
Attempting to contact payosha256.
Bad status: 500

Most other symmetries of the same rule work (e.g. D8_4) , just not 1x256

Can anyone explain why?

[wildmyron]

Recently submitted hauls for the r2b7t8s7t10/D2_+1 census appear to be stuck in the uncommitted queue. There were no errors reported by apgluxe.

Edit: As of 2019-12-12 this issue seems to have resolved itself or been silently fixed (in the last day or so).

[John Goodman]

Cheers to Frums for finding (yesterday) the first new xs38 in b3s23 in over six months: https://catagolue.appspot.com/object?ap ... rule=b3s23

Is the conwaylifebot Twitterbot permanently dead? Thought it would report stuff like this, but it hasn't peeped in over a year.

[dvgrn]

Cheers to Frums for finding (yesterday) the first new xs38 in b3s23 in over six months: https://catagolue.appspot.com/object?ap ... rule=b3s23

Is the conwaylifebot Twitterbot permanently dead? Thought it would report stuff like this, but it hasn't peeped in over a year.

Well, it's certainly glider-constructible, for what that's worth -- hopefully a bit more efficiently than cleaning up after this:

Code: Select all

x = 26, y = 44, rule = B3/S23
18bobo$19b2o$19bo3$23b2o$19bo2b2o$19b2o3bo$18bobo18$13bo$13bo$13bo4$6b
3o$6bo$7bo16b2o$3b2o19b2o$2bobo$4bo4$2o$b2o$o!

The ConwayLife Twitterbot was a project of codeholic's, who recently showed up again briefly but hasn't been active for a few years. There have definitely been other discoveries in the last year that would have been reported if the bot had still been active, but if someone wants to get in touch with codeholic about taking over the maintenance work, it might be possible to get it reactivated. (?)

[John Goodman]

And now another rare discovery in B3S23/C1: the first new yl2304 in over three years:
https://catagolue.appspot.com/object/yl ... 3cab/b3s23

This is only the fourth yl2304 to appear (or maybe fifth? yl2304_1_1553_7ddf... is listed in the census but has no soups).

[Ian07]

And now another rare discovery in B3S23/C1: the first new yl2304 in over three years:
https://catagolue.appspot.com/object/yl ... 3cab/b3s23

This is only the fourth yl2304 to appear (or maybe fifth? yl2304_1_1553_7ddf... is listed in the census but has no soups).

Yeah, I noticed a similar instance of that back in August but it looks like no one responded to me regarding why it had happened: viewtopic.php?p=81473#p81473

P.S. I'd suggest posting these results in the soup search results thread rather than here; this thread is mainly for discussion about the site in general.

[John Goodman]

P.S. I'd suggest posting these results in the soup search results thread rather than here; this thread is mainly for discussion about the site in general.

Ah, you're right, thanks.

[Hdjensofjfnen]

It may have been a few days ago, but we just passed five hundred trillion objects uploaded to b3s23/c1.

[wildmyron]

Recently submitted hauls for the r2b7t8s7t10/D2_+1 census appear to be stuck in the uncommitted queue. There were no errors reported by apgluxe.

Edit: As of 2019-12-12 this issue seems to have resolved itself or been silently fixed (in the last day or so).

I submitted a couple more hauls to the same census which are once again stuck in the uncommitted queue. Same situation for a bunch of hauls submitted to D4_+2 in the same LtL rule.

P. S. Welcome to the forum John Goodman, and nice going with your contribution to b3s23/C1!

[Ian07]

It may have been a few days ago, but we just passed five hundred trillion objects uploaded to b3s23/c1.

It was in fact today or yesterday; it's at 500,180,980,549,780 as I write this, and we've been consistently getting over 600B objects per day for a while.

[calcyman]

It may have been a few days ago, but we just passed five hundred trillion objects uploaded to b3s23/c1.

It was in fact today or yesterday; it's at 500,180,980,549,780 as I write this, and we've been consistently getting over 600B objects per day for a while.

Wow... suddenly the target of 10^15 objects no longer seems so distant.

[testitemqlstudop]

I will be uploading 9200 hauls to the X3VI census that were collected offline (10 million soups each, a total of 1.88 GB) They are NOT fake; I can e-mail a zip file to anyone interested.

[testitemqlstudop]

I've only uploaded 2000. Why are so many not getting committed? After each 20 minute update, no hauls from the queue are getting emptied.

https://gol.hatsya.co.uk/haul/b2c3aei4a ... ommitted=0

[calcyman]

I've only uploaded 2000. Why are so many not getting committed? After each 20 minute update, no hauls from the queue are getting emptied.

https://gol.hatsya.co.uk/haul/b2c3aei4a ... ommitted=0

There's a mixture of brown and green ones here, so it seems to be working:

https://gol.hatsya.co.uk/haul/b2c3aei4a ... jkq6c7c/C1

Note that only the most recent hauls (the 'back' of the queue) is visible from your link, whereas I believe the hauls are emptied from the 'front' of the queue.

[testitemqlstudop]

Okay, and the committed haul count is rising, too. I will continue uploading tomorrow. I hope I haven't broken any quota limits

[calcyman]

Okay, and the committed haul count is rising, too. I will continue uploading tomorrow. I hope I haven't broken any quota limits

There aren't any per-user quota limits. When the daily overall limit is exceeded, Catagolue goes down until midnight Pacific Time. All recent versions of apgsearch cope reasonably well with Catagolue downtime (or indeed lapses in Internet connectivity), and just keep adding to the existing haul until it can connect properly.

[testitemqlstudop]

I've only uploaded 2000. Why are so many not getting committed? After each 20 minute update, no hauls from the queue are getting emptied.

https://gol.hatsya.co.uk/haul/b2c3aei4a ... ommitted=0

There's a mixture of brown and green ones here, so it seems to be working:

https://gol.hatsya.co.uk/haul/b2c3aei4a ... jkq6c7c/C1

Note that only the most recent hauls (the 'back' of the queue) is visible from your link, whereas I believe the hauls are emptied from the 'front' of the queue.

Unfortunately it seems that no new hauls were removed from the queue and committed. Is every haul stuck?

[77topaz]

There is also a limit on how many hauls the script that commits hauls (it has a short name, but I forget what) can process in each pass it does every five to ten minutes, which may be what causing the X3VI hauls to not get committed because there are so many of them uploaded soon after each other.

[testitemqlstudop]

Wait, so it doesn't commit old, uncommitted hauls? That is a problem by itself...

[77topaz]

Wait, so it doesn't commit old, uncommitted hauls? That is a problem by itself...

To clarify since you may not have understood correctly, I didn't mean there was a limit on time in which a haul could be committed, I meant that per a given amount of time the process can only commit so many hauls and you uploaded a very large number of them in a short time.

[testitemqlstudop]

Yes, but now, the queue is not emptying at all. 15 hours ago, the committed haul count was 4707, and now it is still 4707. Shouldn't the queue be slowly emptying?

[calcyman]

Wait, so it doesn't commit old, uncommitted hauls? That is a problem by itself...

It's subtler than that. Currently, the situation is:

• Whenever a haul is uploaded to a census, a flag is set to indicate that there are uncommitted hauls;
• Whenever apgcron runs on a census, up to N (dependent on the census) uncommitted hauls are committed and the flag is unset.

Clearly that flag should only be unset when the end of the queue is fully exhausted; I'll amend that.

No hauls are lost at the moment, but it does mean that they can be in the queue forever until someone starts pinging that census with fresh hauls.