6425256 4112331 30 Jan 2013 | 2:46:46 UTC 30 Jan 2013 | 4:18:27 UTC Completed and validated 3,695.83 2,613.81 1,050.00 ACEMD beta version v6.48 (cuda42)
6424748 4114336 30 Jan 2013 | 1:54:08 UTC 30 Jan 2013 | 3:16:39 UTC Completed and validated 1,780.12 188.09 7,500.00 ACEMD beta version v6.48 (cuda42)
6423051 4116566 31 Jan 2013 | 14:38:52 UTC 31 Jan 2013 | 16:17:40 UTC Completed and validated 3,434.75 2,419.86 1,050.00 ACEMD beta version v6.48 (cuda42)
6422891 4116409 31 Jan 2013 | 13:49:52 UTC 31 Jan 2013 | 15:20:13 UTC Completed and validated 2,472.68 1,485.57 1,050.00 ACEMD beta version v6.48 (cuda42)

Credit is still wonky too. The highlighted one would be about right for Long tasks, but the others are still paying too low.

- So the Nathan tasks are paying, but Noelia's arn't, just yet...
I84R1-NATHAN_tstdhfr5-0-1-RND5000_1

These Noelia beta units are entirely too dependent on the CPU. I had to free up another CPU to get them to run faster. They also have a habit of starting out fast and then slow down toward the end. I observed GPU usage can be as high as 77% at the beginning of the task, and drop to 13% in the end.

beta units were working ok, albeit very low gpu usage, and then yesterday they started locking up my system. Had to do a hard reset. Now system locks up on boot when BOINC starts. Host id 125227, win7 x64 driver 310.70. Will try to update driver.

---

XtremeSystems.org - #1 Team in GPUGrid

Seeing LOTS of errors on the Beta tasks right now.
They say:
ERROR: file mdioload.cpp line 207: Error reading parmtop file

Did I do something wrong? (I recently added the WUProp project)

Note that different types of tasks have to be tested on the new Beta app.
Expect performance variations and problems - this is real β testing!

Thanks for reporting problems,

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Yesterday, I opted out of the beta testing because of the problems it was causing on my computers. Yet, I still kept getting beta WU's. I had to abort them, then set GPUGRID to "No new tasks". Forcing beta WU's on us is NOT COOL! You are jeopardizing the integrity of BOINC. Please let us know when it's SAFE to VOLUNTEER on this project again.
Regards (but disappointed),
Rick

---

To opt out of these Beta tests you need to go to GPUGRID preferences,
Unselect "Run test applications?"
unselect "ACEMD beta"
and unselect "If no work for selected applications is available, accept work from other applications?"

You may need to do this for more than one Profile:

Primary (default) preferences
Separate preferences for home
Separate preferences for work

Most if not all of the trypsin_lig_xxx_run1-NOELIA tasks failed on two of my systems. I also experienced a restart on one system (310.70 drivers).

All my Beta's fail except those ending in 1:

trypsin_lig_306_run4-NOELIA_RL2_equ-0-1-RND7002_1 4114936 1 Feb 2013 | 14:31:26 UTC 1 Feb 2013 | 15:06:00 UTC Completed and validated 1,929.98 1,431.43 1,050.00 ACEMD beta version v6.48 (cuda42)
trypsin_lig_543_run4-NOELIA_RL2_equ-0-1-RND9858_1 4116019 1 Feb 2013 | 1:46:55 UTC 1 Feb 2013 | 3:05:17 UTC Completed and validated 2,022.81 1,466.24 1,050.00 ACEMD beta version v6.48 (cuda42)
trypsin_lig_796_run3-NOELIA_RL2_equ-0-1-RND9844_1 4117167 1 Feb 2013 | 0:26:30 UTC 1 Feb 2013 | 1:46:55 UTC Completed and validated 3,715.23 3,286.65 1,050.00 ACEMD beta version v6.48 (cuda42)

It's ground hog day, again.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

When I attempted to opt out of the GPUGRID Beta, I did:
"go to GPUGRID preferences,
Unselect "Run test applications?"
unselect "ACEMD beta"
and unselect "If no work for selected applications is available, accept work from other applications?""

I also did it for all my profiles:
Primary (default) preferences
Separate preferences for home
Separate preferences for work
Separate preferences for school

After I did all the above, why did I continue to get beta WU's?

Rick

---

Hi Rick,
If you opt out of everything, the settings will automatically reset to include everything (all applications)! This prevents people being attached to the project and doing nothing (unless they manually suspend the project from Boinc).
So you need to select at least one type of task, other than Beta tasks.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

