[QUOTE=Chuck;328210]I guess I would opt for the % fetching. The DCTF would need its own range selection in addition to the LLTF.[/QUOTE]

yes, differing bit levels would be a requirement.

I still recommend the GPU72WorkFetcher as an interim solution.

[QUOTE=Chuck;328210]I guess I would opt for the % fetching. The DCTF would need its own range selection in addition to the LLTF.[/QUOTE]

Actually, (and I hope I'm not "speaking out of school" here), I suggested to Scott that he offer those who do both LLTFing and DCTFing the option of balancing their reservations based on either % of candidates, or % of GHzDays.

[QUOTE=chalsall;328212]Actually, (and I hope I'm not "speaking out of school" here), I suggested to Scott that he offer those who do both LLTFing and DCTFing the option of balancing their reservations based on either % of candidates, or % of GHzDays.[/QUOTE]

No, you are not. "We (anyone who chimes in)" are exploring the options so any ideas are useful.

The percentage fetching with ranges and bit levels specified would be very cool, though I've only recently thrown some DCTF into my pot. :stirpot:

[QUOTE=swl551;328211]yes, differing bit levels would be a requirement.

I still recommend the GPU72WorkFetcher as an interim solution.[/QUOTE]

But that doesn't put in the work as next to be processed, right? It would add in at the end of the existing queue. I have the fetcher, as I was using it before MISFIT.

[QUOTE=Chuck;328236]But that doesn't put in the work as next to be processed, right? It would add in at the end of the existing queue. I have the fetcher, as I was using it before MISFIT.[/QUOTE]
Correct, it appends to bottom of queue. If you have good, ongoing, mixing ratio of LLTF/DCTF why does it matter exactly when it is processed. *help me understand so I can try to see the overall functionality*

[QUOTE=swl551;328240]Correct, it appends to bottom of queue. If you have good, ongoing, mixing ratio of LLTF/DCTF why does it matter exactly when it is processed. *help me understand so I can try to see the overall functionality*[/QUOTE]

I just WANT it to start NOW. That's all.

[QUOTE=Chuck;328245]I just WANT it to start NOW. That's all.[/QUOTE]

Hey Chuck,

I mean no offense, but this seems a bit much. Throughout the development of MISFIT, most, if not all the users have seemed to want assignments to remain in order of their age. Scott has worked to accommodate that. If I understand correctly, you want the program to change on demand to "insert on Line 2" of worktodo.txt. I have no idea how much work this might entail, not being a programmer. I'm sure you have reasons for wanting it.

However, I do think that Scott has gone out of his way to resolve other issues for you, and has done so on a very short turn around. Perhaps this level of tweaking is best done manually. :two cents:

Just for the record, my comment above about percentage fetching stated that it would be "very cool". That should not be taken as a demand. I'm happy with shoving things around by hand, especially since MISFIT is there to clean up my mistakes which could result in duplicating work. :smile:

2.4.3 (final release addressing screen scaling issues) [i hope]
 

Version 2.4.3
1. Added logging of the raw HTML from a GIMPS fetch.
2. Added detection and alerting if no assignments returned from GIMPS/GPU72 where no I/O error occurred. (fetch log file will show what actually happened)
3. Global Work Report is now always generated PRE-work fetch and PRE results upload. The reports are stored in the WEB_LOGS directory. Emailing of the reports is optional.
4. Removed prototype feature allowing random determination of GPU72 work types to fetch.
5. Significant retesting and additional minor tweaks related to proper form sizing when OS display is set to scale over 100%

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

[QUOTE=kladner;328252]

However, I do think that Scott has gone out of his way to resolve other issues for you, and has done so on a very short turn around. Perhaps this level of tweaking is best done manually. :two cents:

Just for the record, my comment above about percentage fetching stated that it would be "very cool". That should not be taken as a demand. I'm happy with shoving things around by hand, especially since MISFIT is there to clean up my mistakes which could result in duplicating work. :smile:[/QUOTE]

Of course; I wouldn't expect the program to incorporate every far-fetched idea. If I'm near the computer I can add work manually as desired. When I'm not, it works in the way MISFIT feeds it. The % is appealing though.

MISFIT generates a lot of logging. After it is set up and running smoothly, these are of not much interest to me. Does the program have any provisions for periodic removal of old log information?