Don't know if this has been brought up before, and I know everyone should be allowed to pick what they want, but seeing things like this makes me sad...http://www.gpugrid.net/workunit.php?wuid=3327127

Has GPUgrid ever thought of making long runs opt-in w/ a warning for cards on accounts page, or someway to prevent issues like the one from above from happening? (besides prevent x amount of WU from being d/l after failures.)

I think you meant this.
This is not the only user, who wants to filter out NATHAN_CB1s from the long queue.
That's why I suggested crediting directly proportional only with the running time of a wu (plus 24h and 48h bounses).
Also, there should be a blacklist of hosts (with low RAC, or inadequate hardware, or selective task abortions) for long workunits.
Long workunits should be like NATHAN_FAX4, IBUCH_adTRYP, PAOLA_PYU and PAOLA_HGA.
The NATHAN_CB1 is really out of this league, though its crediting is very high.

All I can really say is wow, amazing and yes I also agree CB1's don't belong in the long task feed. Again, wow

Here is another two examples of selective workunit abortions:
Host 113154
Host 113196

So there are people who seriously "camp" and wait for anything but CB1's to come through, simply because they offer the most credit for the least amount of work. These CB1 should really by sent to the short task queue. That's ridiculous.

Basically, if these tasks were shifted away from long task (higher credit), than this problem would disappear? If so, I'm rather surprised this hasn't happened yet. I know nothing about scoring coding etc., but wouldn't that just be sending them to the other feeder?

So there are people who seriously "camp" and wait for anything but CB1's to come through, simply because they offer the most credit for the least amount of work.

It's strange, isn't it? These people are commonly called as credit whores. (not my words, sorry for that)

These CB1 should really by sent to the short task queue.

Personally I don't care if a series of workunit is sent to the long queue while they are not qualified to be in this queue (i.e. the project personnel abusing the long queue presumably to achieve fast result returns), unless there is another automatism which prevents abusing the long queue on the cruncher's part.

That's ridiculous.

Kind of.

Basically, if these tasks were shifted away from long task (higher credit), than this problem would disappear?

I think it would. But I would prefer if the task scheduler would qualify the host computers for processing long tasks. (beside the setting in the user profile)

If so, I'm rather surprised this hasn't happened yet.

As I mentioned above, the long queue has shorter turnaround times, so if the project need something to be finished faster, they put it in the long queue. Or, it's simply a mistake.

I know nothing about scoring coding etc., but wouldn't that just be sending them to the other feeder?

Exactly.

Device 0: "NVS 300"

This one failed on a different device (NOT ONE OF MINE), attempting a FAX4. I mean I appreciate the fact that they're trying to contribute, but I actually had to look up to see what this even was. A total of 16 CUDA processors and 2 SM. I did find it interesting that it costs $130 though.