I've got one of these waiting to run, and I noticed it's up to replication _4 already:

http://www.gpugrid.net/workunit.php?wuid=4173049

3 of the previous runs ended with error -9

Anything special you'd like me to watch out for when it runs?

Put your safety glasses on and watch for smoke?
____________
BOINC <<--- credit whores, pedants, alien hunters

Does this mean that those of us who have only been able to run the cuda 3.1 code are no longer wanted?

Hm im suprised that cuda31 will finally disabled after switching it extra to short units queue. My 285gtx can normally do 6 wus per day :(
____________
DSKAG Austria Research Team: http://www.research.dskag.at

Possible but for the half performance of now, i dont invest >200w/h on 3 short wus per day ;) buuuut perhaps the new app runs better, so i will see and test some wus when 31 queue is empty. I will report then ;)

Ps: is it a typeerror to see now cuda32 on the site? Or is this cuda31 or something other?
____________
DSKAG Austria Research Team: http://www.research.dskag.at

Put your safety glasses on and watch for smoke?

Just watched a tasks complete and two subsequently fail after 2seconds.

trypsin_lig_375_run1-NOELIA_RL3_equ-0-1-RND1921_1 4141973 13 Feb 2013 | 9:40:31 UTC 13 Feb 2013 | 10:58:54 UTC Completed and validated 2,033.93 1,484.83 1,500.00 ACEMD beta version v6.48 (cuda42)

trypsin_lig_905_run3-NOELIA_RL3_equ-0-1-RND5342_2 4144209 14 Feb 2013 | 11:03:01 UTC 14 Feb 2013 | 11:03:51 UTC Error while computing 2.07 0.06 --- ACEMD beta version v6.48 (cuda42)

trypsin_lig_905_run2-NOELIA_RL3_equ-0-1-RND6964_2 4144208 14 Feb 2013 | 11:03:01 UTC 14 Feb 2013 | 11:03:51 UTC Error while computing 2.11 0.05 --- ACEMD beta version v6.48 (cuda42)

Stderr output

<core_client_version>7.0.44</core_client_version>
<![CDATA[
<message>
- exit code 98 (0x62)
</message>
<stderr_txt>
ERROR: file mdioload.cpp line 207: Error reading parmtop file
called boinc_finish

</stderr_txt>
]]>

Both tasks that failed had already done so 2 times and have not been resent:

6459826 30790 14 Feb 2013 | 8:51:55 UTC 14 Feb 2013 | 9:18:53 UTC Error while computing 3.05 0.14 --- ACEMD beta version v6.48 (cuda42)
6503647 126506 14 Feb 2013 | 10:24:54 UTC 14 Feb 2013 | 10:30:32 UTC Error while computing 2.06 0.08 --- ACEMD beta version v6.48 (cuda42)
6503815 139265 14 Feb 2013 | 11:03:01 UTC 14 Feb 2013 | 11:03:51 UTC Error while computing 2.11 0.05 --- ACEMD beta version v6.48 (cuda42)
6503960 --- --- --- Unsent --- --- ---

Tried a few as confirmation, with the same result - 12 errors in a row.

Beta tasks for host 132158

But it must be a data error - you can see the host has over 100 valid tasks, all done last weekend after the call went out to clear the queue so that proper application testing could resume.

At least these tasks weren't of the crashing/BSODing kind.

Thought I'd dip a toe back into the Beta testing pool, but I'm getting 'No beta tasks available'. Is it windows only?

Since today there is only 1 user left who connected the last 24hours to the short cuda31 queue (Serverstats). Im proud to tell, im this lonely guy ;) So i need at least 3 more (@24h crunching) days to clear this queue up (~4 hours per WU). Only as little estimate when the adminstaff can deactived it, and the problems with the queue selection on some computers should go away then ;)
____________
DSKAG Austria Research Team: http://www.research.dskag.at

