I received a few of these units. So far, everything is finishing, completed and validated. The progress column updates regularly, until it reaches about 50%, than, in flash, the unit finishes, uploads and reports.

http://www.gpugrid.net/results.php?hostid=127986&offset=0&show_names=0&state=0&appid=25

7928940 127986 14 Mar 2014 | 21:33:54 UTC 14 Mar 2014 | 22:09:38 UTC Completed and validated 598.33 572.70 3.09 CPU only app v1.05

Getting nothing but errors upon starting of v1.05 tasks on BOTH Windows & Android.
Tasks are erroring out for ALL who have attempted to run them.

One example of error message that is common to BOTH types:

Stderr output
<core_client_version>7.0.64</core_client_version>
<![CDATA[
<message>
Incorrect function.
(0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# (BOINC) Mapping [ligand.tar]->[ligand.tar]
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/DECOY405-MJHARVEY_DUDMYREC2-0-1-RND5157_6_0]
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt]
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt]
nextfile: reading [in]
[.]
[..]
[decoy-405.pdbqt]
NEXTFILE : [out] [decoy-405.pdbqt]
copy [in/decoy-405.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat]
# (BOINC) Mapping [progress.log]->[progress.log]
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt]


Parse error on line 1 in file "protein.pdbqt": ATOM syntax incorrect: "9.00 -17.40" is not a valid AutoDock type. Note that AutoDock atom types are case-sensitive.
08:00:21 (2160): called boinc_finish

</stderr_txt>
]]>

---

Getting nothing but errors upon starting of v1.05 tasks...

Me, too. As are all of my wingmen, as best I can tell... :-(

---

Here the same, 5 seconds executing an then... "Misscalculation"

---

+1

Alexander

Yeah, well I buggered up that set of WUs. I guess that poisoned the reliability stats of all participating clients. I think we just have to wait for the server to let you all out of Nid.

IIRC the lockout period is 24h, so most systems should be getting out of jail today.
I believe there is a way to reset this manually, but it's probably not handy and 24h isn't too long.

---

FAQ's

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

But, is it safe to go back in the water? Sorry if I missed something...

---

But, is it safe to go back in the water?

Safer, at least, it would seem. I'm 5-10 minutes into new WU's and no problems, so far.

---

Must be a not-so-bad batch released.

Looks like the MJHARVEY_TINYBOXDEC1 WU's were bad. You might have server aborted them; I was still picking _7 WU's up this evening :(

The MJHARVEY_DUDMYREC15 WU's seem to be working.

---

FAQ's

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

At my systems the DECOY414-MJHARVEY_DUDMYRECxx where erroring, but with wingman too.

---

Greetings from TJ

skgiven wrote:

Looks like the MJHARVEY_TINYBOXDEC1 WU's were bad...The MJHARVEY_DUDMYREC15 WU's seem to be working.

For me, it's just the opposite: The MJHARVEY_TINYBOXDEC1 WU's are fine; it's the MJHARVEY_DUDMYREC15 WU's that are causing me problems.

---

DECOY....-MJHARVEY_DUDMYREC15-0-1-RND...._. is still nothing but failing on Windows 64bit, apparently due to an error in the input files:

Parse error on line 1 in file "protein.pdbqt": ATOM syntax incorrect: "9.00 -17.40" is not a valid AutoDock type. Note that AutoDock atom types are case-sensitive.

Yeah, well I buggered up that set of WUs.

Honestly, I do not understand why you aren't canceling this batch if you can't fix it?

Regards

In fact, I thought they had been cancelled. Will check.

Matt

I see, thanks for checking. No offense intended.