(archive)MISFIT

[swl551]

MISFIT formally known as mfaktXapp....

(MfaktX Internet Service Function Integration Tool)


First big item is MISFIT which now has its own download site on the forum at http://www.mersenneforum.org/misfit/

Second is the full rename from mfaktXapp to MISFIT. Version 2.xa is the first version to use the MISFIT name. Copy all files from the zip into your mfaktXapp directory and run MISFIT.exe. On startup MISFIT.exe will rename all the files and directories to MISFIT*. Other small changes are in 2.xa.


Third is MISFIT-REMOTE: This is the prototype of the REMOTE control system I'm building for GPU farms. It has its own zip file. Please read the README as it explains the basic setup and how to use the test harness. It has no value unless you want to perform remote control of mfaktO/C on remote WINDOWS PCs. The inter-process communication is done over windows named pipes using .NET 3.5


Get em both from http://www.mersenneforum.org/misfit/

Let me know how it goes!

Scott

[kracker]

Looks nice. Will test it out later when I have time.

[kladner]

Sounds good! Thanks! I'll try to get into it tomorrow.

[swl551]

Screenshot demonstrates the basic approach MISFIT will use to manage mfaktO/C on remote PCs.

INQUIRE=Gets count of running instances of mfaktO/C from remote
START=Remote executes its start executable (typically a batch file)
STOP=Remote will send CTRL-C signal to all running instances of mfaktO/C
KILL=Remote will execute a process.KILL to all running instances of mfaktO/C

KILL is useful if you have HUNG instances that are not responding to STOP commands.

Scott

[sonjohan]

Updated to Misfit.
Was still running an old version, as I only use it to easily stage work & post results.
Actually waiting for gpu72 support, which I already know to be on the todo list... :)

The change to Misfit does however have several aesthetic advantages...

[swl551]

11/13/2012
VERSION 2.0 - NEW CHANGE LOG

1.Product rename from mfaktXapp to MISFIT (MfaktX Internet Service Function & Integration Tool)
On startup of MISFIT.exe it will rename the legacy mfaktXApp files and directories to MISFIT files and directories

2.New Error form for display of errors detected during UpdateGridStats. This form will allow UpdateGridStats to execute at each designated interval and log all errors detected in each cycle. Prior to this method of showing errors a modal dialog would block future cycles of of the core timer and prevent things such as Stalled Process Detection or Auto Results Uploading.

3. A mode of operation called "Monitor Mode" which blocks MISFIT from making any file changes, export, uploads etc. It does allow UpdateGridStats and Stalled Process Detection make Monitor Mode ideal to run on a second PC in a GPU farm where its primary role is to monitor the primary PC that is running MISFIT in "Full Mode". Sort of like a monitor for the monitor.

4. A "Force Stalled Process Test" which allows direct testing of stalled processes without waiting for the scheduler to execute the test. Very useful if you have corrected a stalled condition and want to verify MISFIT pulls out of the stall.

5. New locaton for MISFIT library at http://www.mersenneforum.org/misfit/

6. Prevention of running two instance of MISFIT on same PC. With the recent minimize to system tray accidental startup of multiple instances was common.


7.REMOTE CONTROL: Here's the big one for GPU farmers!
I have developer MISFITserver.exe which runs on a remote PC and receives commands from MISFIT to control your instances of mfakto or mfaktc. The server responds to four commands: INQUIRE,START,STOP,KILL. Think GPU farms and you will understand the goal of MISFIT remote control.
See the MISFITSERVER.TXT for more information.


Screenshot of MISFITserver included. Other screenshot and download at http://www.mersenneforum.org/misfit/

[kracker]

Thanks! working good

I guess it's all caps

[swl551]

Originally Posted by sonjohan

Updated to Misfit.
Was still running an old version, as I only use it to easily stage work & post results.
Actually waiting for gpu72 support, which I already know to be on the todo list... :)

The change to Misfit does however have several aesthetic advantages...

Sorry, there won't be any native support in MISFIT for fetching work from GPU72. A method of interfacing the two products could not be agreed upon so I withdrew my effort.

[chalsall]

Originally Posted by swl551

Sorry, there won't be any native support in MISFIT for fetching work from GPU72. A method of interfacing the two products could not be agreed upon so I withdrew my effort.

That's not entirely true.

I took (perhaps an unreasonable) exception to you submitting an affiliate link to GoDaddy for SSL certs on the GPU72 Status thread. I don't like people trying to make money on others' work.

I'm more than happy to work with you to provide automated GPU72 assignments for the community's benefit.

[swl551]

Originally Posted by chalsall

That's not entirely true.

I took (perhaps an unreasonable) exception to you submitting an affiliate link to GoDaddy for SSL certs on the GPU72 Status thread. I don't like people trying to make money on others' work.

I'm more than happy to work with you to provide automated GPU72 assignments for the community's benefit.

Chalsall,
I'll need some feedback from the community at large if adding support to MISFIT is commonly desired. As you can see most of my recent feature releases have not had many responses. I think I've maxxed out the usefull features MISFIT can provide.

So, maybe you can get some feelers out and if the response is positive we'll review the MISFIT <-> GPU72 interface options again.

Scott

[kracker]

I don't have a wide-scale gpu farm, so the last features wasn't needed for me, however gpu72 would still be nice, if it is possible.