hmm ok gpugrid dont sends me anymore tasks from cuda31 queue. strange. who should compute them now? O.o
____________
DSKAG Austria Research Team: http://www.research.dskag.at

Sry for spaming around, only want to help finishing the queue :(

I only want to tell i getting tasks again. Seems i hit any limit before..
____________
DSKAG Austria Research Team: http://www.research.dskag.at

Since today there is only 1 user left who connected the last 24hours to the short cuda31 queue (Serverstats). Im proud to tell, im this lonely guy ;) So i need at least 3 more (@24h crunching) days to clear this queue up (~4 hours per WU). Only as little estimate when the adminstaff can deactived it, and the problems with the queue selection on some computers should go away then ;)

It counts down on the " in work" unit when i finished something when i remeber right. Perhaps it shows 2 units free to send but all "in work" units are ready to resend and it fills the ready to send queue only until 2 or something. But im happy when someone help me, so we can finish it up faster :) gogogooo
____________
DSKAG Austria Research Team: http://www.research.dskag.at

I am a bit confused and I hope it gets resolved soon, I have my lowest power GPU set to only crunch Short Run tasks, but somehow it keeps on being given the Long Run Tasks, even though it has no chance of finishing them even within the 48 hour Bonus time. I hope the settings just didn't set in once I realized Short run 4.2 were available.
____________

I am also getting only long runs on my computers that are set to accept only short runs. I have them set to receive long runs only if there are no short runs available, but there seems to be plenty available.
____________
XtremeSystems.org - #1 Team in GPUGrid

I am a bit confused and I hope it gets resolved soon, I have my lowest power GPU set to only crunch Short Run tasks, but somehow it keeps on being given the Long Run Tasks, even though it has no chance of finishing them even within the 48 hour Bonus time. I hope the settings just didn't set in once I realized Short run 4.2 were available.

I am also getting only long runs on my computers that are set to accept only short runs. I have them set to receive long runs only if there are no short runs available, but there seems to be plenty available.

I tried to get short tasks at one stage (yesterday or the day before) when it said there were hundreds of tasks, but I was unable to for hours...

The first one is cuda31 support, "specially" for 2xx cards with drivers <3xx.xx. It will deactivaded soon. The second is cuda42 support for 4xx or better cards with driver >=3xx.xx

You can compute with eatch card in every queue, but i recommend so for the most performanceoutput.
____________
DSKAG Austria Research Team: http://www.research.dskag.at

The second is cuda42 support for 4xx or better cards with driver >=3xx.xx

The second is cuda42 support for 4xx or better cards with driver >=3xx.xx

Thanks for the feedback, dskag. That's what I thought. :-)

The problem for me is that I've got two hosts set to request tasks for that app only (in preferences, run test apps? No; only short runs CUDA42 checked; accept other work? No), yet I'm not getting any of those tasks. :-( One host has a 550Ti w/306.97 and the other is a 260 w/310.90.

That's a topic already being discussed in the No tasks available for ACEMD short runs cuda 3.2 thread.

That's a topic already being discussed in the No tasks available for ACEMD short runs cuda 3.2 thread.

Thanks for the feedback... Sorry to have missed that, but there's been so much talk lately about similar things in different threads that it's hard for me to keep track! I will set my prefs to accept both short queues and see what happens.

...I will set my prefs to accept both short queues and see what happens.

Dagorath,

I understand the settings, and I do have them set how I want them. I was just making a remark as around the time I got those tasks I checked the server status and it appeared that there were plenty of short run tasks ( but yes I realize it is not a perfect exactly up to date page, just a ball park). I do not mind crunching long runs on the card, so I do leave the box checked that says it can grab basically any GPU grid task it finds if my initial request does not come up with a result.
____________

Adam,

It's obvious I misunderstood your other message and I'm glad you've got it worked out now. Happy crunching!

____________
BOINC <<--- credit whores, pedants, alien hunters