Hi all, One of my PC's does not have a permanent connect to the net and as a result I have the "Connect to the network about every.." setting set to 5 days in the School preferences setion of my preferences. This has been working fine for me for quite a long time now, but recently something has gone amiss. The PC is on 24/7 and I am only able to get about 12 hours of work a day, which I don't understand, thus the PC is sitting idle for the other half of the day. The PC in question IS using the "School" preferences (as stated in the message log), when rosie fires up after a reboot or I shut it down to restart rosie, it requests 432000 seconds of work (about 120 hours yeah?), but for some reason it only recieves 43200 seconds of work (about 12 hours). There is no error associated with this discrepancy - at least not any more.... recently I upgraded both R@H and BOINC at virtually the same time, which is roughly about the same time this error started occuring. Originally, after the upgrades, I was recieving a strange error in the message log from the server that went something like this:::

Message from Server...Machine is only on 10% of the time and rosetta is running 78% of that, work not sent

:::

The error no longer appears when the machine requests work, but I still am only getting about 10% of what the PC is requesting. Subsequent detaches, reattaches, uninstalls and reinstalls - even upgrading BOINC to the unstable testing version (5.6.5) has reaped no results. I am at a loss as to what to do to remedy this problem and would appreciate any help given. TIA

---

Will work for bandwidth!!

Have a look (I use internet explorer) at this file:
C:Program FilesBOINCclient_state.xml
The first nested section is <host_info>, go to the section section called <time_stats> and copy/paste the contents of that section in to a reply here.

...in the meantime, download a set of WUs, suspend them all, then update the project and it should get more.

Another thing, to help you crunch for at least one full day, would be to set your runtime preference to 24hrs. At least for your "School" location.

---

Rosetta Moderator: Mod.Sense

[quote]Have a look (I use internet explorer) at this file:
C:Program FilesBOINCclient_state.xml
The first nested section is <host_info>, go to the section section called <time_stats> and copy/paste the contents of that section in to a reply here.

OK here's the requested info from the client_state file....

<time_stats>
<on_frac>0.157307</on_frac>
<connected_frac>0.226434</connected_frac>
<active_frac>0.999797</active_frac>
<cpu_efficiency>0.890929</cpu_efficiency>
<last_update>1165834482.701714</last_update>
</time_stats>

---

Will work for bandwidth!!

This indicates that in BOINC's experience, your machine is powered on 15% of the time (note, higher then the 10% that it used to think). So, even though your machine is on 24/7, BOINC hasn't fully reflected that yet. So when it orders 432000 seconds of work, it is 432000 seconds of wall-clock time. And within that BOINC is estimating your machine will be running 15% of the time, so it only actually tries to get 64,800 seconds of actual work, which it is estimating will take you the 5 days to complete.

BOINC will adjust over time to the fact that the machine is on much more then 15% of the time. And it will gradually be ordering more and more work. In the meantime, the simplest thing to do would be to set a 10 day quota for that location, and use 24hr work unit runtime preference. Then gradually reduce the quota back down to the 5 days.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/