- Welcome to BOINC-AUSTRALIA FORUM.
News:
If you have forgotten your password use your email address to reset HERE
Recent posts
#21
WORD LINK / Re: Word Link 2
Last post by Dave Studdert - September 17, 2026, 11:23:43 PMcrackle
#26
Prime Crunch / Re: I like this one.
Last post by Dingo - September 15, 2026, 05:34:26 PMI have now found 44 Primes in Primecrunch. I am hoping to find a Prime over a million digits with one of my RPI's.
My latest RPI prime is not in the top 1000 but getting there.
My latest RPI prime is not in the top 1000 but getting there.
Code Select
5,479 · 2560,445 − 1
Prime
168,715 digits
Linux / arm64
Prime, and ours. primecrunch found it on 15 September 2026.
The record
oldest first
2026-09-15 01:43
Fermat test: probable prime
Dingo · Linux / arm64 · 01:16 → 01:43, 26m 54s compute
2026-09-15 02:43
LLR proof: prime
Dingo · Linux / arm64 · 01:43 → 02:43, 59m 44s compute
15 Sep 2026
[b]Entered the public record
Dingo; primecrunch.com; PSieve; srsieve; PRST · pzktupel.de[/b]
Where it stands
by digit count
7,409,172
largest known Riesel prime with k below 10,000: 69·2^24612729-1, 13 Aug 2024
1,415,549
largest primecrunch discovery: 1011·2^4702339-1, world rank 927
923,213
t5k top 5,000 floor: below this line no world rank exists, and the floor only rises
168,715
This number. 7,123rd largest of the 160,580 known Riesel primes with k below 10,000.
754,498 digits short of the t5k list; n would need to reach about 3,066,800
127th largest of the primes primecrunch has discovered.
Its neighbourhood
k 5,479 →
n 500,000 – 999,999, the 500,000-wide cell this candidate falls in
483,060 done
16,940 to do
Ready
16,864
Allocated
76
Prime
1
Probable
1
Completed frontier
-
Unverified frontier
499,999
#28
Prime Crunch / Re: Project Update
Last post by Dingo - September 15, 2026, 04:02:15 PMThe first Challenge on Primecrunch has been set. It is to flesh out any problems as this is a new feature to this platform.
https://primecrunch.com/challenges/1/sweepstakes
https://primecrunch.com/challenges/1/sweepstakes
QuoteRuns for 7 days. Work on n from 1 to 499,999 and any k, allocated from Sat, 19 Sept 2026, 10:00 AEST and completed by Sat, 26 Sept 2026, 10:00 AEST. Every job type counts, and the score is ops.
QuoteA team's score here counts only members who were in the team when the challenge started. Everyone's work still earns their team credit on the Teams page as usual. How challenges work.
Nearly 38 million candidates stand between the sweep and n = 500,000. For one week, every machine that enters is racing the same ground.
The ground
Below n = 500,000 there are about 65 million candidates across the 4,500 odd k from 1,001 to 9,999. Everything below n = 100,000 is done. The sweep, which always takes the lowest untested n in the project, is at n = 170,000. Each candidate there is a number of about 51,000 digits, and by n = 500,000 they are over 150,000 digits long.
In the seven days before this challenge was set, 3.44 million jobs finished below n = 500,000. This week we find out what that number looks like when people are competing for it.
Why this range
We keep the residual of every test, so every result here adds to a complete, checkable record of each candidate below n = 500,000, the composites as well as the primes. Primes found here are below the t5k top 5000 floor, which is over 900,000 digits, but every find is recorded and credited on primecrunch to the member whose machine tested it.
How to win
Enter before the start. Entry closes the moment the challenge begins, for members and teams.
Own a team? Enter it too. A team scores the work of everyone who was in it when the challenge started.
Set up your work ranges so your machines are on work that counts. How is below.
Score is ops, not job count. A test at n = 450,000 is worth more than one at n = 170,000 and takes longer to run, so the leaderboard measures the work your machines did, whichever part of the range they did it in.
No stockpiling. Only work allocated after the start counts.
The top three members and the top three teams win gold, silver and bronze. Medals go on member profiles and in team medal cabinets.
Setting up your work ranges
Your machines take work in the order set on your work ranges page, starting from the top row. With nothing set up, they take work from the shared k at the bottom of that page, whose untested n are large and may well be above 500,000. A few minutes on the page before the start makes sure every machine is on work that counts.
The simple way: Smallest available work
Open work ranges and press + Smallest available work.
A new row is added in a tier of its own at the bottom. Drag it to the top by its grip, or use Move up on its ... menu until it is first. Anything above it is tried first, so it needs to be at the top.
This row hands out the lowest n that nobody has reserved, any k, which is n = 170,000 as this is written. Every test it gives your machines is inside the challenge, and it does not use any of your k quota.
Using k you have reserved
Press Reserve a k. The Quick wins list starts lowest in n, which suits this challenge, or type k values into the box at the bottom.
On the row's ... menu choose Edit n window and machines and set n to to 499,999. The window includes the n you type, and 499,999 is the last n this challenge counts, as the rules at the top of this page say.
Move the row to the top, as above.
Optionally turn on the row's release k switch, so the k goes back to the pool when its window is finished, and put a + Smallest available work row directly below it, so your machines carry on with work that counts when it does.
Only some of your machines
Every row can be limited to particular machines: Edit machines on a Smallest available work row, or Edit n window and machines on a k. Put the machines you want in the challenge on the challenge row, and the rest carry on with your usual plan below it.
Just before the start
Work allocated before the start does not count, even if it finishes during the challenge, and that includes numbers already waiting in your machines' queues. If you want every test to count from the first minute, give those back just before the start from your queued work page, or lower the backlog of a machine under remote control, which hands back whatever it holds above the new number.
Watch the sweep move while it runs. How challenges work.
Suggested by Carlos on the forum.