I have set my connection to 10 days but Rosetta only give me 5-10 units per day, each work unit takes between 2hrs and 3 hrs. How do I get it to download more then 10?

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

Moved from Science forum

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Open the "clientstate.xml" file (located in c:programfilesboinc) copy and paste the values you see for the following (they should be about a dozen lines down from the top):NOTE: do not save the file after opening it

- <time_stats>
<on_frac>0.982556</on_frac>
<connected_frac>0.997521</connected_frac>
<active_frac>0.999762</active_frac>
<cpu_efficiency>0.676768</cpu_efficiency>

How many Rosetta's are in your "work" tab, and what does it "estimate" the completion time to be?

tony

Open the "clientstate.xml" file (located in c:programfilesboinc) copy and paste the values you see for the following (they should be about a dozen lines down from the top):NOTE: do not save the file after opening it

- <time_stats>
<on_frac>0.982556</on_frac>
<connected_frac>0.997521</connected_frac>
<active_frac>0.999762</active_frac>
<cpu_efficiency>0.676768</cpu_efficiency>

How many Rosetta's are in your "work" tab, and what does it "estimate" the completion time to be?

tony

Tony,

I think this might be his time setting. If he is set for 10 days for connections, and 10 hours for processing time that will produce a different download then say a 10 day setting, and a 1 hour time setting.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Open the "clientstate.xml" file (located in c:programfilesboinc) copy and paste the values you see for the following (they should be about a dozen lines down from the top):NOTE: do not save the file after opening it

- <time_stats>
<on_frac>0.982556</on_frac>
<connected_frac>0.997521</connected_frac>
<active_frac>0.999762</active_frac>
<cpu_efficiency>0.676768</cpu_efficiency>

How many Rosetta's are in your "work" tab, and what does it "estimate" the completion time to be?

tony

Tony,

I think this might be his time setting. If he is set for 10 days for connections, and 10 hours for processing time that will produce a different download then say a 10 day setting, and a 1 hour time setting.

So what you are saying is I need to edit my general pref's?


Hope this is the right part you needed
[quote-xml file]- <time_stats>
<on_frac>0.133622</on_frac>
<connected_frac>0.982849</connected_frac>
<active_frac>0.999828</active_frac>
<cpu_efficiency>0.960982</cpu_efficiency>
<last_update>1147990756.625000</last_update>
</time_stats>
- <net_stats>
<bwup>0</bwup>
<bwdown>0</bwdown>
</net_stats>
[/quote]

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

Hope this is the right part you needed

<on_frac>0.133622</on_frac>

It is the part I needed. See how your percentage ON time is only 13 percent. This is taken into account when requesting work. See Work Buffer in the Wiki. It says:

The projects will be contacted in an order that is driven by a number of factors, including: 


Long Term Debt 
Resource Share 
Average Turnaround Time 
% of time client is on 
Deadline 

so it's requesting less because it thinks your puter is ON less.

tony

...So what you are saying is I need to edit my general pref's?
...

