Tour De Primes 2018 (PrimeGrid)

Gilthanis

[H]ard|DCer of the Year - 2014
Joined
Jan 29, 2006
Messages
8,781
Tour de Primes 2018

Welcome to the 10th annual Tour de Primes. 2 is the first prime number...and the only even one. This makes it unique among prime numbers. Therefore, February is declared Prime month...being the 2nd month of the year. :) And there's no better way to pay homage to a prime number than to go out and find one. :) More precisely, a Top 5000 prime.

For the month of February, an informal competition is offered. There are no challenge points to be gained... just a simple rare jersey at the end of the month to add to your badge list. No pressure or stress other than what you put on yourself. :)

For 2018, we're adding four new badges you can win -- and these are available to everyone!


  • tdp_2018_red.png
    Red Jersey -- discoverer of largest prime
  • tdp_2018_yellow.png
    Yellow Jersey -- prime count leader (tiebreaker will be prime score)
  • tdp_2018_green.png
    Green Jersey -- points (prime score) leader
  • tdp_2018_polkadot.png
    Polk-a-dot Jersey -- on the 19th of February we'll have a "Mountain Stage" and award the Polk-a-dot Jersey to the one who finds the most primes on that day (tiebreaker will be prime score for that day).
  • tdp_2018_prime.png
    Prime badge -- awarded to everyone who finds an eligible prime during the month of February. This is a counter badge, so if you find more than one prime it will show how many you've found, up to 99.
  • tdp_2018_mega.png
    Mega prime badge -- awarded to everyone who finds a mega prime during February. This is a counter badge.
  • tdp_2018_ms_prime.png
    Mountain Stage prime badge -- awarded to everyone who finds a prime during the Mountain Stage. This is a counter badge.
  • tdp_2018_ms_mega.png
    Mountain Stage mega prime badge -- awarded to everyone who finds a mega prime during the Mountain Stage. This is a counter badge.


Results will be available at http://www.primegrid.com/challenge/tdp_2018.php.

As with the last few years, for all primes (BOINC and PRPNet) we're using the new reporting system whereby the prime's date of discovery determines whether it's eligible for the Tour de Primes. Prior to 2014, the date of verification for BOINC primes was used while the discovery date was used for PRPNet primes. The current system is more intuitive and fairer.

Note that SGS-LLR and GFN-15 are too small to be reported to the Top 5000 primes list and are therefore not eligible for the 2018 Tour de Primes.

Currently, the fastest opportunities to find Top 5000 primes is with the PPSE (LLR), and GFN-16 (65536) projects. Of course, should someone find a prime in the mega-prime searches, this would certainly give them a good shot at the green jersey. Not a guarantee, however, as in 2017 there were several mega primes found in the Tour de Primes. Overall, in 2017 we averaged more than one mega prime per week for the entire year, so you might need more than "merely" a mega prime to take home green. In 2017 there were 10 mega primes found during Tour de Primes.

At the current time, PRPNet is not running. If that changes, all ports in PRPNet would be available for the competition.

To participate in BOINC PPSE (LLR), GFN-16, or any other eligible LLR or Genefer project, all you have to do is select it in your PrimeGrid preferences. AP27 sequences are not reportable at T5K, so are not eligible for Tour de Primes.

Good Luck, have fun, and enjoy! :D
 
Copied from my PrimeGrid challenge series post. I know it looks like a lot but it pretty well covers all of their apps. Smaller ones can be posted for simplicity if someone was only going to run a single or a few of the sub projects:

App_config for all subprojects - let me know if something needs added
Change N to the number of CPU threads or the number of GPU's to use per work unit. Typically people use a fraction of a GPU to run multiple work units. For example: Setting <gpu_usage>0.5</gpu_usage> would tell BOINC to use half the GPU for each work unit resulting in 2 work units running on the card. The following line <cpu_usage>1</cpu_usage> would tell BOINC to dedicate a full CPU thread for each of the work units.

<app_config>
<app>
<name>pps_sr2sieve</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer17low</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer17mega</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer16</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer18</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>llrSOB</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrSOB</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrMEGA</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrMEGA</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrTRP</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTRP</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llr321</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llr321</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrPSP</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrPSP</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrTPS</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrTPS</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrWOO</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrWOO</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrCUL</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrCUL</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>llrPPS</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrPPS</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>ap27</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer_wr</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<name>llrPPSE</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrPPSE</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<name>llrSR5</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrSR5</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<name>llrESP</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrESP</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<name>genefer15</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer19</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>genefer20</name>
<gpu_versions>
<gpu_usage>N</gpu_usage>
<cpu_usage>N</cpu_usage>
</gpu_versions>
</app>
<app>
<name>gcw_sieve</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>gcw_sieve</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
<app>
<name>llrGCW</name>
<fraction_done_exact/>
</app>
<app_version>
<app_name>llrGCW</app_name>
<cmdline>-t N</cmdline>
<avg_ncpus>N</avg_ncpus>
<max_ncpus>N</max_ncpus>
</app_version>
<app>
</app_config>
 
Anyone gonna put much effort into this years event?
 
I'm out. Just chasing after my personal goals and helping us in FB.
 
I have a few random cores coming and going, but I wasn't going to plan on doing much this go round.
 
They did something new. If you go to the PG page, then to your account, then look at your tasks.

They either have 1st or nothing in the tine for the task description . If it says 1st, it means you beat the wingman.

If it has nothing, you were 2nd, IE the wingman. Nice new feature to see how well you are doing in the race to get the task in first.
 
Back
Top