Everyone can contribute.
It works on Windows, Linux, and Android.
Just contact us at nqueens.distributed@poeschl.io
to receive the program. Here you can get help setting up the program on your PC or mobile device.
Estimated Progress
—
tasks accepted
—
estimated remainingRemaining work divided by the rate at which work has recently been arriving. It
assumes participation stays as it is, so it moves whenever a machine joins or leaves, and it is
only offered once some class has been timed by this campaign itself.
—
active worker threadsThe worker threads currently reported by active clients. SMT threads are
included, so this is intentionally not labelled as a count of physical CPU cores.
—
accepted solution countThe exact solution count across production
packages accepted so far. Once every package is in, this is the campaign's full count. Final
verification also recomputes the stored digests and checks exact coverage of the task
domain.
—
unique solutionsSolutions counted up to the eightfold symmetry of the board — the four
rotations and their mirror images. Most solutions come in a family of eight, so this is close to
an eighth of the total; the ones that are symmetric enough to map onto themselves come in
families of four or two, and the generating solver counted those separately, which is what makes
the conversion exact rather than approximate. It appears once every task of the campaign has been
computed, because it is a function of the total and not of a subtotal.
—
right nowThe
reported column comes from each client's latest heartbeat. Work in flight joins the count only after
its package is accepted. A tail package repeats work whose first copy went quiet; an
audit package verifies work already counted.
contributor
machine
q
threads
reported
eta
by q classA
run is split into q classes — the number of queens on the black even rows — and they are
wildly unequal: the low classes hold the work, the high ones hold the tasks. Each class has its own
exact solution count; together those counts form the total.
symmetry is how many raw
skeleton tasks one scheduled task stands for once the eightfold board symmetry has been folded in.
weight from says whether that class's share of the bar is this campaign's own measured cost
per task, a local measurement made before it started, or an extrapolation.
q
progress
share of work
tasks
compute time
solutions
symmetry
weight from
participant ranking
Ranked by combined device running time, regardless of thread count. Two devices running
all day equal four running half the day. Pauses do not count. Pending accounts are provisional until activation.
rank
contributor
device hours
uptime share
solutions
solved tasks
thread hours
packages
status
Solutions are credited once to the accepted production result. Solved tasks include
successful duplicate and audit checks. Running-time reports include unfinished packages and update with checkpoints.
Show device ranking
Ranked by combined device running time, regardless of thread count. Two devices running
all day equal four running half the day. Pauses do not count. Pending accounts are provisional until activation.
rank
device
device hours
uptime share
solutions
solved tasks
thread hours
packages
status
Solutions are credited once to the accepted production result. Solved tasks include
successful duplicate and audit checks. Running-time reports include unfinished packages and update with checkpoints.
integrityTwo
machines computing one task and disagreeing is a hardware fault, not a disagreement about
mathematics, so the coordinator schedules a third computation by itself and keeps recomputing until
one value has been produced twice.
A task that was ever in dispute stays on the record for
good, settled or not: “no unresolved conflict” and “no task was ever argued
about” are different statements, and the second is the one a published total rests
on.