I only looked at one of your systems, but it was set for 3 hours in the preferences. This would be under your "Target CPU Run time" preferences. If you want more Workunits (although I can't imagine why) you set that value to a low number, and your connection frequency to a high number.

But the it would be better to load fewer workunits and run each one longer. So I would set my connection time to something less than a day, like ".2", and my time preference to something like 12 hours. On a single CPU system that would generate 2 work units per day. The credit claims would be correspondingly higher, but the total work is the same. That way when the next version of the Application comes out you can rest you system to no new work. Set the time to 1 hour, clear your queue, rest the time to your favored setting and get the new application right away. If your system is really stable, your could run a single work unit for up to 24 hours. This also reduces your network traffic.

By the way, Running fewer work units for a longer time kicks your RAC up faster than normal processing (just thought you might want to know).

There is a lot more detail on this in the FAQs, linked from my signature.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

If the ON frac isn't accurate,you can edit it.

Exit Boinc (file-exit) NOT the red X.
open clientstate.xml in notepad
edit that value to read:(or whatever your best estimate is)

<on_frac>1.000000</on_frac>

Make sure you have 6 digits past the decimal

save file
exit notepad
restart boinc.

The more units I can have to process, the less times I have to dialup to get more.. I am on dialup and it cost me everytime I dial...

So whats the best settings to have?

EDIT: and I have edited "client_state.xml" to make it <on_frac>1.000000</on_frac>

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

The more units I can have to process, the less times I have to dialup to get more.. I am on dialup and it cost me everytime I dial...

So whats the best settings to have?

The time setting was invented just for modem people. Figure you can run a single WU for up to 24 hours, I see in the science forum that the WUs just got smaller so that will help your download already.

But the trick would be to get 6 WUs and run them each 24 hours. Then you would only have to connect once a week. You will have to play with it to see what setting gives you what you need. I think you can adjust the time setting after you download so you can play with the connect time until you have what you need and then set the time for for processing.

At the moment I have 18 units and estimated at 02:43:33 to complete each one, so thats better then before but still only over a days worth of crunching.
I dont know much about Rosetta, and dont understand when you have been saying about running a unit for 24 hrs...

I onlt started running Rosetta again because of the CASP7 email

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

At the moment I have 18 units and estimated at 02:43:33 to complete each one, so thats better then before but still only over a days worth of crunching.
I dont know much about Rosetta, and dont understand when you have been saying about running a unit for 24 hrs...

I onlt started running Rosetta again because of the CASP7 email

Hi Rusty,
At rosetta they've enabled us to select how long we want each task to run,
In the Rosetta@Home preferences https://boinc.bakerlab.org/rosetta/prefs.php?subset=project

You need to set (for the correct location of that computer) the 'Target CPU run time' to 1 day

A task will then crunch for ~24hrs, This saves people like me and you on dial-up the frequent connection and given each task is 2MB to 5MB reduces the overall download per day.
Then if you set it too say connect ever 4 days, you should get 4 tasks (it may take time to settle out.

Also as soon as you set the Target CPU runtime, you'll need to hit the Update button in BoincManager for Rosetta, this then apply the setting and will also apply it to the tasks in the queue.
Then ignaore estimated time in boincmanager for a while :-)

---

Team mauisun.org

At the moment I have 18 units and estimated at 02:43:33 to complete each one, so thats better then before but still only over a days worth of crunching.
I dont know much about Rosetta, and dont understand when you have been saying about running a unit for 24 hrs...

I onlt started running Rosetta again because of the CASP7 email

I don't want to put too fine a point on this, but please take a moment to read this FAQ which discusses the Time setting. There are other FAQs that may help you understand the NEW Rosetta and how it works as well.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

At the moment I have 18 units and estimated at 02:43:33 to complete each one,

That estimate is just BOINC's guess based on what the last few WUs took. If you set the crunch time to 24 hours then BOINC's guess will still say 02:43:33. When BOINC sees that WUs are now taking 24 hours, then it should eventually adjust its guess to 24 hours.

Firstly, I cant thank you all for the amount of help you have provided me. Thank you so much. I am so happy to see the amount of people ready to help with the sillest of questions..

mmciastro - I do run other BOINC projects but what I have done is create a new copy for each project, I installed BOINC and move that 'blank' dir, to a different Hard drive so I have a fresh copy of BOINC, then what I do is copy that 'blank' folder and move it to a central location where I keep all my DC project, and I then proceed to attach a project and I also rename the folder to something like 'Rosetta - BOINC','SETI - BOINC', 'HashClash - BOINC' etc.. This may be a strane way to do it but I can keep track of what BOINC project I am running..

So what I might do now is, set the client to 'no more work' and finish the tasks I have, then edit my preference to reflect all the great advise you people have supplied me, by requesting longer tasks...

Say 12hrs and connect every 5 days? Does that sound good? Hopefully by doing this I can get some larger scores of the units I'm doing..

Once again thank you for all your help and support..

Thank you

---

- - - - Rusty - - - -



DC-Vault
Team Ninja's DC-Vault Click Link Here

You do know boinc was designed to meet your requested resource share per project and to handle literally dozens of projects at the same time, don't you? you must really like to micromanage. LOL That's OK.

The DCF (duration correction factor) is used in determining how many wu's you'll get. If you set your "cpu run time" preferences from 3 (not selected) to 12, then all work you currently have on hand will try to run around 12 hours. After the very first 12 hour run, your estimated time to comp will immediately jump to match that figure, and will be used when requesting work. What I'm saying is changing after loading up, will change the 2 day cache into a 12 day cache. However, the next time you ask for work, you'll likely just get 3-6 wus. The DCF will always jump to the highest run time, but it only comes down 10% of the difference when you do the work faster than anticipated. This is going to fight what you're trying to do.

"MM" is right about this. That is really why I gave the instructions in this post. You would have to repeat this adjustment of the time setting, loading and reseting of the time again. to keep things the way you describe.

In theory, you will eventually be able to set your time to 4 days, and if you set your connect time to match that, the system would give you a single work unit which would run for nominally that amount of time +/-. Eventually the BOINC folks are supposed to integrate the time concept into the baseline BOINC system and it will all work smoother after that. Right now it works, but BOINC has no clue about the time setting, and so you can use it to trick BOINC into doing things it would otherwise not be able to to. Some times this is good, sometimes its not.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact