Strategic Double Clicking

[Mark Rose]

You can add the lines to worktodo.add and force manual communication by running ./mprime -c in a new terminal so you don't have to stop mprime.

[LaurV]

Originally Posted by Madpoo

<snip>

You can put the N/A key when you create the list, so one just add them to the worktodo, without doing manual insertion (lot of "paste" (CTRL+V)) or reservation.

[Madpoo]

Originally Posted by LaurV

You can put the N/A key when you create the list, so one just add them to the worktodo, without doing manual insertion (lot of "paste" (CTRL+V)) or reservation.

I guess I'm not up to date on the syntax there. When I'm just testing stuff manually I don't need the assignment key part at all, it's optional. Others have said that doing that and letting it connect will create the assignment and update your worktodo... So it sounds like you just add the line, force a connection to the server, and that's it?

If there's a better way, let me know. Yeah, it'd be nice if we could do a manual reservation online, but yeah, the smaller exponents can't be done manually since they're in that critical range.

[ATH]

Originally Posted by Mark Rose

You can add the lines to worktodo.add and force manual communication by running ./mprime -c in a new terminal so you don't have to stop mprime.

Prime95 checks for "worktodo.add" files like every 15 or 30 min or something like that, so you do not have to do anything other than create that file. I would assume mprime does the same.

Originally Posted by frmky

I do this, but it is a pain for low exponents since the online form won't let me manually reserve them. Currently I stop a running mprime, add them to worktodo.txt, restart it and let it communicate, stop it, remove the updated lines from worktodo.txt, and then restart it. Would it be possible to repurpose the DC LL reservation code from GPU-72 for this project?

Why do you need to remove the key after communication?

[Mark Rose]

Originally Posted by ATH

Prime95 checks for "worktodo.add" files like every 15 or 30 min or something like that, so you do not have to do anything other than create that file. I would assume mprime does the same.

Forcing communication causes worktodo.add to be merged immediately, if you don't want to wait for whatever reason.

Why do you need to remove the key after communication?

Perhaps he's trying to reserve assignments for processing on a graphics card. Using mprime/Prime95 is the only way to reserve assignments in the critical ranges.

[frmky]

Originally Posted by Mark Rose

Perhaps he's trying to reserve assignments for processing on a graphics card. Using mprime/Prime95 is the only way to reserve assignments in the critical ranges.

Exactly. Most of my LL tests are done on 7 GPUs. So using worktodo.add and -c will save stopping it once, but I still need to remove the now-reserved lines from the worktodo.txt so the CPU doesn't do it. I don't need the reservation key for the GPU; I just want to formally reserve it so someone else doesn't grab it while it's running.

[Mark Rose]

Originally Posted by frmky

Exactly. Most of my LL tests are done on 7 GPUs. So using worktodo.add and -c will save stopping it once, but I still need to remove the now-reserved lines from the worktodo.txt so the CPU doesn't do it. I don't need the reservation key for the GPU; I just want to formally reserve it so someone else doesn't grab it while it's running.

You may consider using a second copy of mprime in another directory only for assignment reservation. I'd set these values in prime.txt

UsePrimenet=1
V5UserID=frmky
DaysOfWork=0
NoMoreWork=1

and in local.txt

WorkerThreads=1

and run only mprime -c, which will quit immediately after communicating/registering and not process any work, and give you all the assignments in a single [Worker #1] block.

[Madpoo]

Here's a list of work done by systems with a 4:1 bad:good ratio, so it may be easy pickings for some almost-first-time work:

exponent	Bad	Good	Unk	Sus	worktodo
38867557	5	0	6	3	DoubleCheck=38867557,71,1
40280173	30	5	4	3	DoubleCheck=40280173,72,1
40396613	7	0	8	3	DoubleCheck=40396613,72,1
40409249	4	1	9	0	DoubleCheck=40409249,72,1
41109209	6	1	1	3	DoubleCheck=41109209,72,1
42748019	17	4	5	3	DoubleCheck=42748019,72,1
45364853	43	9	13	17	DoubleCheck=45364853,72,1
45388481	43	9	13	17	DoubleCheck=45388481,72,1
47780699	4	1	10	8	DoubleCheck=47780699,72,1
47786399	4	1	10	8	DoubleCheck=47786399,72,1
47787829	4	1	10	8	DoubleCheck=47787829,72,1
49342991	43	9	13	17	DoubleCheck=49342991,72,1
49360579	43	9	13	17	DoubleCheck=49360579,72,1

[ixfd64]

Originally Posted by kladner

Finished overnight. Two factors.

M48611183 has a factor: 1735077409661214935753 [TF:70:71*:mfaktc 0.21 barrett76_mul32_gs]
M48340183 has a factor: 1314117775062544754639 [TF:70:71*:mfaktc 0.21 barrett76_mul32_gs]

Two factors out of 14 numbers, that's pretty good!

[kladner]

Originally Posted by ixfd64

Two factors out of 14 numbers, that's pretty good!

I was pleasantly surprised.

[frmky]

Originally Posted by Madpoo

Here's a list of work done by systems with a 4:1 bad:good ratio, so it may be easy pickings for some almost-first-time work:

I grabbed these.