Now that the RALPH beta project has finished (?) and the new client is in place on the live Rosetta project, the crunch time per WU on the Work tab in BOINC Manager should accurately reflect the preference set in the Rosetta preference screen.

I set my preference to 2 hours (the lowest possible), and attached to the live Rosetta project.

BOINC downloaded a handful of WUs, and every one had 5:40 as the time to completion, and it was nowhere near enough WUs to fill the 10 day queue.

I did a <RESET> , <UPDATE> to make sure the prefences were loaded, and still got 5:40 on the WUs.

What's the deal? If the fixed crunch time is 2 hours, why don't I get the 120 WUs it should take to fill my 10 day queue?

Somethings broken.

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

It takes time before the figure adjusts itself, you have to process a good number before it gets there....it is the fault of the RDCF....

---

This is a boinc client issue. We do not have a way to modify the rsc_fpops_est (the value used by the client to estimate the time to completion). As Scribe mentioned below, the correction factor should eventually make the time to completion more accurate.

RALPH IS NOT FINISHED. IT IS AN ONGOING PROJECT FOR TESTING.

If the time to completion is user-defined, why is the client doing an estimate?

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

It takes time before the figure adjusts itself, you have to process a good number before it gets there....it is the fault of the RDCF....

RDC should not even be considered in this case. The time to completion is user defined. The WU unit runs for as long as the user has set in the preferences.

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

This feature/preference is unique to our project and the boinc client is not yet designed to use this user defined preference for the time to completion. Maybe the boinc developers can add this into the next client version. The DCF is, thus, still relevant for the time to competion.

This feature/preference is unique to our project and the boinc client is not yet designed to use this user defined preference for the time to completion. Maybe the boinc developers can add this into the next client version. The DCF is, thus, still relevant for the time to competion.

Also remember for the shorter run time settings, the WU will always complete at least one model. In some cases that one model may take a lot longer than 2 hours. During the time it takes to run the first model, the WU will only show 1% complete. It might look like the WU is hung, but if you check the screen saver or image display, you will see the steps running. On some WU a model only take about 35,000 steps and 5 min. others may take over 500,000 steps and take 3-4 hours to do a single model. So if you have your time set to 2 hours, the WU will run way over that to do the first model. This means that you could have more work on your system than you think you have.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

I thought that the estimated time to completion was driven by something in the WU. Different WUs from different projects get different estimated times.
That sounds like a project-specific thing, not a BOINC Manager issue. The rosetta client should be altering the estimated time to match the user preference.

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

I thought that the estimated time to completion was driven by something in the WU. Different WUs from different projects get different estimated times.
That sounds like a project-specific thing, not a BOINC Manager issue. The rosetta client should be altering the estimated time to match the user preference.

It is a combination of things. How long you set the time setting tells the application how long you want the WUs to run.

But it only does so based on the length of a model run for that particular flavor of WU. The shortest run time would be the length of 1 model generation. So if you have a flavor of WU that can do a model in say 5 min. You can set the time to 2 hours and the WU will complete in about that amount of time. But if the particular type of WU would take say 4 hours to do 1 model, then that WU will run for at least 4 hours no matter what the time setting is.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

I thought that the estimated time to completion was driven by something in the WU. Different WUs from different projects get different estimated times.
That sounds like a project-specific thing, not a BOINC Manager issue. The rosetta client should be altering the estimated time to match the user preference.

Still not reading the answers are we??? Why not read the ones given to you?

This feature/preference is unique to our project and the boinc client is not yet designed to use this user defined preference for the time to completion. Maybe the boinc developers can add this into the next client version. The DCF is, thus, still relevant for the time to competion.

I thought that the estimated time to completion was driven by something in the WU. Different WUs from different projects get different estimated times.
That sounds like a project-specific thing, not a BOINC Manager issue. The rosetta client should be altering the estimated time to match the user preference.

We are only able to interact with the boinc client/manager via the boinc api with our application. The api does not allow us yet to modify the time to competion value during a run so we cannot change it when a user does so. You are correct, the estimated time to completion is driven by something in the WU (rsc_fpops_est) but it is set when the work unit is generated and once it is downloaded onto your client we cannot change the value since the boinc api does not let us yet.

See http://boinc.berkeley.edu/api.php. This is what we have to work with.