Welcome to the 50 years First ARPANET Connection Challenge

Arpanet carried its first message on October 29, 1969, laying the foundation for today’s networked world. Fifty years later, more than 4 billion people have internet access, and the number of devices connected to IP networks is more than double the global population. The name Arpanet came from the U.S. military arm that funded it, the Advanced Research Projects Agency. When Arpanet was created, it connected five sites: UCLA, Stanford, UC Santa Barbara, the University of Utah and BBN Technologies.

The first Arpanet node was set up at UCLA on Aug. 30, 1969. The second node, at the Stanford Research Institute, was set up on Oct. 1. The first data message sent between the two networked computers occurred on Oct. 29, when UCLA computer science professor Leonard Kleinrock sent a message from his school's host computer to another computer at Stanford. Kleinrock intended to write "login" to start up a remote time-sharing system, but the system crashed after only two letters, "l" and "o", were transmitted.

In 1983, the U.S. Defense Department spun-off MILNET, which was the part of Arpanet that carried unclassified military communications. (MILNET was later renamed the Defense Data Network and finally NIPRNET, for Non-classified IP Router Network.) Arpanet was renamed the internet in 1984, when it linked 1,000 hosts at university and corporate labs.

The eighth Challenge of the 2019 Challenge series is a 5 day challenge celebrating 50 years since the first ARPANET Connection. The challenge is being offered on the 321 Prime Search (LLR) application.

To participate in the Challenge, please select only the 321 Prime Search LLR (321) project in your PrimeGrid preferences section. The challenge will begin 24th October 2019 00:00 UTC and end 29th October 2019 00:00 UTC.

Application builds are available for Linux 32 and 64 bit, Windows 32 and 64 bit and MacIntel. Intel CPUs with FMA3 capabilities (Haswell, Broadwell, Skylake, Kaby Lake, Coffee Lake) will have a very large advantage, and Intel CPUs with dual AVX-512 (certain recent Intel Skylake-X and Xeon CPUs) will be the fastest.

ATTENTION: The primality program LLR is CPU intensive; so, it is vital to have a stable system with good cooling. It does not tolerate "even the slightest of errors." Please see this post for more details on how you can "stress test" your computer. Tasks on one CPU core will take 12 hours on fast/newer computers and 2 days+ on slower/older computers. If your computer is highly overclocked, please consider "stress testing" it. Sieving is an excellent alternative for computers that are not able to LLR. :)

Highly overclocked Haswell, Broadwell, Skylake, Kaby Lake or Coffee Lake (i.e., Intel Core i7, i5, and i3 -4xxx or better) computers running the application will see fastest times. Note that PPS-DIV is running the latest AVX-512 version of LLR which takes full advantage of the features of these newer CPUs. It's faster than the previous LLR app and draws more power and produces more heat. If you have certain recent Intel Skylake-X and Xeon CPUs, especially if it's overclocked or has overclocked memory, and haven't run the new AVX-512 LLR before, we strongly suggest running it before the challenge while you are monitoring the temperatures.

Please, please, please make sure your machines are up to the task.

Multi-threading optimisation instructions

Those looking to maximise their computer's performance during this challenge, or when running LLR in general, may find this information useful.

• Your mileage may vary. Before the challenge starts, take some time and experiment and see what works best on your computer.
  
• If you have an Intel CPU with hyperthreading, either turn off the hyperthreading in the BIOS, or set BOINC to use 50% of the processors.
  
  
  • If you're using a GPU for other tasks, it may be beneficial to leave hyperthreading on in the BIOS and instead tell BOINC to use 50% of the CPU's. This will allow one of the hyperthreads to service the GPU.

  
  

• The new multi-threading system is now live. This will allow you to select multi-threading from the project preferences web page. No more app_config.xml. It works like this:
  
  
  • In the preferences selection, there are selections for "max jobs" and "max cpus", similar to the settings in app_config.
    
  • Unlike app_config, these two settings apply to ALL apps. You can't chose 1 thread for SGS and 4 for SoB. When you change apps, you need to change your multithreading settings if you want to run a different number of threads.
    
  • There will be individual settings for each venue (location).
    
  • This will eliminate the problem of BOINC downloading 1 task for every core.
    
  • The hyperthreading control isn't possible at this time.
    
  • The "max cpus" control will only apply to LLR apps. The "max jobs" control applies to all apps.

  
  