I have Short & Long projects selected for the default, and all 3 other profiles. Only the beta is unchected. This was the situation when I continued to get beta wu's and had to click "No new tasks" in the BOINC Client in order to keep my computers from freezing up and rebooting. I would love to resume GPUGRID work, but I'm concerned I'll still get more beta wu's, like I did yesterday. Is there a long lag between unchecking beta in the profile, and the scheduler getting the message? Rick

---

Unless there is some server side work being performed (which there might have been) it shouldn't be long at all. If you suspend the project, make the online changes and then click update that should be enough to get the new profiles settings into Boinc. Then when you resume the project you should be using your new profile. I couldn't replicate your problem, but I guess the scheduler might ask for new tasks before checking your profiles settings. Most people just forget to deselect the "Run test applications" options, but the scheduler's logic has taken some criticism of late.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Regarding Sponholz's inability to turn the betas off.. I haven't tried it myself so I can't verify that it works or does not work but I know this feature fails at 2 other projects and they claim it's a known bug in the server code. I have no idea if they are correct in saying it's a known bug, whether they have the feature misconfigured, whether they're using the same server code as GPUgrid or whatever.

The reason I have not tried turning beta off to test the feature is that I could never be certain that I am not not receiving betas simply because they have none to send, so it's pointless trying to test it.

skgiven wrote:

All my Beta's fail except those ending in 1:

I believe the 1 is referring to the iteration count rather than a particular type of task, if that's what you were thinking.

Many but not all of my beta NOELIA are failing too.I don't see any correlation between failure and iteration count. The failed ones all have "run2" in the name for example

trypsin_lig_965_run2-NOELIA_RL2_equ-0-1-RND9201

all "run1" NOELIAs seem to have crunched error free.

One "run2" completed successfully

All of my failed ones say:

Stderr output

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
process exited with code 98 (0x62, -158)
</message>
<stderr_txt>
ERROR: file mdioload.cpp line 207: Error reading parmtop file
21:06:01 (6125): called boinc_finish

</stderr_txt>
]]>

I don't seem to be getting any more "run2" NOELIA so I assume the failure has been noted and the tap turned off.

---

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

I know its just an iteration count, but thought there might have been something in it's name; for example, the app tried to write to a file thats name was generated presuming the iteration _1. Anyway, it was just coincidence that every other task was failing. When you think about it you are most likely to have successful tasks ending in _0, then _1 and then _2... If a task has already failed, and the more it's failed then the less likely it will succeed. So if you get a task ending in _5 or _6 the chances of a successful run are relatively poor.

Thanks for the 'undebugable' server code bug tip. Might explain some of the scheduler quirks, or not.

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Thanks for the 'undebugable' server code bug tip. Might explain some of the scheduler quirks, or not.

hehe, it's debugable, but only by someone who knows for certain whether there are betas in the queue or not.

---

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

Yesterday I got 3 Beta's and 2 errored out very quickly. By the third the system froze after a few seconds running the Beta and had to reboot to get any response. After the reboot I got the message that the graphic driver was restored after failing.
Windows Vista Ultimate x64, i7 12GB Ram, boinc 7.0.28, nVidia 285GTX driver 310.90

Long runs run fine on this machine, but take most of the time around 30 hours.

---

Greetings from TJ

Yesterday I got 3 Beta's and 2 errored out very quickly. By the third the system froze after a few seconds running the Beta and had to reboot to get any response. After the reboot I got the message that the graphic driver was restored after failing.
Windows Vista Ultimate x64, i7 12GB Ram, boinc 7.0.28, nVidia 285GTX driver 310.90

Long runs run fine on this machine, but take most of the time around 30 hours.

Same thing for me :/

Looks like the GPUGRID server is hung up, I've had this message in my Acctivity Log;

Sat 02 Feb 2013 08:27:17 AM MST | GPUGRID | Server can't open database

Beta 6.48: 4 of 4 successful.

GTX660Ti, i7 3770K, Win 7 64, Driver 310.90, BOINc 7.0.44.
GPU utilization is only ~40%, though. Fan speed, temperature and power consumption are really low. Credits per time aren't good either - seems like it's not working very well.

MrS

---

Scanning for our furry friends since Jan 2002

I was under the impression that fan speed shall be kept at max during crunching, and for me, everything I do.

Not if GPU temperature is only 44°C.. and I value my ears ;)

MrS

---

Scanning for our furry friends since Jan 2002