Posts by rlpm

1) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92943) Posted 1 Apr 2020 by rlpm Post: Yep, good call. I'm also wondering if anyone on this thread has access to the code or know anyone who does and can hunt down this bug.
2) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92938) Posted 1 Apr 2020 by rlpm Post: Signal 11 is SEGV (segmentation fault). This is typically due to a programming bug. Per stderr, looks like a few double frees as well, perhaps related. Anyone know how to report this to the boffins that write the software? Moderators?
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92573) Posted 30 Mar 2020 by rlpm Post: Note: Though subscribed to this thread, I received no notification of bormolino's post. Check your community prefs from your main account page.
4) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92490) Posted 28 Mar 2020 by rlpm Post: The binaries should check that there's enough memory for the WU, both at process start time, and checking results of malloc, etc. at run time. Since the process on your computer hit a segfault, it may have been due to a memory allocation failing but the software not checking the result of the allocation. There must be some checking in the 32-bit (for linux) version of the Rosetta & Rosetta Mini binaries, since I've encountered this error message on an older box with only 256MB of memory: working set size > client RAM limit: 180.00MB > 179.51MB (But it would be nice to have the check happen ahead of time -- before sending the WU to the computer.)
5) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92464) Posted 28 Mar 2020 by rlpm Post: <message> process got signal 11 </message> The process is crashing. More info: SIGSEGV 11 Core Invalid memory reference The people with access to the code will have to look into it. I don't know whether there are any crash reports (stack traces, etc.) that you can pull to provide more information to them.
6) Message boards : Number crunching : Raspberry Pi4 (Message 92282) Posted 25 Mar 2020 by rlpm Post: Same question on Twitter, R@H account replied Yep, nice. Here's the tweet. I hope this includes a smaller memory footprint as well. I have five RPi Compute Module 3s arriving in a few days, and would love to dedicate them to R@h. After OS overhead, each of the 4 cores will have 240MB or so of RAM (assuming GPU will not be used).
7) Message boards : Number crunching : How to get only Rosetta mini ? (Message 92280) Posted 25 Mar 2020 by rlpm Post: I'm also interested in running mini only, as the non-mini WUs all seem to fail on my setup, for going over the RAM limit. See also this post. Looks like R@h needs 1GB of RAM per CPU core, with no difference between mini Rosetta and (normal) Rosetta binaries. So I'll have to repurpose this host. See here for more info.
8) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92279) Posted 25 Mar 2020 by rlpm Post: Thanks Mod.Sense. It would be nice if BOINC automatically failed early, perhaps even at project attachment, if the host doesn't meet the minimum requirements for any app (RAM, disk, instruction set, OS). I already have my old 1st gen RasPis crunching on TN-Grid (gene sequencing) via BOINC, so I'll do the same with this AppleTV.
9) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92247) Posted 25 Mar 2020 by rlpm Post: Looks like the same is happening for mini tasks, e.g. task 1132535295: working set size > client RAM limit: 170.39MB > 167.55MB
10) Message boards : Number crunching : How to get only Rosetta mini ? (Message 92244) Posted 25 Mar 2020 by rlpm Post: I'm also interested in running mini only, as the non-mini WUs all seem to fail on my setup, for going over the RAM limit. See also this post.
11) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 92241) Posted 24 Mar 2020 by rlpm Post: All WUs for Rosetta v4.07 i686-pc-linux-gnu on my 1st gen AppleTV running linux (OSMC with all GUI etc. disabled) are failing for going over the RAM limit. See here. E.g.: working set size > client RAM limit: 167.87MB > 167.55MB Is there something wrong with the working set size matching to the amount of available RAM? Or can I limit to the Rosetta Mini application only?
12) Message boards : Number crunching : Raspberry Pi4 (Message 92239) Posted 24 Mar 2020 by rlpm Post: You can crunch on Tn-Grid Thanks! Seems to be working great on two RasPi A rev 2 and one RasPi B rev 2. Memory footprint is surprisingly small for the first tasks I received, under 40MB working set size.