Posts by gemini8

1) Message boards : Number crunching : how long can "long tasks" be? (Message 1916) Posted 21 Jan 2023 by gemini8 Post: I'm running another project that has tasks that are quite allergic to restarts, and I'm running SiDock on a Ubuntu 22 machine on which the Boinc Manager keeps crashing a second after being started, so I can't use it and instead rely on boinccmd which makes aborting tasks a PITA. Because of that I told my machine to stop asking for more SiDock long tasks. If I don't get anything else in the meantime I will have to wait until the SiDock long tasks are working properly. Thanks for reading.
2) Message boards : Number crunching : A challenge of December 2021 (Message 1410) Posted 26 Dec 2021 by gemini8 Post: We tried to inform active participants through various channels and at the moment we see that most of the potentially unsuccessful tasks have already been interrupted or failed. The number of tasks in progress that cannot be affected by this problem is many times larger and if participants start killing tasks without proper attention, the total losses can be much greater. You could abort the workunits with issues on the server side.
3) Message boards : Number crunching : Work-units aren't using percentage of CPU-time (Message 918) Posted 15 May 2021 by gemini8 Post: Hi hoarfrost. The machine I want to keep quiet is an oldish Core2Duo. Just using one of the two cores doesn't help my case. Only reducing the overall workload by cutting off the percentage at around 20% to 30% is keeping the machine quiet. On my newer MacBook Air it is enough to switch off the turbo; while doing four SiDock tasks it keeps being noiseless.
4) Message boards : Number crunching : Work-units aren't using percentage of CPU-time (Message 915) Posted 14 May 2021 by gemini8 Post: Hi hoarfrost. Reducing cores is no problem.
5) Message boards : Number crunching : Work-units aren't using percentage of CPU-time (Message 909) Posted 12 May 2021 by gemini8 Post: Dear SiDock team. The above-mentioned issue is still true. Are you planning to do anything about it? Thanks for considering this!
6) Message boards : News : Half a year, the BOINC Workshop and a move to the new server (Message 866) Posted 3 May 2021 by gemini8 Post: If you want only OPNG wus it easy. in your wcg device profile (home, woek, school) select only OpenPandemics. Then below "processor Usage" set " Allow research to run on my CPU?" to "NO" in " Graphics Card Usage" enable your GPU by setting "YES" near your GPU type Save the profile Well, this might prevent you from participating in Javelin Throw on WCG MIPS. And now for something completely different, namely getting back on-topic: Congratulations on your new server! It might help you to keep the project flowing smoothly even during the Pentathlon. I really hope your research gets an additional bump through it. I'm looking forward to further participating in this project!
7) Questions and Answers : Macintosh : Work units for Mac (Message 780) Posted 13 Apr 2021 by gemini8 Post: @Gemini8/Jens is there a chance your Lion is 32 bit instead of 64 bit? The SiDock app appears to need 64 bit. Thanks for your input. Seems to clear up, not solve this issue. The kernel and Boinc run in 32-bit, the rest in 64-bit. Can't change anything about the kernel, but I'd think it should be possible to run Boinc in 64-bit. Will have a look at all those config xml-files.
8) Questions and Answers : Macintosh : Work units for Mac (Message 334) Posted 23 Dec 2020 by gemini8 Post: No luck with Lion: https://www.sidock.si/sidock/results.php?hostid=1095
9) Questions and Answers : Macintosh : Work units for Mac (Message 312) Posted 20 Dec 2020 by gemini8 Post: Will try RxDock with my MacBook Pro as soon as it finishes old work. RxDock is running on El Capitan. Thanks again!
10) Questions and Answers : Macintosh : Work units for Mac (Message 311) Posted 20 Dec 2020 by gemini8 Post: Thanks again for your work! Unfortunately I'll not be able to test on Lion during the next days while staying away from home. My MacBook is only used for testing (and important challenges), so I can't control it via BAM! for now. Will try RxDock with my MacBook Pro as soon as it finishes old work.
11) Questions and Answers : Macintosh : Work units for Mac (Message 296) Posted 19 Dec 2020 by gemini8 Post: Hello. Thanks for your work! I'm successfully running SiDock@home on a MacBook Pro running El Capitan. I also tried SiDock@home on a MacBook running Lion. Unfortunately the tasks error out on the latter. <core_client_version>7.6.34</core_client_version> <![CDATA[ <message> process exited with code 195 (0xc3, -61) </message> <stderr_txt> 09:16:53 (289): wrapper (7.5.26013): starting 09:16:53 (289): wrapper: running worker () worker: line 14: 292 Segmentation fault: 11 DYLD_FALLBACK_LIBRARY_PATH="$CMDOCK_ROOT/build" "$CMDOCK_ROOT/build/cmdock" -r target.prm -p "$CMDOCK_ROOT/data/scripts/dock.prm" -f htvs.ptc -i ligands.sdf -o docking_out > docking_log 09:16:54 (289): worker exited; CPU time 0.010226 09:16:54 (289): app exit status: 0x8b00 09:16:54 (289): called boinc_finish(195) </stderr_txt> ]]> Might this be an issue with using Lion?
12) Message boards : Number crunching : Work-units aren't using percentage of CPU-time (Message 295) Posted 19 Dec 2020 by gemini8 Post: Dear SiDock@home team. First of all: Congrats of finishing the beta phase and starting your original project! I'm running SiDock@home on a MacBook Pro and and limit CPU-use to reduce heat, and thus fan noise. Unfortunately SiDock@home work-units are using up to 100% of CPU-time although the preferences tell them to use no more than 20%. I haven't noticed the beta work doing this, but maybe I just didn't perceive it. Please have a look into this issue. Thanks a lot!