Grand Cleanup Walk

Announced is a seven day challenge at GCW from 1st until 8th of August. I suggest we start at 12:00 UTC and end at 12:00 UTC.

Generalized Cullen/Woodall Prime Search was originally only for base 13. Now it has extended to several bases.
Its currently searching for Generalized Cullen primes n*b^n + 1 for bases 41, 47, 49 and 53.
More can be found here and here. News and infos about the PRPNet client can be found here.

To take part, you have to activate the following lines in prpclient.ini:

server=GCW:0:1:prpnet.primegrid.com:12004

This is the line in all of my computers master client.

server=GCW:100:1:prpnet.primegrid.com:12004

This is the same line in the notices in boinc and the thread itself.

Which of these are correct for the Aug 1 challenge?

taken from the instructions:

The configuration of the server section is parsed as follows:

server=<suffix>:<pct>:<workunits>:<server IP>:<port>

<suffix> - a unique suffix for the server. This is used to distinguish file names that are created for each configured server.
<pct> - the percentage of PRP tests to do from the server.
<workunits> - the number of PRP tests to get from the server. The server also has a limit, so the server will never return more than its limit.
<server IP> - the IP address or name for the server
<port> - the port of the PRPNet server

Setting pct to 0 means that the client will only get work from the server if it cannot connect to one of the other configured servers.

Is pfgw64 the most efficient and correct app to be running on these tasks on a i7? That's what started on my test runs, rather than LLR.
Thanks,
--Gary
EDIT:: linux, 64-bit.

Is pfgw64 the most efficient and correct app to be running on these tasks on a i7? That's what started on my test runs, rather than LLR.
Thanks,
--Gary
EDIT:: linux, 64-bit.

... and the challenge is running, stats are available here but we still are waiting for the first early bird.

good look to all prime hunters

EDIT: and with the 12:30 UTC update the first two are in :)
____________
Sysadm@Nbg
my current lucky number: 113856050^65536 + 1
PSA-PRPNet-Stats-URL: http://u-g-f.de/PRPNet/

You could run timing tests, but I would expect LLR64 to be faster.

On Windows, with both the lines

llrexe=llr64.exe

and

pfgwexe=pfgw64.exe

present (not commented out) in the .ini file, the program seems to choose pfgw64 as well.

Is it recommended to try to remove pfgw64 from the .ini to check if it runs (and runs faster) with llr64?

/JeppeSN

Have been banging my head on the wall all day trying to install prp.net apps on a computer running win xp pro 64-bit on 2x quad-core socket 771 xeons. Everytime I get to the last step and run start prpclient.bat I get an error message, the pertinent part of which is:

prpclient-5.3.1.-windows\prpclient-1\prpclient.exe is not a valid Win32 application.

I have reinstalled four times with the same result. Another computer running win7 pro 64-bit on 24 cores is running fine so it's not failure to implement the instructions. I do have an old installation for gfnsvCUDA which worked just fine a couple of years ago, but that was before the migration.

Any help would be appreciated.

Have been banging my head on the wall all day trying to install prp.net apps on a computer running win xp pro 64-bit on 2x quad-core socket 771 xeons. Everytime I get to the last step and run start prpclient.bat I get an error message, the pertinent part of which is:

prpclient-5.3.1.-windows\prpclient-1\prpclient.exe is not a valid Win32 application.

I have reinstalled four times with the same result. Another computer running win7 pro 64-bit on 24 cores is running fine so it's not failure to implement the instructions. I do have an old installation for gfnsvCUDA which worked just fine a couple of years ago, but that was before the migration.

Any help would be appreciated.

prpclient-5.3.1.-windows\prpclient-1\prpclient.exe is not a valid Win32 application.

I'm not certain if that's the problem here. We'll need some input from Iain for that.

FFT length has bumped up a notch for me over the past few hours of the GCW challenge. I know there are many variables there, and I'm not claiming a problem. Just pointing it out to others who might notice the same. "Your mileage may vary".

--Gary

FFT length has bumped up a notch for me over the past few hours of the GCW challenge. I know there are many variables there, and I'm not claiming a problem. Just pointing it out to others who might notice the same. "Your mileage may vary".

--Gary

I'm wondering how the scores in the stats will be calculated... Are they Cobblestones?!

Nice challenge! Happy crunching!

Thanx for the fast reply! Is it possible to forecast the BOINC credits with the PRPNet scores? It's nice to have a prediction of the credits you've earn during the challenge. Noncommittal - of course...

Did someone out there mess up their team name? I ask only because I see a team named "Team" in the standings... probably put a "space" character in their prpclient.ini file. It's certainly OK to not claim a team membership, but wanted to point it out in case someone fat-fingered it. If already fixed, never mind.

Only about a day, plus, to go at this point in the challenge... will someone *please* find a prime? :-)

--Gary
____________
"I am he as you are he as you are me and we are all together"

87*2^3496188+1 is prime! (1052460 digits)
4 is not prime! (1 digit)

Did someone out there mess up their team name?

looking at the current stats only 2 participiants can have caused this together
"sm5ymt" and "cnamglaejoer".
both of them having 12 tasks and 24 tasks on team "Team".
There is no other combination of participiants to get 24 tasks.

I did 19 WUs with pfgw, average 16h10min
Then I did 26 WUs with LLR, average 12h51min
Duration is increasing as challenge progresses.
With my AMD X6 1100 LLR is defintely quicker for GCW13.

I had one WU that chose a smaller FFT size and it completed in 9 hours.

I let pfgw64 run for a couple of days on this challenge, with llr running on the other cores of a 3770K, HT off. I think the timings worked out at about 5 hours for llr vs. 7 for pfgw64. Those numbers are pretty rough, from memory, so don't bet the farm on them. The test sizes are different so that's another variable.

As for the "Can you force LLR to use a certain FFT length?" question, I believe the answer is "no".

Into the final challenge day now. Good luck to all.

--Gary

off topic!

oh i didn't expect the spanish inquisition with its two weapons: fear, surprise and comfortable chairs ...

Therefore I'm pleading not guilty.

But no prime were found... :-(