Android E@H many computation errors
8 Sep 2019 18:22:14 UTC
Topic 219552
(moderation:
I have been given 49 tasks on Einstein@Home, and nearly all are getting to 60% completion then disappearing after showing "computation error". I believe I have unhidden my phone's info to allow a knowledgeable person to investigate. If you could help me track down the cause, I would be grateful. I'd like to continue helping, but honestly, seeing the numbers around here and the super computer muscle, paired with the apparent inability to complete a task, makes me question if I could even call this helping!
I found this error message in
)
I found this error message in one of the failed tasks:
This is a failsafe function in Boinc that aborts a task if it runs for to long. To complete a task you need to make sure that it gets enough runtime, you have 4 completed tasks so your device is capable of running them. But it only does so with about 10 000 seconds of margin to when Boinc will abort the task because it's taking to long.
JKnerdy wrote:... I'd like to
)
Thanks for starting your own thread. Everybody has to start somewhere and no matter how small the contribution, every little bit helps. Holmis has identified the problem and the solution is straightforward.
Your phone shows as having 8 processors (no doubt virtual) and BOINC will try to use them all (if allowed). The only thing you really need to do is restrict BOINC to a suitable subset so that concurrent tasks don't prevent each other from finishing in the allowed time. Here is what should allow you to get things running smoothly.
You can (at your choice) make these changes on the website as described and if you do, you need to click update in your local Boinc Manager in order for your client to become aware of the website changes. Alternatively, you can change the preferences locally in BOINC Manager (Advanced view) and then the client will be informed immediately. Local preferences override website preferences so no update is needed. Future changes to those prefs will need to be made locally unless you use the option (in the manager) to revert to website prefs. There are advantages and disadvantages with either method so you need to choose the one that suits you best and stay with that to perhaps avoid future confusion.
If allowing two tasks to run works well, you could further experiment by changing the % cores setting to 37.5% (or 50%) and allowing three (or four). Either of those would probably extend the crunch time (maybe by too much) and would certainly use more power and create more heat. You need to experiment to find the settings that best work for you. I would really advise starting low and testing, before gradually ramping up the number of threads in use. If there are problems with two, try just one (12.5%).
Good luck! Let us know how you get on :-).
Cheers,
Gary.
Thank you both for your help.
)
Thank you both for your help. I think it's good to go now. I'm letting it run one task at a time, takes about an hour for 10%. At least I get to participate some!