Error in Worktodo file

[GARYP166]

A few months ago I posted when I had problems with saved files for 46,266,683 disappearing. Then I decided to have another try after seeing the thread

http://www.mersenneforum.org/showthread.php?t=12766

and seeing the note from Mini Geek

"trial factoring, it's one of the options for what to run in Test > Worker Windows"

Unfortunately although it was only two days ago I can't remember how I did it. However I do remember being asked to paste this text into my worktodo file:

[Worker #1]
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

Nothing happened until this morning when I got the following messages:

Too many sections in worktodo.txt, Line #7
Error: Worktodo.txt file contained bad LL exponent: 0
Illegal line in worktodo file: Test=exponent,68,1
Error: Worktodo.txt file contained bad LL exponent: 0
Illegal line in worktodo file: Test=DoubleCheck=exponent,66,1
Starting workers.
Too many sections in worktodo.txt, Line #7
Error: Worktodo.txt file contained bad LL exponent: 0
Illegal line in worktodo file: Test=exponent,68,1
Error: Worktodo.txt file contained bad LL exponent: 0
Illegal line in worktodo file: Test=DoubleCheck=exponent,66,1

Questions:

1) This was two days afterwards. One of my exponents had reached 75%; was this the trigger?

2) I guess some lines need to be removed from worktodo, which currently reads

[Worker #1]
DoubleCheck=44C4F6F2CB1AA38A4941A98466710304,23110891,67,1
[Worker #2]
Test=BDA22BB964CF82416AE126334DFA234B,45890281,68,1
[Worker #1]
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

how should I edit the worktodo file?

Grateful for advice.

G

[cheesehead]

Originally Posted by GARYP166

1) This was two days afterwards. One of my exponents had reached 75%; was this the trigger?

No.

2) I guess some lines need to be removed from worktodo, which currently reads

[Worker #1]
DoubleCheck=44C4F6F2CB1AA38A4941A98466710304,23110891,67,1
[Worker #2]
Test=BDA22BB964CF82416AE126334DFA234B,45890281,68,1
[Worker #1]
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

how should I edit the worktodo file?

Change it to:

[Worker #1]
DoubleCheck=44C4F6F2CB1AA38A4941A98466710304,23110891,67,1
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
Test=BDA22BB964CF82416AE126334DFA234B,45890281,68,1
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

There should be only one header for each worker, and all assignments for that worker should be listed under that header but before the next header.

[Prime95]

Originally Posted by cheesehead

DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

You need to change the text "exponent" with the Mersenne number you are testing.

[cheesehead]

I presume that's not literally in the file, but the poster simply wishes to conceal the exact exponent.

[Prime95]

I'm not certain. Two of the exponents weren't concealed. A newcomer may assume the program can infer the exponent from the assignment ID or by contacting the server.

[cheesehead]

Originally Posted by cheesehead

the poster simply wishes to conceal the exact exponent.

Isn't that a more reasonable theory than a newbie's thinking that "exponent" is a legitimate character string for that field? C'mon.

[TimSorbet]

Originally Posted by cheesehead

I presume that's not literally in the file, but the poster simply wishes to conceal the exact exponent.

I doubt it, because he said he put the exact lines that were in the example from the Manual Assignments page into his worktodo.txt file. When you get assignments there, after giving your lines, it says the following:

Distribute the lines above to your computer's worktodo.txt files. A typical version 25 prime95 worktodo.txt file on a dual core computer looks like this:

[Worker #1]
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

Older prime95's must run one prime95 instance for each core. The input file is called worktodo.ini. A typical worktodo.ini file looks like this:

Test=exponent,68,1
or
DoubleCheck=exponent,66,1

For Glucas and Mlucas follow the documentation that comes with those programs

[cheesehead]

Originally Posted by Mini-Geek

I doubt it, because he said he put the exact lines that were in the example from the Manual Assignments page into his worktodo.txt file. When you get assignments there, after giving your lines, it says the following:

Oh ... now that I see the exact comparison with the message text ... I guess you're right.

In that case, we should advise GARYP166 to also change the example assignment type, assignment key, bit level and P-1 indicator to his actual assignment type, assignment key, bit level and P-1 indicator.

Some folks are more literal than others. Perhaps the page message should use "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" instead of "A5996856A4F73D28634EFA6CB510066F" and the other key, and make it clearer that those lines are not to be copied literally.

[TimSorbet]

Originally Posted by cheesehead

Some folks are more literal than others. Perhaps the page message should use "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" instead of "A5996856A4F73D28634EFA6CB510066F" and the other key, and make it clearer that those lines are not to be copied literally.

I agree. A line or two in front of the real assignment line(s) saying that THIS is what you should use might also help.

[cheesehead]

Also, use

"[your assignment line from above]" instead of some fake assignment line.

But there's still the problem of copying the [Worker #1] and [Worker #2] lines from the example. Maybe there should be more than one example of arrangement of those, to emphasize that they're only examples.

[GARYP166]

Thanks to Cheesehead and Mini Geek for their replies.

I have no desire to conceal the exponents - indeed I mentioned the one I wanted in my post. For the record they are

46,266,683 - my first test, which crashed in February and which I decided to restart
23,110,891 - 35.43% done
45,890,281 - 76.63% done

I managed to work out what I did. I logged on and clicked on manual testing. For preferred work types I clicked on double check tests, not seeing LL tests in the drop down menu, and then entered 46,266,683 in both the Optional Exponent range boxes. Finally I clicked on Get Assignments. To test it I entered 49,979,687 and got the message

Distribute the lines above to your computer's worktodo.txt files. A typical version 25 prime95 worktodo.txt file on a dual core computer looks like this:

[Worker #1]
Test=A5996856A4F73D28634EFA6CB510066F,exponent,68,1
[Worker #2]
DoubleCheck=B94D34BF558295F697581568AD2E14AF,exponent,66,1

which is the same message as I got for 46,266,683.

I didn't realise that this was an example - my thought on seeing the strings was that they were hex representations of some number that Prime 95 would recognise. I changed the worktodo file so that it read as Cheesehead advised, including the word "exponent", and it's gone past today's communication with the server without generating an error message.

So my new questions are:

1) What should I have in my worktodo file so that 46,266,683 is the next to start?

2) What is the trigger that adds a new exponent to the queue? We've established that having one of my exponents reaching 75% was just a co-incidence, but how far does the test have to progress before another one is allocated?

G