• If you want to continue to use app_config.xml for LLR tasks, you need to change it if you want it to work. Please see this message for more information.
  
• Some people have observed that when using multithreaded LLR, hyperthreading is actually beneficial. We encourage you to experiment and see what works best for you.

Time zone converter:

The World Clock - Time Zone Converter

NOTE: The countdown clock on the front page uses the host computer time. Therefore, if your computer time is off, so will the countdown clock. For precise timing, use the UTC Time in the data section at the very top, above the countdown clock.

Scoring Information

Scores will be kept for individuals and teams. Only tasks issued AFTER 24th October 2019 00:00 UTC and received BEFORE 29th October 2019 00:00 UTC will be considered for challenge credit. We will be using the same scoring method as we currently use for BOINC credits. A quorum of 2 is NOT needed to award Challenge score - i.e. no double checker. Therefore, each returned result will earn a Challenge score. Please note that if the result is eventually declared invalid, the score will be removed.


At the Conclusion of the Challenge

We kindly ask users "moving on" to ABORT their tasks instead of DETACHING, RESETTING, or PAUSING.

ABORTING tasks allows them to be recycled immediately; thus a much faster "clean up" to the end of an LLR Challenge. DETACHING, RESETTING, and PAUSING tasks causes them to remain in limbo until they EXPIRE. Therefore, we must wait until tasks expire to send them out to be completed.

Please consider either completing what's in the queue or ABORTING them. Thank you. :)

About 321 Search

321 Search began in February 2003 from a post by Paul Underwood seeking help from interested parties in a prime search attempt of the form 3*2^n-1. The initial goal was to build upon the completed work at Proth Search and extend the list of known primes to an exponent of 1 million (n=1M). That was quickly achieved so they advanced their goal to finding a mega prime for which they sieved up to n=5M.

As seen on PrimeGrid's front page, that goal was achieved on 23 Mar 2008, 7:57:28 UTC, when Dylan Bennett of Canada returned a positive result for n=4235414 (3*2^4235414-1). official announcement | decimal representation

PrimeGrid added the +1 form and continues the search up to n=25M.

Primes known for 3*2^n+1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 5, 6, 8, 12, 18, 30, 36, 41, 66, 189, 201, 209, 276, 353, 408, 438, 534, 2208, 2816, 3168, 3189, 3912, 20909, 34350, 42294, 42665, 44685, 48150, 54792, 55182, 59973, 80190, 157169, 213321, 303093, 362765, 382449, 709968, 801978, 916773, 1832496, 2145353, 2291610, 2478785, 5082306, 7033641, 10829346

Primes known for 3*2^n-1 occur at the following n (PrimeGrid's finds in bold & linked):
1, 2, 3, 4, 6, 7, 11, 18, 34, 38, 43, 55, 64, 76, 94, 103, 143, 206, 216, 306, 324, 391, 458, 470, 827, 1274, 3276, 4204, 5134, 7559, 12676, 14898, 18123, 18819, 25690, 26459, 41628, 51387, 71783, 80330, 85687, 88171, 97063, 123630, 155930, 164987, 234760, 414840, 584995, 702038, 727699, 992700, 1201046, 1232255, 2312734, 3136255, 4235414, 6090515, 11484018, 11731850, 11895718

What is LLR?

The Lucas-Lehmer-Riesel (LLR) test is a primality test for numbers of the form N = k*2^n − 1, with 2^n > k. Also, LLR is a program developed by Jean Penne that can run the LLR-tests. It includes the Proth test to perform +1 tests and PRP to test non base 2 numbers. See also:

• Lucas-Lehmer-Riesel test (WIKI)
  
• Download LLR by Jean Penné
  

(Edouard Lucas: 1842-1891, Derrick H. Lehmer: 1905-1991, Hans Riesel: 1929-2014).
____________

Some things change drasticaly

The first-generation Interface Message Processors (IMPs) were built by BBN Technologies using a rugged computer version of the Honeywell DDP-516 computer, configured with 24KB of expandable magnetic-core memory,

but the system crashed

For those of us in the affected timezone, or other timezones that may have a daylight savings change, be aware this will start 24th 01:00BST (& end 29th 00:00UT).

Under the European system for summer time ("daylight saving time"), summer time ends on 01:00 UTC the last Sunday of October (which is October 27 this year). So in all time zones in Europe that follow this rule (EU and some nearby countries), clocks will be set back in the same moment. /JeppeSN

Most communities do trick or treat the Saturday or Sunday before October 31st.

Most communities do trick or treat the Saturday or Sunday before October 31st.

This is why we display the current UTC time on the front page! :)

