- Dec 11, 1999
- 16,251
- 3,846
- 75
Welcome to the most grueling PrimeGrid challenge of the year, the Calendula challenge! Your mission, should you choose to accept it, is to complete as many Prime Sierpinski Problem LLR tests as you can, as quickly and correctly as you can. Because these work units take longer than any other challenge WUs this year, you will have a full thirteen days, from September 24 to October 7, to work on them.
What you need:
What won't help (but won't hurt either):
Work not downloaded and uploaded within the challenge will not be counted. Should you not be able to be in front of one or more computers at that time, see the challenge strategy thread for ways to start and finish on time.
Good luck! This message will self-destruct in a few hours! But I'm sure it will come back when the forum downtime is over.
What you need:
- One or more fast x86 processors. (Even slow ones might do some work!)
- new! Having hyperthreading off on i3/5/7s is said to help.
- All of those processors running stably. One good way to check that is to run PPS or SGS LLR for a few days. If those make your processor too hot, try TRP LLR. If you get any errors, your processor probably isn't stable at your current clock/voltage.
- Windows, Linux, or MacOS 10.4+.
- BOINC, attached to PrimeGrid (http://www.primegrid.com/).
- Your PrimeGrid Preferences with only "Prime Sierpinski Problem (LLR)" selected in the Projects section.
- Patience! These are long WUs. (Not as long as Seventeen or Bust, but each will probably take at least two days each.)
What won't help (but won't hurt either):
- A 64-bit OS. (But if it's Linux, type "sudo apt-get install ia32-libs".)
- A large amount of RAM.
- Any video cards.
Work not downloaded and uploaded within the challenge will not be counted. Should you not be able to be in front of one or more computers at that time, see the challenge strategy thread for ways to start and finish on time.
Good luck! This message will self-destruct in a few hours! But I'm sure it will come back when the forum downtime is over.
Last edited: