Posts by Warped

41) Message boards : Number crunching : Facebook App for milestones posting (Message 63115) Posted 1 Sep 2009 by Warped Post: Thanks - that's great (nice and prominent). You're a real wizard. The work done over at PrimeGrid (I imagine with raw data from Rytis) is also much appreciated.
42) Message boards : Number crunching : Facebook App for milestones posting (Message 63113) Posted 1 Sep 2009 by Warped Post: Hi Bok Good to see you here as well. I've followed the instructions to the tee and everything seemed OK except I now do not see any info on my wall or boxes. Could it be that I have not passed a milestone since enabling the app?
43) Message boards : Number crunching : Discussion on increasing the default run time (Message 63068) Posted 28 Aug 2009 by Warped Post: I live in a bandwidth-impoverished part of the world, with high prices and low speed. Consequently, I have selected 16 hours run time. However, I find this thread as well as the others discussing long-running models to be of little interest when I have work units running for about 4 hours. Is the preferred run time really applied? I have noticed that on my faster machine, the limit of 99 decoys is usually reached before the 12-hour expected runtime I've requested. You might want to check the report visible on the Rosetta@home of how well the workunit succeeded to see if your workunits also often stop at the 99 decoys limit instead of near the requested run time. The workunits ending before the selected run-time get to a stop at 100 decoys, whereas the one recent workunit which made it to the selected 16 hours stopped at 88 decoys. Is there anything I can do to adjust this or is it a lucky-dip?
44) Message boards : Number crunching : Discussion on increasing the default run time (Message 63031) Posted 24 Aug 2009 by Warped Post: I live in a bandwidth-impoverished part of the world, with high prices and low speed. Consequently, I have selected 16 hours run time. However, I find this thread as well as the others discussing long-running models to be of little interest when I have work units running for about 4 hours. Is the preferred run time really applied?
45) Message boards : Number crunching : SERVER PROBLEMS. (Message 62592) Posted 29 Jul 2009 by Warped Post: I am seeing the same problems. One of my machines was totally empty - I suspended all other projects (for the fifth time). This time I had extra time to stick around and after about four hours it picked up a few. My other machine has one uploading (not successful after two tries) and has one which it finally downloaded this morning. I have my prefs set for 6 days of work and it gave me one work unit which it states has a 4 hour time to completion. On this machine with 200 to this and 100 to just one other project - I would expect it to be finished in 6 hours - max. Try increasing your target CPU run time in your preferences. This reduces the amount of server contact required. I have mine set to 16 hours and I seem to be able to get work. Maybe there are more of the longer workunits available.
46) Message boards : Number crunching : SERVER PROBLEMS. (Message 62438) Posted 26 Jul 2009 by Warped Post: Hi. I'm getting this type of message on all rigs. Sun 26 Jul 2009 14:59:09 EST\|rosetta@home\|Scheduler request failed: Failed sending data to the peer Sun 26 Jul 2009 14:59:10 EST\|\|Internet access OK - project servers may be temporarily down. Sun 26 Jul 2009 14:59:18 EST\|rosetta@home\|Temporarily failed upload of lr10_seq_score12_rlbd_1npu_IGNORE_THE_REST_DECOY_13841_2574_0_0: HTTP error Sun 26 Jul 2009 14:59:18 EST\|rosetta@home\|Temporarily failed upload of lr8_seq_score12_ss5.0_rlbd_1l6p_IGNORE_THE_REST_DECOY_14281_2574_0_0: HTTP error Servers are all green, but is something broken! I saw one rig trying to D/L a new app, could that be what's jamming up the works. I'm getting timeouts as well.
47) Message boards : Number crunching : CPU usage (Message 62124) Posted 8 Jul 2009 by Warped Post: This is a standard message because there were people that said they never heard a newer version was available. Use the version you like, if the project you like requires a higher version it will be made known on their boards that you will have to upgrade. I don't know why they threw out 5.10.45. As far as I'm concerned it was the most stable version available. This CUDA rubbish is has really messed up BOINC IMHO. Apart from all sorts of problems with the performance whenever I've tried to use it, the comparative statistics are now meaningless as well.
48) Message boards : Number crunching : Problems with version 5.96 (Message 53748) Posted 17 Jun 2008 by Warped Post: 2008/06/17 19:13:08\|rosetta@home\|Reason: Unrecoverable error for result t405__CASP8_JUMPAB_RES81to192_SAVE_ALL_OUT_BARCODE__3758_22480_0 ( - exit code 1073807364 (0x40010004)) I'm out of here - it seems that more than half of my WU's have bombed out. The downloads are quite big as well, using up valuable bandwidth.

Previous 20