[QUOTE=swl551;326208][hint hint, several day reserve!][/QUOTE]

An excellent hint.

At least for the next week or so... (Hint, hint... :wink:)

[QUOTE=swl551;326208]EDIT:$100.00 says FLASHJH asks the work fetching trigger be changed to use calculated GhzDays from MISFITworkToDo.txt instead of number of lines in the file. (If he does ya'll pay up!)[/QUOTE]

Well, since YOU mentioned it ;)

[QUOTE=flashjh;326230]Well, since YOU mentioned it ;)[/QUOTE]
It does make a lot of sense so I'll have that update avail later tonight.

2.4.b9 (last release for the weekend)
 

VERSION 2.4.b9
Changed the determination of when to fetch work from the number of rows in MISFITworkToDo.txt to the calculation of GhDz remaining in said file. This provides a much better method for calibrating the balance between work consumption and work fetching.

This should help you in determining if you are fetching work in suitable quantities to have a several day reserve. (imagine how mad you will be if you fetch so frequently that you have a near real-time dependency on fetching, and somehow access to to your work source is cut-off for an extended period of time) [hint hint, [U]several day reserve![/U]]

Get from [url]http://mersenneforum.org/misfit/[/url]

When all these improvements start to settle down I think I will look into becoming a MISFIT...when I take an extended trip this spring I want my system to be in automated fetch/report mode.

[QUOTE=Chuck;326331]When all these improvements start to settle down I think I will look into becoming a MISFIT...when I take an extended trip this spring I want my system to be in automated fetch/report mode.[/QUOTE]


As a weekend warrior frequent releases are what we get until:
1. There is no more functionality to add
2. I get bored

However 2.4's next build (eta is 2/3) will have native GPU72 fetching completed. Now is the time to get on-board.

After that I might take a few weekends off.

[QUOTE=swl551;326349]As a weekend warrior frequent releases are what we get until:
1. There is no more functionality to add
2. I get bored[/QUOTE]

That's my spirit :razz:

[QUOTE=swl551;326349]As a weekend warrior frequent releases are what we get until:
1. There is no more functionality to add
2. I get bored

However 2.4's next build (eta is 2/3) will have native GPU72 fetching completed. Now is the time to get on-board.

After that I might take a few weekends off.[/QUOTE]

You may have left one off:

3. Jerry stops asking for changes

As 3 is easily trumped by 2, however, 3 really isn't all that important ;)

DEFECT in 2.4b8 & b9
 

PROBLEM: MISFITworkToDo.txt has more rows than expected and the extra rows are duplicates.

CONDITIONS: MISFIT drains work from MISFITworkToDo.txt and if there is [B]left-over[/B] work (not assigned out) the left-overs are appended to MISFITworkToDo.txt instead of replacing MISFITworkToDo.txt

ROOT CAUSE: MERGE_WORK method accidentally calling the file.AppendWithLock instead of the file.ReplaceWithLock method. Problem introduced after refactoring some methods and then calling the wrong method.

SOLUTION: SHORT TERM: STOP MISFIT....

STAND BY........ MORE INFORMATION.... 60 MINUTES.....

<ALL STOP>

A newbie question
 

I tired the MISFIT today for the first time.

After the initial configuration I pushed “Add Work”

It reserved 25 exponents.

I pushed “Assign Work”

I went to Prices Control – Start Batch, and mfaktc started cranking. But when it was done with the 25 exponents, nothing happened.

How do I configure MISFIT to get more work and submit results automatically without my intervention?

Thank you

URGENT FIX 2.4.b12 (required for 2.4b8 and 2.4b9)
 

[B]NOT REQUIRED IF YOU RUNNING VERSIONS PRIOR TO 2.4b8[/B]

VERSION 2.4.b12 (beta)
Fixed bug where MISFIT drains work from MISFITworkToDo.txt and if there is left-over work (not assigned out) the left-overs are appended to MISFITworkToDo.txt instead of replacing MISFITworkToDo.txt.

How to fix if you have duplicates: (visually inspect MISFITworkToDo.txt in an editor, external editor is best since it can go full screen)

You can manually edit MISFITworkToDo.txt and try to remove the duplicates, but some of them may already be assigned out to WorkToDo files.
or
1.) DOWNLOAD 1.4.B12 and start it up.
2.) From PROCESS CONTROL MENU select SUSPEND AUTOMATION (10 minutes)
3.) Click the ASSIGN WORK Button and assign out ALL work in one shot. (duplicates may be detected which is what we are looking for)
4.) From the OPERATIONS menu select FORCE WORK BALANCE (even if you have only one mfaktX instance). All duplicates will be tossed!
5.) Now you can either leave as is or you can reclaim work from the WorkToDo.txt (with an editor) and add it back into MISFITWorkToDo by using the ADD WORK button.
6.) UN-SUSPEND AUTOMATION... you back up and running.


Get from [url]http://mersenneforum.org/misfit/[/url]