Posts by Richard Haselgrove

1) Message boards : Problems and Bug Reports : BRP4 Intel GPU app feedback thread (Message 133303)
Posted 2 days ago by Richard Haselgrove
Seems to be flowing more freely this morning (famous last words...). Got a dozen on my last request.
2) Message boards : Problems and Bug Reports : BRP4 Intel GPU app feedback thread (Message 133278)
Posted 3 days ago by Richard Haselgrove
I'm seeing the same thing, on all intel_gpu requests - and BRP4 (arecibo, non-GPU) is the only app version available for intel_gpu.
3) Message boards : Technical News : Fermi LAT Gamma-ray pulsar search #4 "FGRP4" (Message 133078)
Posted 11 days ago by Richard Haselgrove
The 1.03 version passed the 8 sec marker ...

A strange behaviour: after reaching ~25% whithin 6 min or so the progress bar makes a major step backwards to 2.4%

If you are using the recommended BOINC v7.2.42, or a later Beta build, BOINC will estimate and display a 'pseudo-progress' percentage while waiting for the first actual checkpoint and progress report from the science application.

If the first checkpoint is made quickly, or if the overall runtime estimate for the task is reasonably accurate, then the transition from pseudo-progress to real progress is almost invisible.

But if the estimate for the whole task is seriously wrong, pseudo- and real progress have time to diverge before the real figure is available, and a large correction becomes necessary.

Having a pseudo-progress display avoids the progress bar displaying 0.000% for extended periods, which tends to make users nervous.

A great explanation!
But can a big change of the estimated runtime also be handled by the BM (every version)? The initial estimated runtime was ~20 to 25 min, jumping then to > 4hrs. Maybe this is the reason why they time out on some machines.
My first 2 wu's are at 73% now with a runtime of ~3hrs and reporting a remaining time of ~1hr.
I'm using BM 7.4.12

By BM, I assume you mean BOINC Manager. As the term 'Manager' implies, that's the command-and-control module for BOINC, and doesn't do any actual work - your question would be better directed to the BOINC client.

And yes, the BOINC ecosystem as a whole - client and server - can handle a big change like this.

If both the server and the client are to a recent (2010 or later) specification, the adjustment is handled on the server, using tools like CreditNew and RuntimeEstimation.

If either (or both) of the server and client pre-date 2010 - as the server here at Einstein does - then both components drop back to the older 'Duration Correction Factor' mechanism (no longer documented, since the demise of the Unofficial BOINC Wiki).

Unfortunately, catch-22 applies in both cases. Neither CN/RE, nor DCF, updates their estimates until a task has successfully completed - in the case of CN/RE, 11 tasks have to complete and validate: in the case of DCF, a single completed task is sufficient. But if BOINC aborts the tasks for 'Maximum elapsed time exceeded' before successful completion......

Hence the references in this thread to 'innocculation' - modifying <rsc_fpops_bound> to bypass the infinite-loop safety-valve, and allowing completion so that estimate-modification can proceed. These are the sort of issues we were grappling with at Albert before attention switched to the new web design.
4) Message boards : Problems and Bug Reports : FGRP4 Observations and Problems (Message 133071)
Posted 11 days ago by Richard Haselgrove
They show a strange behaviour. After ~ 6 min the progress bar shows 25%, making a big step backwards then to 2,4%.
My first wu is now at 20% after 52 mins, the second at 16% after 47 min. Remaining time shows 3h35min and 3h16min now.
A third one started right now.
In the first stages the estimatet remaining time is at ~20 min.

See my explanation in the technical news area, replying to your matching post there.
5) Message boards : Technical News : Fermi LAT Gamma-ray pulsar search #4 "FGRP4" (Message 133070)
Posted 11 days ago by Richard Haselgrove
The 1.03 version passed the 8 sec marker ...

A strange behaviour: after reaching ~25% whithin 6 min or so the progress bar makes a major step backwards to 2.4%

If you are using the recommended BOINC v7.2.42, or a later Beta build, BOINC will estimate and display a 'pseudo-progress' percentage while waiting for the first actual checkpoint and progress report from the science application.

If the first checkpoint is made quickly, or if the overall runtime estimate for the task is reasonably accurate, then the transition from pseudo-progress to real progress is almost invisible.

But if the estimate for the whole task is seriously wrong, pseudo- and real progress have time to diverge before the real figure is available, and a large correction becomes necessary.

Having a pseudo-progress display avoids the progress bar displaying 0.000% for extended periods, which tends to make users nervous.
6) Message boards : Problems and Bug Reports : FGRP4 Observations and Problems (Message 133063)
Posted 11 days ago by Richard Haselgrove
The error on my fastest PC has a much longer stderr, of which one entry reads "Maximum elapsed time exceeded", although another entry buried deep in the might be interesting and reads
- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x76343226

That's the normal error when Boinc aborts the job because of "Maximum elapsed time exceeded".

Rom Walton once told me it was a deliberate choice by the developers. One possible reason for a task running far longer than expected is that the execution path for that particular dataset has branched into a previously undetected infinite loop. The full program debug logs are to help the developer find that loop.
7) Message boards : Cruncher's Corner : Parallella, Raspberry Pi, FPGA & All That Stuff (Message 132930)
Posted 17 days ago by Richard Haselgrove
And it should be available in a complete retail build next month (US release):

http://www.misco.co.uk/blog/news/02193/acer-launches-first-tegra-k1-powered-chromebook
http://www.techradar.com/news/mobile-computing/laptops/acer-chromebook-13-finds-luck-with-tegra-k1-processor-long-battery-life-1260731
8) Message boards : Technical News : Albert@Home down due to migration to Drupal (Message 132734)
Posted 27 days ago by Richard Haselgrove
I didn't see anybody else's profile, but I did see everyone's email address as a tooltip on mouseover the silhouette image by their posts.
9) Message boards : Problems and Bug Reports : change language (Message 132641)
Posted 31 days ago by Richard Haselgrove
On the Home Page under the header Community there is a option Language.

I think that just controls the language used to display this website - the question was about BOINC Manager.

In BOINC Manager, either simple or advanced view, choose the third item on the menu bar - 'Tools' in English, if you can recognise that in your current display language.

Click the second item on that menu - 'Options...' in English.

The first drop-down list on the Options dialog is the language selector. You'll need to restart the BOINC Manager for the new settings to be loaded.
10) Message boards : Technical News : Albert@Home down due to migration to Drupal (Message 132576)
Posted 35 days ago by Richard Haselgrove
Any news about Albert, did it get lost in the crossfire?

All I see there is You don't have permission to access /index.php on this server.

Details posted at http://boinc.berkeley.edu/dev/forum_thread.php?id=9517&postid=55135


Next 10

Home · Your account · Message boards

This material is based upon work supported by the National Science Foundation (NSF) under Grants PHY-1104902, PHY-1104617 and PHY-1105572 and by the Max Planck Gesellschaft (MPG). Any opinions, findings, and conclusions or recommendations expressed in this material are those of the investigators and do not necessarily reflect the views of the NSF or the MPG.

Copyright © 2014 Bruce Allen