CUDALucas (a.k.a. MaclucasFFTW/CUDA 2.3/CUFFTW)

[James Heinrich]

Originally Posted by kladner

I may have missed something in the last few days, but what does "-polite 64" indicate?

You did miss it.

[kladner]

Originally Posted by James Heinrich

You did miss it.

Thanks James. That is an interesting capacity.

[MOBAJOBG]

msft, I certainly appreciate the masterpiece of a CUDA program source code that is CUDALucas.cu v1.66 speaking from a commercial software developer's point-of-view.

Of course, you did a little bit more than merely making a correction to the spelling of agressive->aggressive.

Thank you.

[Dubslow]

I found a bug (design error?) in my hack; it deletes the current assignment from worktodo.txt regardless of whether or not the test is finished or if it was just paused. I'm sure there's an easy fix, but it's 0519 local, and I found the bug while setting up my comp for sleep , so I'm definitely not going to investigate right now

[Dubslow]

Originally Posted by Dubslow

I found a bug (design error?) in my hack; it deletes the current assignment from worktodo.txt regardless of whether or not the test is finished or if it was just paused. I'm sure there's an easy fix, but it's 0519 local, and I found the bug while setting up my comp for sleep , so I'm definitely not going to investigate right now

Easy fix. New file attached; version string changed to "v2.00a".

I tried to add some of Prime95's torture test cases, but as it turns out, all those have a variety of different checkpoints, none of which are 10,000; and worse, only the 33rd-64th bits of the residue are actually checked, not all 64, so there's incomplete data for msft's check() function.

[Dubslow]

Bad News: I got a DC mismatch.
Good News: My script detected the mismatch.
Good News: I'm quite sure my run is correct, barring cosmic errors; it's my first mismatch (out of 3 recent tests and many more 1.2/1.3 DCs). Anyone want to run it through Prime95? (Edit: Expo is 26409557)
Bad News: The prog didn't automatically continue with next assignment.
Good News: "Stupid Programmer Error": Somehow I failed in understanding how a "Test=..." line is constructed, and counted the wrong number of commas (but it worked fine for the first few assignments). Either way, stupid error == easy fix; change line 1772 from

if ((2!=number_of_commas))	// must have 2 commas...

to

if ((2!=number_of_commas) && 3!=number_of_commas)	// must have 2 or 3 commas...

and all will be good

[LaurV]

Originally Posted by Dubslow

Anyone want to run it through Prime95? (Edit: Expo is 26409557)

I will queue it second on my list (after current DC expo finishes in 6-7 hours) on one core. ETA ~3 days. Should I automatically report it? Or check with you first? (in this case please remind me in few days, otherwise it may remain unreported).

[Dubslow]

Go ahead and report it. I'll claim the Anon, so when you report it the assignment isn't closed.

[James Heinrich]

Originally Posted by Dubslow

Somehow I failed in understanding how a "Test=..." line is constructed, and counted the wrong number of commas

// must have 2 or 3 commas...

It can potentially have 4 commas, at least in Prime95, which may record the FFT size in use if it's close to the transition point. This is the regex I use:

^(Test|DoubleCheck)=(|N/A,|[A-F0-9]{32},)(FFT2=[0-9]+[KM],)?([0-9]{4,10}),([0-9]{1,2}),([01])$

Which would match something like

Test=ABCDEF01234567890123456789ABCDEF,FFT2=2880K,45678901,72,1
Test=n/a,FFT2=2880K,45678901,72,1
Test=FFT2=2880K,45678901,72,1
Test=ABCDEF01234567890123456789ABCDEF,45678901,72,1
Test=45678901,72,1
Test=n/a,45678901,72,1

The first two elements (assignment ID and FFT size) are either-or optional (one or both could be missing).

[Dubslow]

Nuts. Thanks, though as I recall FFT2=... is only inserted by Prime95 whenever it starts an assignment, such that PrimeNet would never assign them that way?

[James Heinrich]

Originally Posted by Dubslow

Nuts. Thanks, though as I recall FFT2=... is only inserted by Prime95 whenever it starts an assignment, such that PrimeNet would never assign them that way?

Correct. That portion only appears when Prime95 is uncertain which FFT size to use and runs a few iterations before the test to determine the best FFT size. It then records the FFT size used in case the test is interrupted/resumed.