Just a heads up to the scientists to check if they have enough work units ready to cope with the increased capacity from the new users.

From the home page:

640,798 - Total queued jobs
904,402 - In progress
341,521 - Successes last 24h

34,117 - New hosts last 24h

229.9 - TeraFLOPS estimate


As of today the project has about 166% of the active hosts it had in June, when it was reaching 130 TFLOPS.

See the graphs at BOINC stats for more information.

Hmmm ... from the credits view, invalid ones sometimes even have an advantage ... that's quite mean :´(

CPU time 43483 (preferred 28800), claimed 245, granted 20 because that stupid thing created only one decoy.

It has been a 4oo3_01_S_t000_cstw05_krypton_SAVE_ALL_OUT_161776_567_0

Hi.

I'll add myself to the list of those getting validate errors now as well, I think this has only started for me anyway since the servers had been moved.
It seams to be a mixture of task name types for both my rigs, plus with the trouble getting work that seamed start around the same time, just wondering if something got knocked about on one or more of the servers when they where moved.

just my 2c!

I am new to Rosetta and I am getting a lot of Invalid tasks reported as Validate errors. I did a test run of Rosetta a few weeks ago and about 30% of the tasks I ran then were Validate errors.

Some of my team mates said it might be because of my mild over clock. Since we were all crunching for a team event on another project I had not had a chance to run any more Rosetta tasks until yesterday. I removed my over clock and tried again. Validate errors are not as prevalent as they were but I am still getting them.

Here is Rosetta's explanation of a Validate error.

Validate error - The task was reported but could not be validated, typically because the output files were lost on the server.

I can only conclude that I am spending three hours plus on each task only to have 25 to 30 percent of them get lost on your server. Not acceptable. This needs fixed asap.

Task ID 651174635
Name gr040214_ama1_longee_newhair377_relax_SAVE_ALL_OUT_157229_40_0
Workunit 591389920
Created 3 Apr 2014 11:32:15 UTC
Sent 3 Apr 2014 11:35:21 UTC
Received 3 Apr 2014 14:05:41 UTC
Server state Over
Outcome Validate error
Client state Done
Exit status 0 (0x0)
Computer ID 1730267
Report deadline 13 Apr 2014 11:35:21 UTC
CPU time 2409.047
stderr out

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>
[2014- 4- 3 8:22: 1:] :: BOINC:: Initializing ... ok.
[2014- 4- 3 8:22: 1:] :: BOINC :: boinc_init()
BOINC:: Setting up shared resources ... ok.
BOINC:: Setting up semaphores ... ok.
BOINC:: Updating status ... ok.
BOINC:: Registering timer callback... ok.
BOINC:: Worker initialized successfully.
command: projects/boinc.bakerlab.org_rosetta/minirosetta_3.48_windows_x86_64.exe -out:file:silent default.out -in:file:s 00001.pdb -frag3 00001.200.3mers -in:file:native 00001.pdb -frag9 00001.200.9mers -silent_gz 1 -ex2aro 1 -relax::default_repeats 15 -in:file:fullatom 1 -run:protocol relax -ex1 1 -in:file:boinc_wu_zip gr040214_ama1_longee_newhair377_data.zip -out:file:silent default.out -silent_gz -mute all -detect_disulf True -in:file:native 00001.pdb -in:file:fullatom -in:file:s 00001.pdb -nstruct 10000 -cpu_run_time 10800 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 1434278
Registering options..
Registered extra options.
Initializing broker options ...
Registered extra options.
Initializing core...
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Initializing options.... ok
Options::initialize()
Options::adding_options()
Options::initialize() Check specs.
Options::initialize() End reached
Loaded options.... ok
Processed options.... ok
Initializing random generators... ok
Initialization complete.
Setting WU description ...
Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_b14204d.zip
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/gr040214_ama1_longee_newhair377_data.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
======================================================
DONE :: 99 starting structures 2408.23 cpu seconds
This process generated 99 decoys from 99 attempts
======================================================
BOINC :: WS_max 4.39628e+008

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
]]>

Validate state Invalid
Claimed credit 25.3788504634809
Granted credit 0
application version 3.48

That actually sounds like the screensaver. Would it be asking too much for a screenshot. You can email it to dekim at u. washington .edu

Does it look like the images on:

http://boinc.bakerlab.org/rosetta/rah_graphics.php ??

Mikey and Chilean thanks for the information.

At the most I only have room for two PCs most of the time I only have one running like at present I'm using my Q6700 quad @ stock speed 2.66. I believe speed wise Intel is faster than amd. Once I get enough money together I plan to build a Intel i7 3.2 system. Reason why I want to build a 3.2ghz system is because I don't believe in over clocking as it puts extra strain on hardware, I'll overclock a system if it's older and has good cooling. Because I don't have much room for computers that's why I want to build a big computer, my build will be a while away yet.

Awwww there is always room for more pc's, shelves let you go up instead of out! I have a 3 floor house and pc's on each floor. The basement has the most with 13 running down there. With a small program like VNC you don't even need a monitor, keyboard or mouse hooked up to each one all the time. Here's just an example http://www.flickr.com/photos/12424716@N04/3367914308/ of some of my basement stuff.

You'll notice that the invalid jobs have been granted credit if you click on the specific workunit. Looks like the validator has caught up now also.

this has been one of those rare occasions where we sent out a batch of workunits that had a change in output format with the latest app update and thus got rejected by our validator. It required us to rebuild our validator to fix the issue and the system had a little bit of catching up to do, possibly slowed down by the invalid batch.

http://boinc.bakerlab.org/rosetta/workunit.php?wuid=158648907

Two validate errors after full crunch.

Rosetta needs to think about how to apply credit when the problems are obviously of project/WU source.

Jim

Credit is applied to these as claimed - it doesn't show on the task's main page but does if you hit the Task ID link on the left.

HTH
Danny