Posts by Saenger

1) Message boards : Number crunching : NoContraintsWithDisk200 vs. south4s (or whatever) (Message 68547) Posted 16 Apr 2019 by Saenger Post: Just a thought here: I suspect most (if not all) of the people having the "instant fail" trouble with the new work units might be running older versions of BOINC which have a maximum command line capability of about 1024 characters. There have been other tasks in the past that had lots of parameters and overflowed that limit, though I'm not sure it produced this error. In particular, it appears the OP is using 7.2.42 (which certainly truncated command lines for one of the earlier groups of tasks with extra parameters!) So if nothing else seems to work it might be worth trying a newer BOINC client if one is available for your distribution. I think 7.8 didn't have this problem, and I know 7.14.2 doesn't because that's what I use and it runs these new tasks quite happily. But the names of the fine running WUs are considerably longer than the ones of the failing WUs. Perhaps I'll try a new BOINC some time later.
2) Message boards : Number crunching : NoContraintsWithDisk200 vs. south4s (or whatever) (Message 68542) Posted 15 Apr 2019 by Saenger Post: Some reason your BOINC.exe can't create the slot directory for the WU? No, as it's doing fine on the NoContraintsWithDisk200, just the south4s are crashing. And I don't care about linguistic sophistry, they fail, full stop. Before everything was fine as well, so nothing here with me.
3) Message boards : Number crunching : NoContraintsWithDisk200 vs. south4s (or whatever) (Message 68533) Posted 14 Apr 2019 by Saenger Post: I got tons of invalid tasks in the last couple of days, and I don't have a clue why. I know the names of those who get crunched fine lately all include NoContraintsWithDisk200, while those without this, and currently south4s in its name, all crash asap. As I don't loose much crunchhtime due to their immediate crashing, I won't stop with MilkyWay, but... I'd like to know how I can avoid DLing those WUs that won't run, or, even better, how to get them to run on my machine.
4) Message boards : News : Database Maintenance 9-4-2014 (Message 67796) Posted 7 Sep 2018 by Saenger Post: I'm getting credit, even for WUs that got crunched after the maintenance. And I have a bunch of _1 WUs an my machine. So they are probably getting things sorted by and by.
5) Message boards : News : Database Maintenance 9-4-2014 (Message 67788) Posted 7 Sep 2018 by Saenger Post: Yep I have nearly 4000 invalids :( Not invalid, just not yet validated, because they are waiting for the wing-WU. On one and the other of your computers.
6) Message boards : News : Database Maintenance 9-4-2014 (Message 67784) Posted 6 Sep 2018 by Saenger Post: Yep, all of my WUs are _0 as well, so it looks like _1 are kept behind for now. What went wrong after the restart of the machines?
7) Message boards : News : Bad Runs Over the Weekend (Message 66658) Posted 20 Sep 2017 by Saenger Post: I aborted all with 18 or 20 in the name, and without a fixed somewhere. All others run fine. Some seem to be resend until 5 are done, but they don't last long.
8) Message boards : Number crunching : Errors (Message 66633) Posted 17 Sep 2017 by Saenger Post: Hey Add me pls to the List, same Errors here, over 90%. Same Batch of WUs "de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy" LG Sandra Wrong;) I've got some 20 in my list of errors as well, and some are called Random, some not. Looks a wee bit random to me ;) P.S.: I just saw, you changed your post, so now it fits here as well ;)
9) Message boards : Number crunching : Errors (Message 66628) Posted 16 Sep 2017 by Saenger Post: My BOINC says this: So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [slot] assigning slot 0 to de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [slot] linked ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_1.46_x86_64-pc-linux-gnu__opencl_nvidia_101 to slots/0/milkyway_1.46_x86_64-pc-linux-gnu__opencl_nvidia_101 So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [slot] linked ../../projects/milkyway.cs.rpi.edu_milkyway/parameters-18-3s-ModfitConstraintsWithDisk.txt to slots/0/astronomy_parameters.txt So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [slot] linked ../../projects/milkyway.cs.rpi.edu_milkyway/stars-18.txt to slots/0/stars.txt So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [task] ACTIVE_TASK::start(): forked process: pid 18869 So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [task] task_state=EXECUTING for de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 from start So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| Starting task de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 So 17 Sep 2017 01:03:11 CEST \| Milkyway@Home \| [cpu_sched] Starting task de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 using milkyway version 146 (opencl_nvidia_101) in slot 0 So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [task] Process for de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 exited, status 256, task state 1 So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [task] process exited with status 1 So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [task] task_state=EXITED for de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 from handle_exited_app So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [sched_op] Deferring communication for 00:03:01 So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [sched_op] Reason: Unrecoverable error for task de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [task] result state=COMPUTE_ERROR for de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 from CS::report_result_error So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| Computation for task de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 finished So 17 Sep 2017 01:03:13 CEST \| Milkyway@Home \| [task] result state=COMPUTE_ERROR for de_modfit_fast_18_3s_146_bundle5_ModfitConstraintsWithDisk_Bouncy_2_1500622801_16641904_2 from CS::app_finished The WU has this as stderr: <core_client_version>7.2.42</core_client_version> <![CDATA[ <message> process exited with code 1 (0x1, -255) </message> <stderr_txt> <search_application> milkyway_separation 1.46 Linux x86_64 double OpenCL </search_application> Reading preferences ended prematurely BOINC GPU type suggests using OpenCL vendor 'NVIDIA Corporation' Setting process priority to 0 (13): Permission denied Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' Switching to Parameter File 'astronomy_parameters.txt' <number_WUs> 5 </number_WUs> <number_params_per_WU> 21 </number_params_per_WU> Number of parameters doesn't make sense 00:40:15 (6533): called boinc_finish(1) </stderr_txt> ]]> Something's fishy, but they only take a second, so not much is lost in terms of crunch time ;)
10) Message boards : Number crunching : Credit and CPU utilisation of NBody_104 (Message 56735) Posted 4 Jan 2013 by Saenger Post: N-Body does not use the GPU at this time, as the GPU code is still in development. Jake Then why do you send them out, and block the GPU from doing real work?
11) Message boards : News : Nbody 1.04 (Message 56724) Posted 4 Jan 2013 by Saenger Post: Please look in this thread in numbers as well, these WUs should probably not be sent to GPUs, as they just obviously waste their power.
12) Message boards : Number crunching : Credit and CPU utilisation of NBody_104 (Message 56722) Posted 4 Jan 2013 by Saenger Post: I just looked those nvidia-nbodys up in my WU-list, and saw that they get extremely poor credits for a GPU-WU. Here's an example with paallel CPU-results (290919767): 374569179 256454 4 Jan 2013 \| 5:35:27 UTC 4 Jan 2013 \| 5:50:05 UTC Fertig und BestÃ¤tigt 198.13 195.52 1.31 MilkyWay@Home N-Body Simulation v1.04 374579051 449717 4 Jan 2013 \| 5:55:27 UTC 4 Jan 2013 \| 10:04:38 UTC Fertig und BestÃ¤tigt 197.60 197.60 1.31 MilkyWay@Home N-Body Simulation v1.04 (opencl_nvidia) 374676981 456675 4 Jan 2013 \| 10:07:22 UTC 4 Jan 2013 \| 10:16:00 UTC Fehler beim Berechnen 0.00 0.00 --- MilkyWay@Home N-Body Simulation v1.04 374684677 475680 4 Jan 2013 \| 10:19:42 UTC 4 Jan 2013 \| 10:53:07 UTC Fertig und BestÃ¤tigt 189.65 187.81 1.31 MilkyWay@Home N-Body Simulation v1.04 They all took about the same amount of time on the CPU and on the clock, but mine probably used the GPU as well, 'though I can't say, as it crunched while I was away from the machine. There are two possibilities: -> They really don't use the GPU, then they should never be sent as GPU-WUs -> They use the GPU, but are so poorly programmed, that they can't make any real use of it, which should not happen as well -> They use the GPU for crunching, and really do work on the GPU, so they should be awarded much more credits compared with CPU-only. If all results of one WU should do the same work, the GPU-ones are a waste of ressources.
13) Message boards : Number crunching : de_plum_slice_EMD_NEW_100K error (Message 55007) Posted 4 Jul 2012 by Saenger Post: Slightly different here on Linux, but with same result: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=249328133 <core_client_version>6.12.34</core_client_version> <![CDATA[ <message> process exited with code 15 (0xf, -241) </message> <stderr_txt> <search_application> milkyway_nbody 0.88 Linux x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 3 max threads on a system with 4 processors Error reading histogram line 37: massPerParticle = 0.000100 16:43:06 (6509): called boinc_finish </stderr_txt> ]]> Odd enough, in-between the 22 errors is one good one: http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=249135420 <core_client_version>6.12.34</core_client_version> <![CDATA[ <stderr_txt> <search_application> milkyway_nbody 0.88 Linux x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 3 max threads on a system with 4 processors Histogram has 16250 bodies with 16250 in accepted bins <search_likelihood>-0.281333565711975</search_likelihood> 10:17:12 (27147): called boinc_finish </stderr_txt> ]]>
14) Message boards : Number crunching : Boinc Client for Android (Message 54498) Posted 23 May 2012 by Saenger Post: Is the thread in the polish forum the only support thread? Because most people will very probably have problems to register there... Anyway, in hope it can be answered here, I copy here a question from the SETI forums: When i open it, I have to configure it to a new host, and I have no clue as to how to do that. I was wondering if anyone here knows what to do? It is asking for Host Nickname, Address and password, using port #31416 That's what BOINC always asks if you want to attach a new host to a new project. If you chose "Existing Account" instead of "New Account" you just have to give your email and password. If you use BAM! (or any other account manager), you can attach projects to your android there as well. I have just finished my first 2 WUs on my Galaxy S2, not that bad for a mobile methinks.
15) Message boards : Cafe MilkyWay : Word Link (Message 15454) Posted 15 Mar 2009 by Saenger Post: lake
16) Message boards : Cafe MilkyWay : Word Link (Message 15375) Posted 14 Mar 2009 by Saenger Post: LysergsÃ¤urediethylamid
17) Message boards : Cafe MilkyWay : Word Link (Message 15355) Posted 14 Mar 2009 by Saenger Post: Schweinshaxn
18) Message boards : Cafe MilkyWay : Word Link (Message 15322) Posted 14 Mar 2009 by Saenger Post: Huckleberry Finn
19) Message boards : Cafe MilkyWay : Word Link (Message 15316) Posted 14 Mar 2009 by Saenger Post: levee
20) Message boards : Cafe MilkyWay : Word Link (Message 15314) Posted 14 Mar 2009 by Saenger Post: kd lang

Next 20