[snip]

[QUOTE=Dubslow;318819](who I haven't seen for a year)
[/QUOTE]

Lemme do a posting, maybe magically the posse once again shows up.

Oh on automatic assigning exponents - i thought about it for Wagstaff as well. Yet with many computers searching not on the internet it doesn't make much of a sense. I hand out ranges by hand. What would be interesting though is a tool checking whether you forgot something and a tool to take a sample in ranges you didn't take a sample yet to double check. Tony Reix found for example a bug in the LLR-software when we got to higher ranges for Wagstaff. That thirst to double checking will grow when i manage to get the Tesla's search 'em.

[QUOTE=flashjh;318815]Does anyone know what would be involved in writing a small program (or modifying CUDALucas) to automatically assign exponents?

What I mean is instead of getting LL-DC work from GPU72 and then putting it into P95 to get it assigned to me and then moving them to CUDALucas worktodo, just have a small program in the same directory and anytime the worktodo file gets updated, you double click it and it updates your PrimeNet account with your exponent and an expected completion date, maybe 30 days or a settable date. I'm thinking even a Perl script might be enough; I just don't know how to do it.[/QUOTE]

Jerry,
Can you get LL-DC from the gimps manual assign page (seem so, but need confirmation) if so I can whip up a util to fetch it via HTTP GET. Just like I get TF factors from GIMPS in MISFIT.

[QUOTE=swl551;320100]Jerry,
Can you get LL-DC from the gimps manual assign page (seem so, but need confirmation) if so I can whip up a util to fetch it via HTTP GET. Just like I get TF factors from GIMPS in MISFIT.[/QUOTE]

Yes, I can, however, right now I'm getting all my LL-DC assignments from GPU72.

[QUOTE=flashjh;320101]Yes, I can, however, right now I'm getting all my LL-DC assignments from GPU72.[/QUOTE]

As you know I've already written code to get TF assignment from GPU72 via HTTP POST. Wouldn't that same approach be useful here. I don't get the Prime95 "connector" methodology. (really, what is that for?)

Can I help here?

Also has anyone looked at creating a WEB SERVICE for fetching/reporting work?

PrimeNet and Gimps? These products are ripe for such services.

[QUOTE=swl551;320102]As you know I've already written code to get TF assignment from GPU72 via HTTP POST. Wouldn't that same approach be useful here. I don't get the Prime95 "connector" methodology. (really, what is that for?)

Can I help here?[/QUOTE]
If you can use MISFIT for get LL-DC assignments from GPU72 and submit the results to PrimeNet, that would be very helpful. I'm currently only doing one DC per week on a GT 430, but I'm sure there are others that would like CuLu to be automated with both PrimeNet and GPU72. My main question is how to let PrimeNet know that the assignment belongs to 'me' once I get it from GPU72. I don't undersatand the API at all. Right now I decided to use a copy of P95 as I described above, but it's not optimal because it causes another 'computer' to show up in GPU72 and on PrimeNet even though it's actually not doing anything. A 'real' i7 would be able to do more LL-DC than one per week.

Looks like adapting MISFIT to CuLu will be simple since they use the same worktodo/results files as mfaktO/C

Minor changes
1. the prefix of the factor row is different
2. the type of work to fetch from gimps is different


Everything else, including my SendCtrlSignal.exe and MISFITServer.exe will work without modification.

The first thing I'll do is outfit MISFIT with the file locking system implemented in mfaktO and CuLu and finally get that addressed.

How to calculate GHZdaysCredit for DC and LL
 

As I look at adding support for CuLu to MISFIT I need the formula for calculating GHZdaysCredit for DC and LL that CuLu processes.

Please don't point me to the MONSTER source code at Mersenne.ca to try to find it.


For TF Chalsall gave me the following in perl. Below is my version converted to C#. I'm looking for the same type of documentation for DC/LL.
[B]public static double CalcGHDZ(int exp, int from, int to)
{
double GHZdays=0;

for(int i=from+1;i <= to;i++)
{

GHZdays += (0.00707 * 2.4) * (Math.Pow(2, i - 48)) * 1680 / exp;
}

return GHZdays;
}

}[/B]

Thanks!

Chalsall got his info from Mersenne.ca, or more specifically its owner; I have absolutely no idea how PrimeNet calculates the credit for CUDALucas tests.

[QUOTE=swl551;320167]For TF Chalsall gave me the following in perl. [...] I'm looking for the same type of documentation for DC/LL. [/QUOTE]

Why use a loop for TF credit?

Anyway, LL/DC credit is based on the FFT size actually used for a given assignment. Come back when you have that info.

[QUOTE=ckdo;320193]Why use a loop for TF credit?[/quote]It loops over each bit level.
[QUOTE=ckdo;320193]
Anyway, LL/DC credit is based on the FFT size actually used for a given assignment. Come back when you have that info.[/QUOTE]
That it does, however for Prime95 results, there's more to it than that, and even with the FFT, it does vary by exponent. You could probably experimentally make a decent guess at the formula, but that would take a variety of results to make an actually decent guess.

(PS @swl551 the FFT length is the "n = ..." part of the result line.)