Message boards :
News :
Nbody release v1.72
Message board moderation
Author | Message |
---|---|
Send message Joined: 19 May 14 Posts: 73 Credit: 356,131 RAC: 0 |
Hey All, I just released version 1.72 of nbody for linux and windows. Mac to follow soon. I have also put up some new runs. Please let me know if there are any issues. Thank you for your continued support, Sidd |
Send message Joined: 6 Mar 17 Posts: 8 Credit: 58,786,575 RAC: 16,347 |
some of my 1.72 (not all) say: "computation error" |
Send message Joined: 6 Mar 17 Posts: 8 Credit: 58,786,575 RAC: 16,347 |
sim ok: Application MilkyWay@Home N-Body Simulation 1.72 (mt) Name de_nbody_9_27_2018_v172_20k__sim_2_1536217849_153490 State Ready to report data never: Application MilkyWay@Home N-Body Simulation 1.72 (mt) Name de_nbody_7_23_2018_v170_20k__data_3_1536217849_32740 State Computation error |
Send message Joined: 1 Jan 08 Posts: 2 Credit: 33,443,291 RAC: 12 |
Hi all, I have the same experience: as of Sep 28 2018 I found more than 150 WU's failing running N-Body Simulation 1.72 (mt). I noticed the same as Jan Henrik above: the failing WU's are all ".._v170_20k__data_.." There are no failing WU's ".._v172_20k__sim_.." I did some random check for valid "data" WU's, but did no find any. Too many to check them all. The failing WU's all error out after 2 sec. of processing time with the following: <core_client_version>7.10.2</core_client_version> <![CDATA[ <message> De gegevens zijn ongeldig. (0xd) - exit code 13 (0xd)</message> <stderr_txt> <search_application> milkyway_nbody 1.72 Windows x86_64 double OpenMP, Crlibm </search_application> Using OpenMP 2 max threads on a system with 8 processors Error evaluating NBodyCtx: [string "-- /* Copyright (c) 2016 Siddhartha Shelton..."]:85: bad argument #1 to 'create' (Missing required named argument 'IterMax') Failed to read input parameters file 18:48:10 (119036): called boinc_finish(13) </stderr_txt> Hope this info helps. Regards, Ruud |
Send message Joined: 16 Aug 10 Posts: 15 Credit: 32,160,978 RAC: 0 |
I am running an AMD A10-6800k Win 10 64 Pro build 17763.104 and the N-Body Simulation 1.72 (mt) 4 CPUs, seem to for lack of better definition run away. The first one I let run for 24 hours before aborting, then today I had two more (de_nbody_10-11-2018_v172_20k_data_2_1538704602_247830_0 and de_nbody_10-11-2018_v172_20k_data_1_1538704602_247907_0) which are exhibiting similar symptoms. The symptoms are the Remaining increases at more than double the Elapsed. I currently have them suspended. |
Send message Joined: 16 Aug 10 Posts: 15 Credit: 32,160,978 RAC: 0 |
OK with the latest MSFT patches it appears to be functioning again. I am on the insider track at MSFT for Win10 and receive many "updates" before they are ready for prime time. I really dislike devops style of coding. Note the latest patches did not change the OS build number which I can not explain. |
Send message Joined: 8 Aug 08 Posts: 21 Credit: 468,893 RAC: 338 |
@PROJECT ADMINS: USERS STILL HAVING PROBLEMS WITH LATEST Nbody release v1.72 BUILD. SEE > http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=4347 |
Send message Joined: 19 Jul 10 Posts: 622 Credit: 19,254,980 RAC: 1 |
Please let me know if there are any issues. Well, no errors so far, but the mix of (mt) and non-(mt) tasks causes lots of idle time on my CPU, so it would be good if we could choose in the preferences which one we would prefer to use. If there's a single core task running, BOINC will even not start another already downloaded single core task unless it's the next one in the list (or I manually suspend all mt tasks between those two). |
©2024 Astroinformatics Group