(archive)MISFIT

[LaurV]

Decided to give a try to misfit. Made a VBox installation of XP, until I can see the sources (well, you know, I am a bit paranoid) and eventually compile them by myself.

It seems to work as promised, except it is always telling me that I have no "no factor" lines in the results file, and I will "have problems" reporting only "factor found" lines (that's the trick with PrimeNet sometimes confusing the algorithms used to find the factors, if no "no factor" line is present in the result file).

That is a very nice feature to notify me,.... except that the reality was that I only had "no factor" lines, and no "factor found" lines (that is, vice-versa!).

[edit: this also happens when I try to export the results in a new file, and generally, misfit does not recognize the format of my lines in the result files]

However, I use an output format with "username/computername" as P95 outputs (this is an option of mfaktc, how to output the results) because that helps me with batch reporting, and there is no way around it, i.e. I will not change that, as I continue to report/fetch by hand/batch files, not yet trusting misfit so much to input passwords into it, again paranoid, sorry.

Is this output format the reason why Misfit does not recognize the "no factor" lines? Can the behavior be changed from the settings? Or the internal parser need to be reviewed?

Any other suggestion?

[swl551]

Originally Posted by LaurV

Decided to give a try to misfit. Made a VBox installation of XP, until I can see the sources (well, you know, I am a bit paranoid) and eventually compile them by myself.

It seems to work as promised, except it is always telling me that I have no "no factor" lines in the results file, and I will "have problems" reporting only "factor found" lines (that's the trick with PrimeNet sometimes confusing the algorithms used to find the factors, if no "no factor" line is present in the result file).

That is a very nice feature to notify me,.... except that the reality was that I only had "no factor" lines, and no "factor found" lines (that is, vice-versa!).

[edit: this also happens when I try to export the results in a new file, and generally, misfit does not recognize the format of my lines in the result files]

However, I use an output format with "username/computername" as P95 outputs (this is an option of mfaktc, how to output the results) because that helps me with batch reporting, and there is no way around it, i.e. I will not change that, as I continue to report/fetch by hand/batch files, not yet trusting misfit so much to input passwords into it, again paranoid, sorry.

Is this output format the reason why Misfit does not recognize the "no factor" lines? Can the behavior be changed from the settings? Or the internal parser need to be reviewed?

Any other suggestion?

Since your results lines start with "username/computername" MISFIT does not find the expected .StartsWith phrases and considers the lines invalid.

No work around sans code change.

[swl551]

Flashjh see screenshot.

This is TOO simple. We should have done this long ago.


I'll have this in a build later today. GREAT IDEA.

[swl551]

Originally Posted by swl551

Flashjh see screenshot.

This is TOO simple. We should have done this long ago.


I'll have this in a build later today. GREAT IDEA.

And here is the output send via email.

MISFIT Global Work Status Report
****** REMAINING WORK INFORMATION ******
GhzDzToDo:4,262.346
ExpRows:50
Staged Work:6
****** COMPLETED WORK INFORMATION ******
GhzDzDone:89.854
ExpsDone:8
FactorsFound:0
Results Bytes:608
 
Sent by MISFIT 2.4.b4 from computer THOR at 1/26/2013 11:19:55 AM

[flashjh]

Perfect

[Xyzzy]

That is very cool.

[swl551]

VERSION 2.4.b5
Added LLDC stats to the Leaderboard

Added option to email Global Work Stats prior to Auto Results Uploading

Get from http://mersenneforum.org/misfit/

*** in this version clicking the Export Results button will also send the email, but that will be removed in final version ***
This will allow you to generate the email without waiting for automated upload, but since you actually looking at the screen it doesn't need to be emailed to you. (that why it will be removed)

[kracker]

Is it possible to reduce upload time minimum from 4 hours to let's say, 2?

Other than that... latest working great

[flashjh]

My daily upload just occurred and the email was perfect, thanks!

[swl551]

Originally Posted by kracker

Is it possible to reduce upload time minimum from 4 hours to let's say, 2?

Other than that... latest working great

Yes, configure scheduled uploads to manually achieve an aggressive upload frequency.

[swl551]

Added calculation of GhzDays from the MISFITworkToDo.txt file. This information also now in the Emailed Global Stats report. 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, several day reserve!]


Added file-locking to all I/O scenarios where MISFITworkToDo.txt is involved. A few conditions didn't have locking and that was OK when it was only possible to load the MISFITworkToDo.txt via the UI. Now with randomly timed fetching threads adding work to the file it was at risk of an un-handled IO collision. A few new file handling methods were written to resolve this so it is definitely BETA code.

Enjoy.

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!)