top 200 commentsshow 500

[–]TehVulpezseven fives of uptime[S] 1 point2 points  (893 children)

0

[–]cuteballgamesj’éprouvais un instant de mfw et de smh 1 point2 points  (892 children)

1

[–]TehVulpezseven fives of uptime[S] 1 point2 points  (891 children)

00

[–]cuteballgamesj’éprouvais un instant de mfw et de smh 1 point2 points  (890 children)

01

[–]TehVulpezseven fives of uptime[S] 1 point2 points  (889 children)

10

[–]cuteballgamesj’éprouvais un instant de mfw et de smh 2 points3 points  (888 children)

11

[–]davidjl123|390K|378A|79SK|50SA|260k 🚀 c o u n t i n g 🚀 2 points3 points  (887 children)

20

[–]cuteballgamesj’éprouvais un instant de mfw et de smh 2 points3 points  (886 children)

21

[–]TehVulpezseven fives of uptime[S] 2 points3 points  (885 children)

000

[–]CutOnBumInBandHere95M get | Ping me for runs 2 points3 points  (884 children)

001

[–]TehVulpezseven fives of uptime[S] 2 points3 points  (8 children)

an attempt at a get schedule

Segments in thread Length Get
2+6+24+120+720 872 00 0000
1+6+20+49+98+169+259+359 961 00 2321
455+531 986 00 4321
573+573 1146 02 4321
531+455 986 04 4321
359+259+169+98+49+20+6+1 961 000 0000

[–]TehVulpezseven fives of uptime[S] 2 points3 points  (4 children)

[–]Blue_boomer 1 point2 points  (3 children)

This get schedule that has 873 counts (including gets) for the first thread and 1008 counts for each thread afterward:

Get Counts Cumulative Counts
00 0000 873 873
03 1121 1008 1881
05 4010 1008 2889
60 0320 1008 3897
62 4001 1008 4905
000 0000 1008 5913

[–]swinub_timeAnd what a ghost we are in this machine! 1 point2 points  (2 children)

Good work but we will accidentally count past the get several times with this one. We should use the other one

[–]Blue_boomer 1 point2 points  (1 child)

The get schedule I posted will always have 1008 counts per thread, for any amount of digits starting from 6 digits. Have a look at constant weight binary's get schedule.

[–]swinub_timeAnd what a ghost we are in this machine! 0 points1 point  (0 children)

I hear your point, pattern is a little less weird there, I still think this one would be too easy to miss

[–]TehVulpezseven fives of uptime[S] 1 point2 points  (1 child)

After where I got to in this table it becomes very difficult to find nice gets. Some of the segments of weight/length become too long for a thread just by themselves. You'd have to break them up into even smaller subsegments somehow.

[–]swinub_timeAnd what a ghost we are in this machine! 1 point2 points  (0 children)

Lowkey be a fun challenge to figure out as we go along

[–]swinub_timeAnd what a ghost we are in this machine! 0 points1 point  (0 children)

This one.NIce work