Help with Misfit
 

Hi, folks.

I've got my new X99 machine up and running and I'm looking forward to playing around with it. As part of this, I have made the resolution to actually start using Misfit but I was a bit overwhelmed by the options. I used the work calculator feature and that gave me settings for a lot of the things I don't understand. Anyway, I was able to get misfit to fetch work from GPU72 and then give it to the worktodo feeding my GPU which is currently chugging away fine, so I *imagine* that I have something that functions more or less.

The first thing I'm not seeing is any way to "link" worktodo/results files to a specific instance of mfaktx but now that I think of it, maybe that isn't even necessary to do? Is the allocation of a specific instance to a specific GPU still done with batch files or does MISFIT handle that?

I completely don't understand the CTRL-C section. Is this the only way to shut down a running instance? Can MISFIT run in tandem with a speed controller?

What is "Auto Update Stats" and what could possibly require contact with the server every 10 minutes (here I assume that the defaults are +/- sane)?

In the work fetch tab, I can set a pledge level AND set let GPU72 Decide? Which gets priority? If all I want to do is whatever makes sense (which might be 74 bits some times but 75 bits other times) how do I maintain that flexibility?

answers in RED

...

The first thing I'm not seeing is any way to "link" worktodo/results files to a specific instance of mfaktx but now that I think of it, maybe that isn't even necessary to do? Is the allocation of a specific instance to a specific GPU still done with batch files or does MISFIT handle that?


[COLOR="Red"]MISFIT interacts with the RESULTS.TXT and WORKTODO.TXT stored in each directory where you have MFAKTX running. Putting MISFIT in the same directory as a MFAKTX is not recommended since MISFIT can manipulate many MFAKTX installations. Double-Click a value in the ER,ED or Working columns and you will see file contents directly. (I guess that is your "link") [/COLOR]


I completely don't understand the CTRL-C section. Is this the only way to shut down a running instance? Can MISFIT run in tandem with a speed controller?

[COLOR="red"]CTRL-C is used to control the stopping of MFAKTx. If you kill a MFAKTx instance manually MISFIT will detect it as a stalled instance and alarm out. It is also a critical configuration if you use scheduling to stop/start MFAKTx instances. I use my speed controller outside of MISFIT all the time, but to be clear MISFIT does not interact with speed controller in any way. [/COLOR]

What is "Auto Update Stats" and what could possibly require contact with the server every 10 minutes (here I assume that the defaults are +/- sane)?

[COLOR="Red"]It does not contact a server. It is updating all those on-screen statistics and work values with what is happening on YOUR PC[/COLOR]

In the work fetch tab, I can set a pledge level AND set let GPU72 Decide? Which gets priority? If all I want to do is whatever makes sense (which might be 74 bits some times but 75 bits other times) how do I maintain that flexibility?
[COLOR="red"]Let GPU72 decide is just that. You pass in values you are interested in but the end result is whatever GPU72 if favoring. Chalsall could change the algorithm for determining work assignments at any time and MISFIT does not care. If you want further information you should post on the GPU72 boards as the discussion of work assignments is a constant over there.[/COLOR]


Well I hope that helps...

Fantastic, thanks!

If I want to stop one specific instance of mfaktx but it has the same process name as another instance I don't want to stop, am I SOL?

Or is there a way to customize the process name that CTRL-C uses?

[QUOTE=TheMawn;394739]If I want to stop one specific instance of mfaktx but it has the same process name as another instance I don't want to stop, am I SOL?

Or is there a way to customize the process name that CTRL-C uses?[/QUOTE]

You can customize the process names by renaming one of the mfaktc.exe to something else, but MISFIT will still detect if the process is not updating checkpoint files. Of course you can disable Stall Detection and do everything outside of misfit.

[QUOTE=swl551;394750]You can customize the process names by renaming one of the mfaktc.exe to something else, but MISFIT will still detect if the process is not updating checkpoint files. Of course you can disable Stall Detection and do everything outside of misfit.[/QUOTE]

Okay. I think I've got it. I want to use a speed controller so I didn't specify an executable in the configuration, but I still specified the directory and it looks like it's communicating with worktodo.txt just fine.

Thanks.

I use different folders for each mfaktc instance/card, and don't indicate the card in the ini file, but in command line. This way I can just create a folder, put mfaktc inside, set it accordingly, and duplicate that folder 100 times (I wish to have so many cards! :smile), then outside of these folders I have misfit and a startall.bat batch which says mainly variation of:
[CODE]@echo off
color 0A

set /p choice="Are you sure you want to start new mfaktc instances? [y/n]: "
if %choice%==Y goto doit
if %choice%==y goto doit
goto getout

:doit
start "mfaktc20_1" /D mf_201 /I /LOW mf_201\mfaktc_201.exe -d 0
start "mfaktc20_2" /D mf_202 /I /LOW mf_202\mfaktc_202.exe -d 1
start "mfaktc20_3" /D mf_203 /I /LOW mf_203\mfaktc_203.exe -d 2
rem start "mfaktc20_4" /D mf_204 /I /LOW mf_204\mfaktc_204.exe -d 1
rem start "mfaktc20_5" /D mf_205 /I /LOW mf_205\mfaktc_205.exe -d 0
rem start "mfaktc20_6" /D mf_206 /I /LOW mf_206\mfaktc_206.exe -d 3
rem start "mfaktc20_7" /D mf_207 /I /LOW mf_207\mfaktc_207.exe -d 2
rem start "mfaktc20_8" /D mf_208 /I /LOW mf_208\mfaktc_208.exe -d 1
[COLOR=DarkSlateGray][I]rem ..etc[/I][/COLOR]..

:getout
[/CODE]This I edit few times per year when I switch from this to that or play with cards, but the rest I use misfit to launch it. The additional question in the beginning helps in case I have all instances running and I mistakenly double click the bat with my drunk mouse - without the confirmation it will double all instances, resulting in slow computer and/or occasional driver crashes. Better safe than sorry. Of course, the batch can be more pro, to ask you about the cards and different work type, latency (for slow/fast mfactk, etc).

Also, renaming the windowzes like that allows me to address them individually when I want to stop them.

It works like a swiss clock.

Okay so for you Misfit is entirely a work fetching / reporting tool and you don't use it to manage your mfaktx instances?

Does anyone have a specific utility they use to merge a large number of text files? I was interested in looking through the misfit logs to see if I had found any factors yet (since I normally scanned through the 3-4 days worth of results in a single file before submitting), but all I found was a squintillion text files which I have no interest in sifting through one by one.

[QUOTE=TheMawn;396210]Does anyone have a specific utility they use to merge a large number of text files? I was interested in looking through the misfit logs to see if I had found any factors yet (since I normally scanned through the 3-4 days worth of results in a single file before submitting), but all I found was a squintillion text files which I have no interest in sifting through one by one.[/QUOTE]

[CODE]find "has a factor" *.*[/CODE]
?

[QUOTE=TheMawn;396210]Does anyone have a specific utility they use to merge a large number of text files? I was interested in looking through the misfit logs to see if I had found any factors yet (since I normally scanned through the 3-4 days worth of results in a single file before submitting), but all I found was a squintillion text files which I have no interest in sifting through one by one.[/QUOTE]

cat *.txt > merged.txt

Even works in DOS.