Posts by Daedalus

1) Message boards : Number crunching : New kind of app on Ralph (Message 101989) Posted 1 Jun 2021 by Daedalus Post: I haven't changed my cc_config.xml yet but i don't receive python tasks anymore.
2) Message boards : Number crunching : New kind of app on Ralph (Message 101978) Posted 31 May 2021 by Daedalus Post: Thank you a lot ! Will do.
3) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 101975) Posted 31 May 2021 by Daedalus Post: Sorry to interrupt your rants but we are quite a lot having trouble with the new python project work units. Thread is here : https://boinc.bakerlab.org/rosetta/forum_thread.php?id=14448
4) Message boards : Number crunching : New kind of app on Ralph (Message 101974) Posted 31 May 2021 by Daedalus Post: Apparently, when i got one and another one is in waiting the CPU crunches one of the pythons ones and nothing else. Same here. I have a 12 cores AMD Ryzen and even if i stop all other wus, the system crunchs only 1 python. When i have one of these python jobs i can force rosetta to crunch classical WU's by cancelling all the pythons in the queue. Anyway it doesn't finish them all. I get a unmanageable VM message after several hours of my electricity wasted so i killed the tasks. Edit: the funny thing is i don't get -of course- those python VM jobs on another machine which has no virtualbox installed. So a radical solution to this problem could be to uninstall virtualbox. I won't.I use it.
5) Message boards : Number crunching : New kind of app on Ralph (Message 101967) Posted 31 May 2021 by Daedalus Post: Apparently, when i got one and another one is in waiting the CPU crunches one of the pythons ones and nothing else. If i let the current python one running but cancel all the other python ones BOINC picks up other rosetta 4.20 WU's to crunch. To me, this current state of affairs is inconvenient. My python WU is taking a lot of memory and disk space.
6) Message boards : Number crunching : Why are my 'Remaining' time estimates so far off? (Message 98338) Posted 25 Jul 2020 by Daedalus Post: I use a 4 hours target time and all the WU's show a time to completion of 8 hours. But they complete in 4 hours and half. Do you split time with other Boinc Projects? I used to. But it was too much of a hassle so my main rig works for folding now. None of my two computers are pure crunching boxes. I use them for common work. I used to even game on my main rig before the COVID crisis.
7) Message boards : Number crunching : Why are my 'Remaining' time estimates so far off? (Message 98215) Posted 18 Jul 2020 by Daedalus Post: I use a 4 hours target time and all the WU's show a time to completion of 8 hours. But they complete in 4 hours and half.
8) Message boards : Number crunching : No decoys on an old Pentium 4. Just a curiosity: why? (Message 98009) Posted 11 Jul 2020 by Daedalus Post: It seems the same machine is now running Linux and returning results. I started long ago in 2008 on a pentium 4 @ 2,6 ghz and while the credit was much lower than nowadays, it had enough processing power to do something.
9) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 97785) Posted 28 Jun 2020 by Daedalus Post: It assumes what the server thinks is the time required, which in the case of Rosetta is the standard 8 hours. Unless your computer takes nothing like 8 hours to do a task, it should be correct from the beginning. Wild estimates happen in other projects, where work units can take vastly different times depending on processor power. Nope, you can choose the running time. I set mine to 4 hours or else i would have more tasks failing or being cancelled.
10) Message boards : Number crunching : Rosetta on Android 10 not working? (Message 97769) Posted 28 Jun 2020 by Daedalus Post: Same thing on an android 7 phone. And same problem with einstein@home.
11) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 97581) Posted 24 Jun 2020 by Daedalus Post: I have no idea as I've never used it, but would it help to set something in Boinc's "Daily Schedules" tab under Computing Preferences? I wonder what it would do. I don't know. It doesn't seem to forbid specific days. Just specific hours some days. In the meantime, i will try to reduce further the cache to see if it helps well enough. :)
12) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 97577) Posted 24 Jun 2020 by Daedalus Post: Have you tried setting No new tasks about the time any more tasks downloaded will not finish in time? Yes but it doesn't work out well enough. Reducing the cache helped better but i still have to cancel some. It doesn't help that i sometimes stop to crunch for Folding. :)
13) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 97573) Posted 24 Jun 2020 by Daedalus Post: The BOINC manager is not that good at predicting my compute time and anyway i am not home on weekends so i always have some tasks due to finish a day my computer will be off. So at the end of the week i have to cancel a batch. Systematically. I understand they want their results fast but i cannot always provide.
14) Message boards : Number crunching : no new tasks? (Message 97528) Posted 23 Jun 2020 by Daedalus Post: i don't know if it is related but BOINC on my android smartphone has been unable to communicate with r@h for days. Soon after Einstein@home. i doubt it is related but no warning whatsoever. Edit: That said i crunch for folding@home which is far from being useless. I used to alternate between projects.
15) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 95588) Posted 30 Apr 2020 by Daedalus Post: Yes, save a few tasks cancelled by the server, all my tasks computed normally. So i wil ignore the progression as reported by the BOINC manager. :)
16) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 95562) Posted 29 Apr 2020 by Daedalus Post: Ok, i may have an optimistic explanation of this: The completion percentages shown in the BOINC manager might be wildly innacurate. I had "very slow" WU's and "less slow" WU's. I killed a lot of very slow ones and let the less slow run their course. Surprise: the less slow tasks, announced to take 6 hours or more have stopped at around 4 hours and half as promised. They were at 85 -90 % completion and they suddently jumped to 100% With the correct run time. Let's hope it will be the same with the "very slow" ones. I will only know tomorrow.
17) Message boards : Number crunching : Problems and Technical Issues with Rosetta@home (Message 95558) Posted 29 Apr 2020 by Daedalus Post: I get an awful lot of tasks that complete very slowly. I set my runtime goal to 4 hours. Most rotten tasks advance at exactly 6.480 % an hour. I kill them mercilessly. But i have to babysit rosetta and check all my tasks one by one as soon as they start crunching. This is a waste of my time and my electricity. Should i dump my whole queue ? P.S. And previously i was getting a lot of tasks with a completion time of 9 hours. But you could detect them and dump them before they started so less effort was needed.
18) Message boards : Number crunching : Limit number of download workunits (Message 91962) Posted 14 Mar 2020 by Daedalus Post: You may also verify in your options, the "preferences" menu. You can set a minimal amount of downloaded work. In the sense it will download at least work for the set time. If the value is too high, it will always download too much work. Setting a lower value is not a guarantee it will download little work though.
19) Message boards : Number crunching : Abnormally high run times (Message 91728) Posted 17 Feb 2020 by Daedalus Post: Thank you for your very quick answer. :) I think i understand the problem, but my computer is not a dump. Edit: I don't know if that still happens but in the pasts i had had WU's running 12 hours instead of 4.
20) Message boards : Number crunching : Abnormally high run times (Message 91726) Posted 17 Feb 2020 by Daedalus Post: Hello, I sometimes catch tasks which run for an unusually longer time. My run time is set to four hours and those show low completion rates even after longer hours. I kill them as soon as i see them. Does anyone else have the same problem. Is there an explanation ? Edit: They also guzzle huge amounts of RAM but sounds like some bug.

Next 20