Taking that wording strictly, then this:

received BEFORE 29th October 2019 00:00 UTC

means midnight at the beginning of 29th October. If that is not what is meant, then there are 2 ways of indicating midnight at the end of a day, depending on your googling results ;) :

24:00
23:59:60 Although I personally don't like this one!

There's 3 days left to go until the challenge starts. If anyone wants to spin up some cloud servers for the challenge for the first time, it might be a good idea to learn how it works before the challenge begins. First time users can make use of free introductory offers at various services. For the previous challenge, I created a writeup on how to get $50 free credit at Digital Ocean. It includes instructions for how to set up a server for running BOINC. An executive summary of the process is here.

The full instructions can be found here: https://www.primegrid.com/forum_thread.php?id=8831&nowrap=true#133770
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

**Public Service Announcement:**

Penguin and I both tried a shortcut to setting up cloud servers for a challenge by preconfiguring a custom image with BOINC already set up. **DO NOT DO THIS**

This seems to confuse the PrimeGrid server into thinking the cloud instances are all the same computer, and the result is that many tasks will get abandoned and may not count. If you intend to run multiple cloud instances to help in the challenge, you should set them up individually.

Good luck in the challenge!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

**Public Service Announcement:**

Penguin and I both tried a shortcut to setting up cloud servers for a challenge by preconfiguring a custom image with BOINC already set up. **DO NOT DO THIS**

This seems to confuse the PrimeGrid server into thinking the cloud instances are all the same computer, and the result is that many tasks will get abandoned and may not count. If you intend to run multiple cloud instances to help in the challenge, you should set them up individually.

Good luck in the challenge!

**Public Service Announcement:**

Penguin and I both tried a shortcut to setting up cloud servers for a challenge by preconfiguring a custom image with BOINC already set up. **DO NOT DO THIS**

This seems to confuse the PrimeGrid server into thinking the cloud instances are all the same computer, and the result is that many tasks will get abandoned and may not count. If you intend to run multiple cloud instances to help in the challenge, you should set them up individually.

Good luck in the challenge!

I suspect this might work if you "reset" the PrimeGrid project on each cloud instance before downloading work. But I'm not 100% sure on that.

That's definitely not the problem. The image was created *before* it was attached to any projects.

I think I know what the problem is, and, if so, I think I know how to correct it, but it's not worth the effort.

The challenge has started!

Good luck everyone!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Thanks Michael. I took a stab on this for current challenge and signed up using the referral code. I followed the instructions and those were very clear indeed. So far, I am pretty happy with the results. Hoping to continue the same in future challenges. :)

Thanks Michael. I took a stab on this for current challenge and signed up using the referral code. I followed the instructions and those were very clear indeed. So far, I am pretty happy with the results. Hoping to continue the same in future challenges. :)

I don't know how many people this represents, but as of a couple of hours ago there were 74 of those 3-core droplets participating in the challenge. They seem to be a very popular option. Not the absolute fastest server you can get, but it's probably the best value.

Enjoy the free $50 worth of computing!

I'm trying to limit myself to 5 droplets, but they're addicting!

Moar power!!!

Thanks Michael. I took a stab on this for current challenge and signed up using the referral code. I followed the instructions and those were very clear indeed. So far, I am pretty happy with the results. Hoping to continue the same in future challenges. :)

I don't know how many people this represents, but as of a couple of hours ago there were 74 of those 3-core droplets participating in the challenge. They seem to be a very popular option. Not the absolute fastest server you can get, but it's probably the best value.

Enjoy the free $50 worth of computing!

I'm trying to limit myself to 5 droplets, but they're addicting!

Moar power!!!

I signed up too. Also realize that $50 credit expires after 30 days! Fortunately, we have a couple of challenges here to use it up on.

If you do the math, each droplet costs about $0.50/day. Well, $0.53. If you're only going to do the 3-cores on PrimeGrid challenges, you should run about 6 droplets.

I learned through the API that my account, at least, has a limit of 10 droplets at once. So I guess you could save your entire credit for the next challenge.

Day 1 is complete!


Challenge: 50 years First ARPANET Connection
App: 7 (321-LLR)
(As of 2019-10-25 00:04:27 UTC)

18451 tasks have been sent out. [CPU/GPU/anonymous_platform: 18431 (100%) / 0 (0%) / 20 (0%)]

