I would love to see an expanded version of this that goes down to 100 (or lower) memclock using latest version of cgminer, latest drivers, and SDK 2.1.

Anyone have any ideas how to automate a loop of cgminer.
I would imagine the easiest would be something like.

setup config file w/ shares: "5000", static memclock, static coreclock, worksize defined, vectors defined.

script
a) modifies config file to next parameter set to be tested (i.e. V2, W256, memclock = 180)
b) starts cgminer
c) cgminer stops after 5000 shares (and script detects it)
d) capture and save final avg hashrate, rejects, errors, etc.
e) goto a

I would be happy to run something like this on one of my rigs.   Once we get the complete result set for one core clock we could run it at another core speed.  Between 5870s & 5970s I figure coreclocks of 725 (5970 stock), 800, 825 (5870 stock), 850, 875, 900, 925, 950, 1000 (watercooled ) would be useful.

Doing it manually would be a nightmare but if someone can make some semi-automated tool I would be happy to leave it running on one of my rigs.  Once we get data for SDK 2.1 we could compare it to SDK 2.4, 2.5, 2.6.  It is possible that some parameters do better on different versions of SDK (as an example maybe SDK 2.1 is best w/ high work, low vectors, low memclock but SDK 2.5 is better at smaller  work, high vectors, "normalish" memclock, etc).

Con, maybe we can talk about integrating global offset parameter support into CGMINER?

Take a short look at http://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueNDRangeKernel.html and the global_work_offset parameter. All that has to be taken into consideration from the kernel-side is in DiaKGCN. OpenCL 1.1 detection is in your code, too, which is needed, but I can't do the other required changes without a compiler.

In short, the nonce-base is not supplied via the base parameter, if GOFFSET is enabled, but instead via the global_work_offset parameter and used via the global work-item ID in the kernel. This saves a few instructions and can give us a small boost.

Dia

Or

--sched-stop `date -d "+6 hours" +%H:%M`

... since shares are random

And 6 hours for a 1GH/s is approximately 5029 shares

Okay so I tested the fastest diablominer has to offer on 7970 and current cgminer is 1.5 MHash faster with defaults, so I'm pleased . I guess I should keep working on my kernel

Hmm don't expect that to last forever ...

Is it exiting or crashing?

What am I missing here, cuz my 5970 BAMT rig has been mining with cgminer for a week now - and it took 3 mins to set up 

BAMT already has cgminer installed and it is integrated into BAMT other tools (mgpumon, web monitor, gpumon, etc).

It is only cgminer 2.1.2 I believe but you can install newer copy if you like.  SDK is 2.4, I am not sure the driver.  It doesn't have 100% bug.

So it is write BAMT to flash drive.  Run fixer to grab latest updates, change 2 config files (1 for BAMT, 1 for cgminer) and you are mining.  You can then take that flash drive, record the image, put that image on 8 flash drives, put them in 8 rigs make a few changes via SSH and power up 20 GH/s farm in a few minutes.

I tried writing code to send nonce as the global offset parameter and your code returned duplicate work on 2 or more vectors. Looking at your code:
This won't be right as global id will now be the global thread id + the global offset parameter so doubling it will give random results.

Umm... I actually do understand the code  I was explaining what was wrong with it.