![]() GitHub - wyim-pgl/BOINC: NSF Award #1664022 Abstract: Volunteer computing (VC) uses donated computing time consumer devices such as home computers and smartphones to do scientific computing. That is, some gradual loss of precision is possible, app not fails immediatelly on resuming from checkpoint, but after some more computations done, at very end of computations.īTW, if you need to run some debug/verbose build for checking why error occurs I will glad to run such build on my device. Looks like checkpointing improving is essential.įrom the other side, I'm almost sure there were no restarts between 95% and ultimate computation error. Skipping: /nbody_graphics_point_point_sizeĮrror loading Lua script 'astronomy_parameters.txt': :1: '' expected near '4'Įrror reading astronomy parameters from file 'astronomy_parameters.txt'įor last task I did whole NativeBOINC snapshots at ~92%, ~95% task completion and before reporting. Unrecognized XML in project preferences: nbody_graphics_point_point_size Skipping: /nbody_graphics_textured_point_size Unrecognized XML in project preferences: nbody_graphics_textured_point_size Unrecognized XML in project preferences: nbody_graphics_float_speed Unrecognized XML in project preferences: nbody_graphics_poll_period ![]() Unrecognized XML in project preferences: max_gfx_cpu_pct milkyway_separation 1.00 Linux ARM double So far all completed tasks were invalid ones. ![]() I don't think app was restarted many times for each task but few restarts per taks seem unavoidable (even with "untouched" state I saw some NativeBOINC restarts before). Few tasks were completed on that device working in usual manner. Will do SD-card snapshots while it goes again. Now I run another task from de_separation_09_2s_sample_2_*. NativeBOINC log doesn't show the cause of restart unfortunately. I captured different computation stages of this task as separate SD-card snapshots but cause there was no computation error I'm not sure if these snapshots interesting/useful. Of course, NativeBOINC restart means MW task restart too so it was impossible to run w/o restarts at all. At least one time I saw kind of SMS message (screen popup) came around time NetiveBOINC was restarted. What strange: NativeBOINC was restarted few times (not only MW task, but very NativeBOINC itself). So, it's unknown is it valid or invalid, server refused to check it.įrom device side it finished w/o error and was uploaded so I think it could be validated ok, no computation error. ![]() Well, this task ran better than previous (I did not press power button through whole run, phone screen was always on, dimmed), but not perfect: as one can see, another hosts complete task faster (though it took less than 2 days to get result) and my task got validation error. Fresh MW app was downloaded at project attaching so I started with fresh MW installation this time. Will report how it goes later.ĮDIT2: Before re-attaching to MW NativeBOINC manager and core client were updates to latest revisions. Unfortunately, MW is my the only chance to make use of this device for BOINC cause all other projects require too much free inner space and NativeBOINC still can't make use of SD card space.ĮDIT: ps_separation_09_2s_sample2_* task was downloaded. Of course can't recall what series were that time so will re-do this experiment again. ![]() Sorry for long delay, I was occupied with other things. You can simply detach/attach project or reinstall NativeBOINC. Please check project directory (milkyway) and please do not suspend/resume workunit (too often) when crunched (it impact on the final results). Do you can tell me what was you crunching workunit (series)? I crunched ps_separation_09_2s workunit. Unfortunatelly I got good results (without NaN's). I checked original version on brother's smartphone (with ARMv6 VFP). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |