[QUOTE=chalsall;329082]
Also, the change to the system WRT MISFIT users has been made. Anyone who's "Option" setting is "What Makes Sense" will be assigned work to 73 regardless of what the pledge level is.

Again, anyone who instead wants to only go to 72 or 71, simply change the Option to anything else. Human interaction with the form remains the same, including the use of WMS. As in, if a human pledges to, for example, 72 that's what will be assigned for all Options including WMS.[/QUOTE]

This is excellent; I think of it as the "what Chris wants/best for GIMPS" option.

I still can't fathom why there's a difference between the automated WMS option and the manual one. I thik it will only breed confusion for people new to the project who start with manual sttings and move to auomated one. Are there any upsides at all to them being different?

[QUOTE=Aramis Wyler;329087]I still can't fathom why there's a difference between the automated WMS option and the manual one. I thik it will only breed confusion for people new to the project who start with manual sttings and move to auomated one. Are there any upsides at all to them being different?[/QUOTE]

They're not really different.

When a human looks at the assignment form, the default pledge is (now) 73. If they simply enter the number of assignments they want and click "Get Assignments" they will be given "What Makes Sense" (currently the same as "Lowest Exponent"). It is only if they change any of the parameters do things change.

The reason I've made the change to the behavior only for MISFIT is MISFIT simply does a POST to the form requesting assignments -- it doesn't first do a GET for the form to see what the Pledge level should be. Thus until this change I couldn't actually give assignments which "Made Sense".

At the end of the day the results work out to be the same for humans and MISFIT robots.

An important thing to keep in mind is that WMS was built when there was no automation at all. Contrasted to a year ago, MISFIT has completely redefined mfaktX work. Because the one major intention of MISFIT is complete automation, the changes made G72 much more responsive to real-world demands. MISFIT users who use WMS can know that their automated system is doing what's best for GIMPS as a whole, while manual G72 users can still get exactly what they want.

Anyone wanting to move from manual to automated will understand the difference and reasons by just following the threads and development of G72/MISFIT.

Just a [URL="http://www.gpu72.com/reports/workers/p-1/week/"]thing[/URL] on P-1....

[SIZE=1][COLOR=Silver](on another thought... I actually won't be able to do much P-1... the systems that have enough memory? They had memory for another reason I just 'membered. Meh. :[SIZE=1]\[/SIZE] )[/COLOR][/SIZE]

[QUOTE=kracker;329120]Just a [URL="http://www.gpu72.com/reports/workers/p-1/week/"]thing[/URL] on P-1....

[SIZE=1][COLOR=Silver](on another thought... I actually won't be able to do much P-1... the systems that have enough memory? They had memory for another reason I just 'membered. Meh. :[SIZE=1]\[/SIZE] )[/COLOR][/SIZE][/QUOTE]

Is it the sort of situation where 'LowMemWhileRunning' would be of any use?

[QUOTE=kladner;329123]Is it the sort of situation where 'LowMemWhileRunning' would be of any use?[/QUOTE]

Mike had mentioned it, and I had looked it up in undoc but couldn't really understand, But what does it actually do? Does it reduce memory when a specified program is run etc?

[QUOTE=kracker;329124]Mike had mentioned it, and I had looked it up in undoc but couldn't really understand, But what does it actually do? Does it reduce memory when a specified program is run etc?[/QUOTE]

Personally I find MaxHighMemWorkers=2 much more useful.

[QUOTE=kracker;329124]Mike had mentioned it, and I had looked it up in undoc but couldn't really understand, But what does it actually do? Does it reduce memory when a specified program is run etc?[/QUOTE]

When the specified program(s) run, it switches any Stage 2 P-1 workers to the next available Stage 1 assignment. In line with Chris's comment, I have found that for my Photoshop work I get the best results with PauseWhileRunning on 3 workers, [U]and[/U] LowMemWhileRunning, [U]and[/U] MaxHighMemWorkers=4. LowMem alone was still too sluggish. This means that while Photoshop and its cousins are running I switch from 6 P-1 workers with 4 High Mem workers, to 3 Stage 1 workers.

In prime.txt:[INDENT]PauseWhileRunning=photoshop[3],bridge[3]
LowMemWhileRunning=photoshop,bridge
[/INDENT]In local.txt:[INDENT]MaxHighMemWorkers=4

[/INDENT]

MaxHighMemWorkers, 2, 3, or 4 what is the difference?

[QUOTE=kracker;329152]MaxHighMemWorkers, 2, 3, or 4 what is the difference?[/QUOTE]

The number of workers who can use the maximum allowed amount of RAM.