To deal with the problem below, I added a new API function boinc_fraction_done_exact(double) This is like boinc_fraction_done(), but in addition it tells the client that the fraction done is accurate, and it can estimate task duration based solely on fraction done and current elapsed time. (Note: only new clients will do this).
If your task has a known total duration T, you can do double x = boinc_elapsed_time(); boinc_fraction_done_exact(T/x); ----------- In addition, I changed the formula for estimating duration (in the non-exact case) so that the weight of the dynamic estimate is FD rather than FD^2. This gives more weight to the dynamic estimate. -- David On 30-Apr-2014 9:29 AM, Martin McCaffery wrote: ...
An unrelated question is: so, my program works by running for a period of time, timing out deliberately then returning the results along with a "continuation" input file. As such, the time remaining on a given job is known pretty well (ie. defined by the job admin), but is dependent on the command-line arguments for the job itself. Is it possible to easily input this to the BOINC API such that the client shows an appropriate time-remaining estimate?
_______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
