(archive)MISFIT

[kracker]

The forum's god and creator approaches! Stand at attention or be.....zzzzzasdokfapppp... ouch..

ME >

[TObject]

Originally Posted by swl551

MISFIT does not support results.txt file with lines containing prefixs like "UID: xyz/abc"
I personally didn't find an meaning/use in having those values configured in my mfaktc.ini so I stopped using them and MISFIT was never designed to support them. Until someone can establish their benefit in the GIMPS system MISFIT won't have support for it.

Let me just say that Mr. Flashjh one of the TOP producers doesn't use "UID: xyz/abc" and he is very serious about his data.

Ok, thanks. I will try without user ids.

[Chuck]

I am thinking about downloading and installing this program.

It is designed to support multiple instances of mfaktx. In my case, with only one instance, does everything operate in the same way EXCEPT that there is only one instance to which work is distributed?

[flashjh]

Yes, it will work fine with one instance.

[chalsall]

Originally Posted by swl551

MISFIT does not support results.txt file with lines containing prefixs like "UID: xyz/abc"
I personally didn't find an meaning/use in having those values configured in my mfaktc.ini so I stopped using them and MISFIT was never designed to support them. Until someone can establish their benefit in the GIMPS system MISFIT won't have support for it.

If I may... And this is meant constructively...

Since mfaktc can produce such results lines, you need to parce them correctly. And Primenet may someday find this additional information useful, even if it doesn't currently.

I made the same mistake with my submission spider, as pointed out by Mini-Geek here.

It turned out (as shown by Mini-Geek) that simply removing the constraint that the search string was at the start of the target string was all that was needed to fix the problem.

[swl551]

Originally Posted by chalsall

If I may... And this is meant constructively...

Since mfactc can produce such results lines, you need to parce them correctly. And Primenet may someday find this additional information useful, even if it doesn't currently.

I made the same mistake with my submission spider, as pointed out by Mini-Geek here.

It turned out (as shown by Mini-Geek) that simple removing the constraint that the search string was at the start of the target string was all that was needed to fix the problem.

I may look at this after the release supporting the world famous GPU72.com is delivered. GPU72 first.

[chalsall]

Originally Posted by swl551

After the long awaited release supporting the world famous gpu72.com site I may resolve this. Gpu72 first!

Nameste.

[swl551]

Originally Posted by TObject

Ok, thanks. I will try without user ids.

So how'd it go? The entire MISFIT support team is on stand-by until we can close out this ticket.

[TObject]

Thank you to everybody, and especially swl551, for helping with MISFIT configuration – my installation now appears to be fully operational. It just submitted results to PrimeNet without my intervention.

I appreciate your help.

[swl551]

Originally Posted by TObject

Thank you to everybody, and especially swl551, for helping with MISFIT configuration – my installation now appears to be fully operational. It just submitted results to PrimeNet without my intervention.

I appreciate your help.

So here is what I learned.
1. the product should support OR warn about the UID limitation
2. There should be a simple auto-config wizard that asks a few questions and then sets up basic values.

{after I finish GPU72 integration}

Please check out gpu72.com as you might find it VERY useful.

[Dubslow]

Originally Posted by swl551

1. the product should support OR warn about the UID limitation
2. There should be a simple auto-config wizard that asks a few questions and then sets up basic values.