Looking good, thanks! :smile:

MISFIT for CUDALucas (proof of concept)
 

A very basic prototype is avail and is basically proof of concept. I was able to get MISFIT CuLu aware in just over an hour. A full conversion of MISFIT to fully support all the same features it does for mfaktX will take many hours. Feedback and interest in MISFIT for CuLu will determine its future.

READ CAREFULLY.

1. it assumes you are working [B]DoubleCheck[/B] work. [B]Test[/B] work won't get detected.

2. many of the MISFIT features are disabled as they need adaptation.

3. [B]you can fetch DoubleCheck work from gimps[/B] using the Add Work button. Sorry gimps allows a MAX of two rows to be fetched at a time.

4. [B]You can upload results as normal[/B]

5. can't balance

6. can't detect stalled process

7. can use remote control as normal

8. very little testing... [B]BE CAREFUL[/B].



This install should go into a different directory than your existing MISFIT installation.

[url]http://www.mersenneforum.org/misfit/[/url]

Have it working remote just like MISFIT.

Had to rename the executable so it would open on the same system as MISFIT for TF. Also need to change the name internally so it can be distinguished between the two versions in the notification bar.

It's working quit well so far. I had it send the current results file just for a test and it submitted correctly.

Formatting is a little off for some reason.

Retrieved one assignment from PrimeNet with no trouble.

For info in the boxes, 'Factor' should be LL Rows, LL Done, Prime [#], Not Prime [#]

I have an LL-DC that will complete in about 5 hours and I have it set to auto submit after that. I'll post on how it goes.

MISFIT-CuLu
 

Screenshot of MISFIT-CuLu managing four instances of CUDALucas. (two local, two remote)

Development of MISFIT-CuLu is against CUDALucas 2.04 beta.

Looking good!

Off the record: how can you process exponents so fast?! N = 50k seems a bit low :smile:

[QUOTE=Stef42;320258]Looking good!

Off the record: how can you process exponents so fast?! N = 50k seems a bit low :smile:[/QUOTE]

I've asked Dubslow and Flashjh to confirm my throughput as it seems much higher in the beta version.

Allowing the beta to auto-select the FFTLength caused what normally took 2 hours to go to 27 hours so I started setting the lengths manually. Using 50k reduced my GPU load to <50% allowing me to run a second instance on the same GPU while each instance was running the expected ~2 hours to do an LL test.

I have confirmed this behavior on two GTX 570s and one 560.

[QUOTE=swl551;320260]I've asked Dubslow and Flashjh to confirm my throughput as it seems much higher in the beta version.

Allowing the beta to auto-select the FFTLength caused what normally took 2 hours to go to 27 hours so I started setting the lengths manually. Using 50k reduced my GPU load to <50% allowing me to run a second instance on the same GPU while each instance was running the expected ~2 hours to do an LL test.

I have confirmed this behavior on two GTX 570s and one 560.[/QUOTE]
Yeah, something's definitely wrong. Those interim residues aren't changing (they should look like random hex, not ffffffffff00000000000). I've just sent a PM with more details.

Btw, a DC exponent should take about a day on a 570. It takes around 40 hours on a 460.

For that given range, your N= should be 1600K at least, not 50. The error rate should have stopped the program already, I wonder why it did not. I'm running the same range on my GTX570, it's taking about 26 hours.

If you have been reporting assignments which took the 2 hours you mentioned, they are all incorrect I suppose.

[QUOTE=Stef42;320262]For that given range, your N= should be 1600K at least, not 50. The error rate should have stopped the program already, I wonder why it did not. I'm running the same range on my GTX570, it's taking about 26 hours.

If you have been reporting assignments which took the 2 hours you mentioned, they are all incorrect I suppose.[/QUOTE]

I suspect they are. Who do I give the list to so they can be reversed out?

So what can you do with MISFIT CuLu
 

1. Fetch DC work from gimps
2. Assign/Manage/monitor work to instances on local machine or over network share (samba for Linux users)
3. Balance work assignments
4. Detect stalled instances of CuLu and email out
5. Email when work gets low
6. Perform remote control START/STOP of CuLu instances on remote machines
7. Have results automatically uploaded to GIMPS

Actually the only thing that MISFIT CuLu lacks in comparison to MISFIT is the calculation of GHZDays right in the app for remaining work and completed work.


Hopefully this helps motivate more people to move back to LL work since the TF work is so far ahead of the curve.

I am currently working an exponent that I broke into two because it's so large:

[CODE]Factor=2012-11-21,332240563,77,78
Factor=2012-11-21,332240563,78,79[/CODE]

It's telling me they're a duplicate even though they're not. Can you make it also check the from and to for duplicate checking?

[QUOTE=swl551;320270]SURE...give me about an hour[/QUOTE]

I need to find a way to get more time so I can program ;)