Posts by Jipsu

1) Message boards : Number crunching : Tasks end prematurely. (Message 55282) Posted 25 Aug 2008 by Jipsu Post: I have noticed this too. Mini is running normally and graphics show that it has produced some decoys, then if I restart my computer it will report the task as completed and only 1 decoy or validate error. Strange. I just shouldn't reboot the computer I quess. :D This is the latest task Validate error.
2) Message boards : Number crunching : trouble getting new work units (Message 55146) Posted 17 Aug 2008 by Jipsu Post: Well there is some work available, but not nearly enough... Last time one of my computers got two WUs was about 2 hours ago.
3) Message boards : Number crunching : Post your Beta 5.98 Error 161 items here for the mods (Message 54211) Posted 6 Jul 2008 by Jipsu Post: It's sunday and I'm pretty sure they are already aware of the problem just not saying anything like always. Which sure as hell is not good for the whole rosetta project, but that's just my opinion. :P Personally I have nothing to add, only seen one -161 error lately and it was on ralph.
4) Message boards : Number crunching : Problems with version 5.96 (Message 53906) Posted 22 Jun 2008 by Jipsu Post: This one was stuck on my Gentoo Linux-2.6.24-gentoo-r7, it finished after 2 restarts, but was marked invalid. It also has an interesting stderr. <core_client_version>5.10.45</core_client_version> <![CDATA[ <stderr_txt> Graphics are disabled due to configuration... # cpu_run_time_pref: 86400 # random seed: 3053615 ====================================================== DONE :: 1 starting structures 85344.8 cpu seconds This process generated 22 decoys from 22 attempts ====================================================== BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down... called boinc_finish * glibc detected * free(): invalid next size (normal): 0x0959cfb8 * SIGABRT: abort called Stack trace (18 frames): [0x8e1b49b] [0x8e15d8c] [0xb7f97420] [0x8e870f4] [0x8e9c05f] [0x8ea10c5] [0x8ea13a3] [0x8e71d51] [0x8e73779] [0x87cb085] [0x8e8763f] [0x8e179ac] [0x8e17ab7] [0x8628fd6] [0x8768a2a] [0x8768b4a] [0x8e80034] [0x8048111] Exiting... Graphics are disabled due to configuration... # cpu_run_time_pref: 86400 ====================================================== DONE :: 1 starting structures 86247.3 cpu seconds This process generated 23 decoys from 23 attempts ====================================================== BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down... called boinc_finish * glibc detected * free(): invalid next size (normal): 0x0959d070 * SIGABRT: abort called Stack trace (18 frames): [0x8e1b49b] [0x8e15d8c] [0xb7fa7420] [0x8e870f4] [0x8e9c05f] [0x8ea10c5] [0x8ea13a3] [0x8e71d51] [0x8e73779] [0x87cb085] [0x8e8763f] [0x8e179ac] [0x8e17ab7] [0x8628fd6] [0x8768a2a] [0x8768b4a] [0x8e80034] [0x8048111] Exiting... Graphics are disabled due to configuration... # cpu_run_time_pref: 86400 WARNING! attempt to gzip file ./xxd010.out failed: file does not exist. ====================================================== DONE :: 1 starting structures 83399.6 cpu seconds This process generated 23 decoys from 23 attempts ====================================================== BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down... called boinc_finish </stderr_txt> ]]> http://boinc.bakerlab.org/result.php?resultid=172011426
5) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53461) Posted 30 May 2008 by Jipsu Post: I don't know if this is an error or bug, but The application is crunching MUCH slower than the estimated time. The estimated time is just over 3 hours, but right now the two units that are being worked on are at 8 hours, and only 33 and 35% done. Since I have a 7 day queue set up, I now have about 70 units waiting to be crunched, all of them with a deadline of 9 days from now, meaning that about 50 will be aborted... And since there has been a lot of mentions on the topic of the graphics, I figured I would mention that my graphics button is completely grayed out. Is it one of the these h00x tasks? h003__BOINC_ABRELAXt397__IGNORE_THE_REST-S25-10-S3-7--h003_-_3578_594_0 Took 18 hours to complete one decoy. <core_client_version>5.10.45</core_client_version> <![CDATA[ <stderr_txt> # cpu_run_time_pref: 86400 # cpu_run_time_pref: 86400 # cpu_run_time_pref: 86400 ====================================================== DONE :: 1 starting structures 65543.7 cpu seconds This process generated 1 decoys from 1 attempts ====================================================== BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down... called boinc_finish </stderr_txt> ]]> And don't worry if some of the WUs will be aborted, they will be assigned to other users. Just let it crunch! :)
6) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53434) Posted 29 May 2008 by Jipsu Post: When the screensaver starts for app 1.25 my screen just goes blank, the tasks complete fine if i wiggle my mouse the desktop comes back fine. i am using boinc 5.10.45 the other apps 5.96 display the graphics just fine Speedy minirosetta doesn't have proper graphics yet. You could say that the graphics are still in beta stage, and I remember reading that they are looking into that issue you have. I personally wouldn't even want to have minirosetta as a screen saver, at current state I think it's ugly. ;)
7) Message boards : Number crunching : minirosetta v1.25 bug thread (Message 53410) Posted 28 May 2008 by Jipsu Post: Hi everyone! It looks that everything is OK on my home PC with minirisetta 1.25, but... Sometimes computations for a WU finished before the end of target CPU run time. I.e. target run time is 12 hours, but computation may take 6 or 7 hours. Results are sending to server, I receive my credits, but is such short run time ok? It's ok, it's because application can't complete another model with the time it has remaining. For example if computation of one model takes 7 hours then minirosetta thinks that second model would also need 7 hours, which exceeds your runtime preference by 2 hours so it submits the result(s) it has completed so far and requests another WU. At least that's how I understand it, please correct me if I'm wrong.
8) Message boards : Number crunching : minirosetta 1.19 no Graphic (Message 53195) Posted 20 May 2008 by Jipsu Post: ive got a black screen, with a wireframe outline of the molecule. there is no option to change it to a ball type look or the other style like in 5.96 there are no other boxes showing the accepted energy or the overall energy plot. That's how it is supposed to look at the moment. I remember reading that the goal is to get same graphics to minirosetta as rosetta beta, but at the moment there is need to focus on more serious problems with the software.
9) Message boards : Number crunching : minirosetta v1.19 bug thread (Message 53072) Posted 15 May 2008 by Jipsu Post: I think the out of memory error is corrected already in minirosetta v1.2 which is going thru testing at ralph at the moment. 24h minorosetta v1.2 tasks are taking around 150M of memory and the out of memory error in minirosetta v1.19 seems to exist only in windows version of the application. Just throwing my thoughts around, but I think it's pointless to post out of memory errors since the problem is already fixed in v1.2.
10) Message boards : Number crunching : minirosetta v1.19 bug thread (Message 53004) Posted 12 May 2008 by Jipsu Post: Had three WUs fail because they exceeded the 2GB memory limit. WU1 WU2 WU3 For some reason this seems to be a problem with windown version of minirosetta. On my linux server the memory usage peak seems to be around 150MB and both computers have same runtime prefences.