I see value in participating to R@H so I would like to complete more WU-work units per day than 1 WU per cpu core per day.

All the tasks so far are validated as "client error" which perhaps causes the 1 WU per cpu core per day - rule to step in.

Is there anything I can do to avoid the "client error" or any other trick to get more WU per day?

Look e.g.

ask ID	542536772
Name	Ploop5_3_1_1_abinitio_design_y003_006_63787_35_0
Workunit	493456645
Created	8 Nov 2012 8:32:21 UTC
Sent	8 Nov 2012 8:32:54 UTC
Received	8 Nov 2012 13:12:58 UTC
Server state	Over
Outcome	Client error
Client state	New
Exit status	0 (0x0)
Computer ID	1510982
Report deadline	18 Nov 2012 8:32:54 UTC
CPU time	10124.64
stderr out	
<core_client_version>7.0.27</core_client_version>
<![CDATA[
<stderr_txt>
[2012-11- 8 10:33:32:] :: BOINC:: Initializing ... ok.
[2012-11- 8 10:33:32:] :: 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. 
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. 
Setting WU description ...
Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_rev50262.zip
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/2012_11_7_mini_y003_folding.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
Setting up folding (abrelax) ...
Beginning folding (abrelax) ... 
BOINC:: Worker startup. 
Starting watchdog...
Watchdog active.
Starting work on structure: _00001
Starting work on structure: _00002
Starting work on structure: _00003
Starting work on structure: _00004
Starting work on structure: _00005
Starting work on structure: _00006
Starting work on structure: _00007
Starting work on structure: _00008
Starting work on structure: _00009
Starting work on structure: _00010
Starting work on structure: _00011
Starting work on structure: _00012
======================================================
DONE ::     1 starting structures  10123.7 cpu seconds
This process generated     12 decoys from      12 attempts
======================================================
BOINC :: WS_max 1.94906e+289

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

</stderr_txt>
]]>
Validate state	Invalid
Claimed credit	94.9080141977075
Granted credit	94.9080141977075
application version	---

Paavo

BOINC v7 often causes such problems. See this thread for discussion. There really is no way to override the task per day limit, which is normally 100 but is decreased each time an error is triggered.

You might consider changing your Rosetta preferences to indicate that you would prefer your work units to run for longer than the default 3 hours. You can designate a number as high as 24hrs. That way you'd typically only need one per day to keep the machine busy.

---

Rosetta Moderator: Mod.Sense

BOINC v7 often causes such problems. See this thread for discussion. There really is no way to override the task per day limit, which is normally 100 but is decreased each time an error is triggered.

It would be good to have easy to follow downgrade instructions for Ubuntu users.

You might consider changing your Rosetta preferences to indicate that you would prefer your work units to run for longer than the default 3 hours. You can designate a number as high as 24hrs. That way you'd typically only need one per day to keep the machine busy.

I still receive credit from the Tasks which were validated with Client Error status.
So I will give this a try first.

Found from Rosetta-www pages
Rosetta@home preferences --> Target CPU run time = 1 day
Assume that this is the correct place to set this.

You might consider changing your Rosetta preferences to indicate that you would prefer your work units to run for longer than the default 3 hours. You can designate a number as high as 24hrs. That way you'd typically only need one per day to keep the machine busy.

Found from Rosetta-www pages
Rosetta@home preferences --> Target CPU run time = 1 day

Now the work units are larger. They still trigger in validation the famous client error but it doesn't matter because
- the 1 wu per core per day rule doesnt matter with this 1 day configuration.
- and because credit is still given

[quote]
Now the work units are larger. They still trigger in validation the famous client error but it doesn't matter because
- the 1 wu per core per day rule doesnt matter with this 1 day configuration.
- and because credit is still given

It seems that the granted credit is upper bound to 300 for invalidated - client error wu.
Look:
resultid=544377307

Validate state Invalid
Claimed credit 654.285663218454
Granted credit 300
application version ---

Could the validation "invalidation" be because the missing version information?
What could be done to fix this validation challenge?

[quote]
Now the work units are larger. They still trigger in validation the famous client error but it doesn't matter because
- the 1 wu per core per day rule doesnt matter with this 1 day configuration.
- and because credit is still given

It seems that the granted credit is upper bound to 300 for invalidated - client error wu.
Look:
resultid=544377307

Validate state Invalid
Claimed credit 654.285663218454
Granted credit 300
application version ---

Could the validation "invalidation" be because the missing version information?
What could be done to fix this validation challenge?

Is there any practical way to overcome this challenge?

[quote]
Now the work units are larger. They still trigger in validation the famous client error but it doesn't matter because
- the 1 wu per core per day rule doesnt matter with this 1 day configuration.
- and because credit is still given

It seems that the granted credit is upper bound to 300 for invalidated - client error wu.
Look:
resultid=544377307

Validate state Invalid
Claimed credit 654.285663218454
Granted credit 300
application version ---

Could the validation "invalidation" be because the missing version information?
What could be done to fix this validation challenge?

Is there any practical way to overcome this challenge?

Btw. "Your results" link in Boinc Manager opens report page: where there are columns for Claimed credit and Granted credit. My contribution seems to get only the Claimed ones and the upperbound Granted ones wont even show up here.
I have understood that this has something to do with the setup and there is humungous thread about different trials to fix this behaviour but none have shown to be very successful, except the ones where people take away their graphics cards.
Also I believe that it is still worthwhile keep crunching R@h work-units even with the Client errors but I am no longer sure that it is so.

Can someone give practical hint how to fix this?

rgrds Pm

Can someone give practical hint how to fix this?

Need to look other projects to see if they also fail the same way.

rgrds Pm