Of those tasks that have been sent out:

655 (4%) were aborted. [655 (4%) / 0 (0%) / 0 (0%)]
188 (1%) came back with some kind of an error. [188 (1%) / 0 (0%) / 0 (0%)]
5129 (28%) have returned a successful result. [5111 (28%) / 0 (0%) / 18 (0%)]
12479 (68%) are still in progress. [12477 (68%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

3437 (67%) are pending validation. [3422 (67%) / 0 (0%) / 15 (0%)]
1680 (33%) have been successfully validated. [1677 (33%) / 0 (0%) / 3 (0%)]
3 (0%) were invalid. [3 (0%) / 0 (0%) / 0 (0%)]
9 (0%) are inconclusive. [9 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15239808. The leading edge was at n=15141383 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 0.65% as much as it had prior to the challenge!

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

After 2 days:


Challenge: 50 years First ARPANET Connection
App: 7 (321-LLR)
(As of 2019-10-26 00:11:22 UTC)

29078 tasks have been sent out. [CPU/GPU/anonymous_platform: 29038 (100%) / 0 (0%) / 40 (0%)]

Of those tasks that have been sent out:

938 (3%) were aborted. [938 (3%) / 0 (0%) / 0 (0%)]
726 (2%) came back with some kind of an error. [726 (2%) / 0 (0%) / 0 (0%)]
12536 (43%) have returned a successful result. [12498 (43%) / 0 (0%) / 38 (0%)]
14878 (51%) are still in progress. [14876 (51%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

6262 (50%) are pending validation. [6242 (50%) / 0 (0%) / 20 (0%)]
6203 (49%) have been successfully validated. [6185 (49%) / 0 (0%) / 18 (0%)]
26 (0%) were invalid. [26 (0%) / 0 (0%) / 0 (0%)]
45 (0%) are inconclusive. [45 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15295998. The leading edge was at n=15141383 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.02% as much as it had prior to the challenge!

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Usually when I do the daily updates, I try do a little cheerleading and point out how fantastic everyone is doing. I didn't do that the last two days because I was rather busy.

In general, this year, we've been increasing traffic on challenge tasks to about 10 times the normal rate. That's decidedly up from previous years where 5 times was more common.

The previous challenge on PPS-DIV was a notable exception: It was only about 3 times normal. I suspect that's because being new and shiny and having short tasks, it was already essentially in "mini-challenge" mode because it was so new. There may not have been a lot of room for it to grow.

With the current 321-LLR challenge, we're back into 10x territory. After almost 71 hours, we're returning tasks at a bit more than 11 times normal, averaging over 5800 challenge tasks returned over the first half of the challenge.

That's pretty incredible.

So to everyone who participates, Thank You!!!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Three days are done; two to go!


Challenge: 50 years First ARPANET Connection
App: 7 (321-LLR)
(As of 2019-10-27 00:07:02 UTC)

39909 tasks have been sent out. [CPU/GPU/anonymous_platform: 39849 (100%) / 0 (0%) / 60 (0%)]

Of those tasks that have been sent out:

3384 (8%) were aborted. [3384 (8%) / 0 (0%) / 0 (0%)]
1223 (3%) came back with some kind of an error. [1223 (3%) / 0 (0%) / 0 (0%)]
21189 (53%) have returned a successful result. [21131 (53%) / 0 (0%) / 58 (0%)]
14113 (35%) are still in progress. [14111 (35%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

7871 (37%) are pending validation. [7842 (37%) / 0 (0%) / 29 (0%)]
13198 (62%) have been successfully validated. [13169 (62%) / 0 (0%) / 29 (0%)]
52 (0%) were invalid. [52 (0%) / 0 (0%) / 0 (0%)]
68 (0%) are inconclusive. [68 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15340170. The leading edge was at n=15141383 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.31% as much as it had prior to the challenge!

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Just one day to go!


Challenge: 50 years First ARPANET Connection
App: 7 (321-LLR)
(As of 2019-10-28 02:39:49 UTC)

50548 tasks have been sent out. [CPU/GPU/anonymous_platform: 50467 (100%) / 0 (0%) / 81 (0%)]

Of those tasks that have been sent out:

4193 (8%) were aborted. [4193 (8%) / 0 (0%) / 0 (0%)]
1840 (4%) came back with some kind of an error. [1840 (4%) / 0 (0%) / 0 (0%)]
30937 (61%) have returned a successful result. [30858 (61%) / 0 (0%) / 79 (0%)]
13578 (27%) are still in progress. [13576 (27%) / 0 (0%) / 2 (0%)]

Of the tasks that have been returned successfully:

8884 (29%) are pending validation. [8857 (29%) / 0 (0%) / 27 (0%)]
21861 (71%) have been successfully validated. [21809 (70%) / 0 (0%) / 52 (0%)]
108 (0%) were invalid. [108 (0%) / 0 (0%) / 0 (0%)]
84 (0%) are inconclusive. [84 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15389652. The leading edge was at n=15141383 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.64% as much as it had prior to the challenge!

____________
My lucky number is 75898⁵²⁴²⁸⁸+1

With about a day remaining in the challenge, it's time to remind everyone...

At the Conclusion of the Challenge

When the challenge completes, we would prefer users "moving on" to finish those tasks they have downloaded, if not then please ABORT the WU's (and then UPDATE the PrimeGrid project) instead of DETACHING, RESETTING, or PAUSING.

ABORTING WU's allows them to be recycled immediately; thus a much faster "clean up" to the end of a Challenge. DETACHING, RESETTING, and PAUSING WU's causes them to remain in limbo until they EXPIRE. Therefore, we must wait until WU's expire to send them out to be completed.

Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first. Also, be aware that merely shutting off a cloud server doesn't stop the billing. You have to destroy/delete the server if you don't want to continue to be charged for it.

Thank you!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first.

Thank you!

Likewise, if you're shutting down the computer for an extended period of time, or deleting the VM (Virtual Machine), please ABORT all remaining tasks first.

Thank you!

And remember, if you're using DigitalOcean, you need to "destroy" your droplets or they'll continue racking up charges!

The challenge is over!

Final statistics:


Challenge: 50 years First ARPANET Connection
App: 7 (321-LLR)
(As of 2019-10-29 00:00:03 UTC)

59276 tasks have been sent out. [CPU/GPU/anonymous_platform: 59178 (100%) / 0 (0%) / 98 (0%)]

Of those tasks that have been sent out:

7323 (12%) were aborted. [7323 (12%) / 0 (0%) / 0 (0%)]
2580 (4%) came back with some kind of an error. [2580 (4%) / 0 (0%) / 0 (0%)]
39786 (67%) have returned a successful result. [39689 (67%) / 0 (0%) / 97 (0%)]
9586 (16%) are still in progress. [9584 (16%) / 0 (0%) / 1 (0%)]

Of the tasks that have been returned successfully:

7846 (20%) are pending validation. [7826 (20%) / 0 (0%) / 20 (0%)]
31678 (80%) have been successfully validated. [31601 (79%) / 0 (0%) / 77 (0%)]
166 (0%) were invalid. [166 (0%) / 0 (0%) / 0 (0%)]
96 (0%) are inconclusive. [96 (0%) / 0 (0%) / 0 (0%)]

The current leading edge (i.e., latest work unit for which work has actually been sent out to a host) is n=15418603. The leading edge was at n=15141383 at the beginning of the challenge. Since the challenge started, the leading edge has advanced 1.83% as much as it had prior to the challenge!


Fantastic job everyone!


There's a really quick turnaround to the next challenge, which starts on Friday. Please note the next challenge starts four minutes after the hour. Tasks sent before 18:04:00 will not count, so be sure not to jump the gun!
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The cleanup now begins. I expect the cleanup will take 3 to 6 weeks.

Cleanup status:
Oct 28: 50 years First ARPANET Connection: 7907 tasks outstanding; 6683 affecting individual (294) scoring positions; 5619 affecting team (77) scoring positions.
Oct 29: 50 years First ARPANET Connection: 6483 tasks outstanding; 5427 affecting individual (287) scoring positions; 4399 affecting team (72) scoring positions.
Oct 30: 50 years First ARPANET Connection: 4459 tasks outstanding; 3757 affecting individual (280) scoring positions; 2144 affecting team (58) scoring positions.
Oct 31: 50 years First ARPANET Connection: 3454 tasks outstanding; 2828 affecting individual (270) scoring positions; 1428 affecting team (47) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

Why the orange color of the last line ?

The cleanup now begins. I expect the cleanup will take 3 to 6 weeks.

Cleanup status:
Oct 28: 50 years First ARPANET Connection: 7907 tasks outstanding; 6683 affecting individual (294) scoring positions; 5619 affecting team (77) scoring positions.
Oct 29: 50 years First ARPANET Connection: 6483 tasks outstanding; 5427 affecting individual (287) scoring positions; 4399 affecting team (72) scoring positions.
Oct 30: 50 years First ARPANET Connection: 4459 tasks outstanding; 3757 affecting individual (280) scoring positions; 2144 affecting team (58) scoring positions.
Oct 31: 50 years First ARPANET Connection: 3454 tasks outstanding; 2828 affecting individual (270) scoring positions; 1428 affecting team (47) scoring positions.
Nov 1: 50 years First ARPANET Connection: 2830 tasks outstanding; 2078 affecting individual (255) scoring positions; 998 affecting team (40) scoring positions.
Nov 2: 50 years First ARPANET Connection: 2379 tasks outstanding; 1579 affecting individual (236) scoring positions; 824 affecting team (34) scoring positions.
Nov 3: 50 years First ARPANET Connection: 2179 tasks outstanding; 1441 affecting individual (233) scoring positions; 651 affecting team (33) scoring positions.
Nov 4: 50 years First ARPANET Connection: 1855 tasks outstanding; 1144 affecting individual (208) scoring positions; 557 affecting team (30) scoring positions.
Nov 5: 50 years First ARPANET Connection: 1564 tasks outstanding; 964 affecting individual (197) scoring positions; 474 affecting team (29) scoring positions.
Nov 6: 50 years First ARPANET Connection: 1313 tasks outstanding; 784 affecting individual (178) scoring positions; 346 affecting team (22) scoring positions.
Nov 7: 50 years First ARPANET Connection: 1077 tasks outstanding; 598 affecting individual (156) scoring positions; 254 affecting team (15) scoring positions.
Nov 8: 50 years First ARPANET Connection: 908 tasks outstanding; 504 affecting individual (145) scoring positions; 148 affecting team (9) scoring positions.
Nov 9: 50 years First ARPANET Connection: 712 tasks outstanding; 372 affecting individual (125) scoring positions; 25 affecting team (8) scoring positions.
Nov 10: 50 years First ARPANET Connection: 554 tasks outstanding; 259 affecting individual (102) scoring positions; 12 affecting team (4) scoring positions.
Nov 11: 50 years First ARPANET Connection: 437 tasks outstanding; 166 affecting individual (80) scoring positions; 6 affecting team (3) scoring positions.
Nov 12: 50 years First ARPANET Connection: 361 tasks outstanding; 132 affecting individual (71) scoring positions; 1 affecting team (1) scoring positions.
Nov 13: 50 years First ARPANET Connection: 272 tasks outstanding; 88 affecting individual (54) scoring positions; 1 affecting team (1) scoring positions.
Nov 14: 50 years First ARPANET Connection: 198 tasks outstanding; 59 affecting individual (39) scoring positions; 0 affecting team (0) scoring positions.
Nov 15: 50 years First ARPANET Connection: 153 tasks outstanding; 38 affecting individual (27) scoring positions; 0 affecting team (0) scoring positions.
Nov 16: 50 years First ARPANET Connection: 125 tasks outstanding; 30 affecting individual (23) scoring positions; 0 affecting team (0) scoring positions.
Nov 17: 50 years First ARPANET Connection: 92 tasks outstanding; 10 affecting individual (10) scoring positions; 0 affecting team (0) scoring positions.
Nov 18: 50 years First ARPANET Connection: 61 tasks outstanding; 4 affecting individual (4) scoring positions; 0 affecting team (0) scoring positions.
Nov 19: 50 years First ARPANET Connection: 50 tasks outstanding; 3 affecting individual (3) scoring positions; 0 affecting team (0) scoring positions.
Nov 20: 50 years First ARPANET Connection: 43 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
Nov 21: 50 years First ARPANET Connection: 40 tasks outstanding; 1 affecting individual (1) scoring positions; 0 affecting team (0) scoring positions.
____________
My lucky number is 75898⁵²⁴²⁸⁸+1

The results are final!

Top 3 individuals:

1: Jesmar
2: vaughan
3: zunewantan

Top 3 teams:

1: Czech National Team
2: Aggie The Pew
3: SETI.Germany

Congratulations to the winners, and well done to everyone who participated.
See you at the Aussie, Aussie, Aussie! Oi! Oi! Oi! Summer Solstice Challenge!
____________