1)
Message boards :
Number crunching :
Error While Computing after brief processing with Orbit Fitting work units
(Message 77007)
Posted 15 days ago by eiernacken1983 Post: Same here! Don't worry it is not related to your machine. I usually check other computers via credit statistics whether they have the same problem. That seems to be the case. So this is a general problem. |
2)
Message boards :
Number crunching :
Linux RX 5700 XT All GPU WU Fail
(Message 70332)
Posted 10 Jan 2021 by eiernacken1983 Post: It is an issue wird the driver. You have probably installed Version 20.45, which doesn‘t work with MW. Try 20.40, that should work. Me and my teammates have the same issue with our Radeon GPUs. The other option is waiting for a driver update which fixes the problem. ETA unknown... |
3)
Message boards :
Number crunching :
Selecting tasks for CPU
(Message 70129)
Posted 24 Sep 2020 by eiernacken1983 Post: How did you decide that NBody are better for CPU than Separation? I think he compared the time of the separation tasks when processed on GPU vs CPU. Separation on GPU: 12 - 300 seconds (depending on the gpu) Separation on CPU: 5400 seconds less than 300 seconds < 5400 seconds --> so it is not efficient to process separation on CPU As NBody can only be processed on the CPU he doesn't want to block his CPU with Separation units. If you use a GPU the you don't care about the small amount of credits you can make with a CPU. (Separation: 1 task * 8 CPUs yield 1816 in a same ~1,5 hrs --> separation on Radeon VII: 12 Secs/task --> 300 Tasks per hour --> 450 tasks per 1.5 hours = 68,100 credits) So if you want to maximize scientific output (not credits) for the project you should do separation on GPU and NBody on CPU. I think this was the intention of Bill Eckard. If yes, I agree with him :-) |
4)
Message boards :
Number crunching :
Finally getting new tasks only seconds after running out. May not be worth the hassle.
(Message 69593)
Posted 11 Mar 2020 by eiernacken1983 Post: I built that "mod" with Visual Studio 2013. I am not sure what version the official release was built with. That "100" DLL might be 2010 version. Berkeley has a problem maintain compatibility with Linux and after 2013 Microsoft made so many changes that Berkeley gave up on using "the latest and greatest". Just my opinion, worth 2c. But I know for a fact that VS2013 was the last version of Visual Studio compatible with BOINC. My strange combination of ambition (ambitios about good progress of the Project which made me updating the Project manually every hour to skip 10 minute idle time) and laziness (too lazy to follow your instructions) makes me answering with a delay of almost 4 weeks. But I am not answering to ask for further support but just to say thank you because …………. it finally works. There were some problems: In the beginning I misunderstood your instructions and thought I had to download the latest Version of VS runtimes. I was lucky beacause by accident I installed VS 2013 before I installed VS 2015 - 2019 on my first machine. After installing and replacing boinc.exe with your version it worked instantly. On my second machine I just installed VS 2015 - 2019 and it did not work. It only took me 2 minutes to recognize what was different on the first device. So I installed VS 2013, too. Again, it worked instantly, which is kind of prove that VS 2013 is required. I am kind of relieved now that the manual actualization each hour is over now. I hope your kid enjoys beeing in Germany. VAT is generally 19 % but only 7 % for food and other basic stuff (books, drugs/medicine and hundreds of exceptions). Dried Beef is not popular here, so there is no supply. THANK YOU AGAIN for your support! Summary for others who want to try the Workaround and have the same Problem like me: If BOINC cannot connect to client after replacing original boinc.exe with the modified boinc.exe, install VS 2013 (but not the version 2015 to 2019 (available on https://www.techspot.com/downloads/6776-visual-c-redistributable-package.html)). |
5)
Message boards :
Number crunching :
Finally getting new tasks only seconds after running out. May not be worth the hassle.
(Message 69542)
Posted 17 Feb 2020 by eiernacken1983 Post:
Thank you for your long answer :-) I followed your instructions. Here are my results :-) Your assumptions 1. to 4. are right (exception: german system, so c:\program files\boinc is c:\programme\boinc on my system; but the relative location matches your assumptions) So BOINC not running, (double checked it in task manager) I went to the command promt as administrator c:\programme\BOINC>.\boinc.exe --version --> I got a german error message stating "execution of the code can not be continued because MSCR120.dll was not found. Problem migth be solved be reinstalling the program" So obviously your boinc.exe needs MSVCR120.dll. My system only has MSVCR100.dll (installation was in Dec 2019) c:\programme\BOINC>.\boinccmd.exe --version --> built from BOINC 7.14.2 (like you already stated) c:\programme\BOINC>.\boinc_orig.exe --version --> 7.14.2 c:\programme\Boinc>boinccmd --quit --> can't connect to local host (like you already stated) c:\programme\Boinc>boinccmd --status --> can't connect to local host (like you already stated) So there is a problem with the MSVCR120.dll which is MSVCR100.dll on my system. |
6)
Message boards :
Number crunching :
Finally getting new tasks only seconds after running out. May not be worth the hassle.
(Message 69535)
Posted 13 Feb 2020 by eiernacken1983 Post: I did all of this and when i try to run my boinc manager after replacing the original Boinc executable the boinc manager launches but can not connect to the client. As your little fix sounded nice I tried to apply it. Unfortunately it didn't work on my two computers. What did I do: 1. Downloaded the boinc.exe via the link you provided earlier 2. Shutdown of boin and boinc mgr 3. Renamed boinc.exe in boinc_old.exe in the original boinc folder 4. Copied your boinc.exe from step 1 to the exact same folder 5. started boinc manager Result: exact same outcome like some posts above: boincmanager was not able to connect to the client. So i made sure no other copies of boinc were running. I even deacivated boinc in the autostart menu and restarted the pc. So boinc was not running at all. I repeated steps 3 to 5. Result: no connection to client When I change back original boinc.exe everything works fine (except the issue with getting new tasks instantly). So is there a thing that I did obviously wrong? Did I take an old version of boinc.exe or additionly do I have to edit some of the config files in order to get your fix working? Thank you in advance for any answers! |
©2024 Astroinformatics Group