Posts by Hefto99

1) Message boards : Number crunching : minirosetta 2.02 (Message 64470) Posted 13 Dec 2009 by Hefto99 Post: Task id: 303891966 Name: broker_idealclose_kic10_hb_t297__IGNORE_THE_REST_16447_56_0 Error: ====== BOINC:: Worker startup. Starting watchdog... Watchdog active. # cpu_run_time_pref: 28800 CLOSING with IDEALIZATION CLOSING with IDEALIZATION CLOSING with IDEALIZATION SIGSEGV: segmentation violation Stack trace (16 frames): [0x96a99e3] [0x96d38b8] [0xffffe400] [0x8eb6f8e] [0x8e5aea3] [0x8fe343f] [0x8fe8232] [0x85dcc61] [0x85df5d9] [0x8127d5e] [0x8129041] [0x86986f0] [0x8240424] [0x80496a9] [0x972f8ac] [0x8048121] Exiting... </stderr_txt> ]]>
2) Message boards : Number crunching : Minirosetta 2.00 (Message 64033) Posted 13 Nov 2009 by Hefto99 Post: I have got several errors too (on 64-bit Linux): =========== <core_client_version>6.2.15</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> [2009-11-13 13: 7:12:] :: BOINC:: Initializing ... ok. [2009-11-13 13: 7:12:] :: BOINC :: boinc_init() BOINC:: Setting up shared resources ... ok. BOINC:: Setting up semaphores ... ok. BOINC:: Updating status ... ok. BOINC:: Registering timer callback... ok. BOINC:: Worker initialized successfully. Registering options.. Registered extra options. Initializing broker options ... Registered extra options. Initializing core... Initializing options.... ok Options::initialize() Options::adding_options() Options::initialize() Check specs. Options::initialize() End reached Loaded options.... ok Processed options.... ok Initializing random generators... ok Initialization complete. Setting WU description ... Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_rev33769.zip Setting database description ... Setting up checkpointing ... Setting up graphics native ... BOINC:: Worker startup. Starting watchdog... Watchdog active. # cpu_run_time_pref: 28800 * glibc detected * corrupted double-linked list: 0x11b99940 * SIGABRT: abort called Stack trace (23 frames): [0x9667f13] ============ <core_client_version>6.2.15</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> [2009-11-13 13:10: 5:] :: BOINC:: Initializing ... ok. [2009-11-13 13:10: 5:] :: BOINC :: boinc_init() BOINC:: Setting up shared resources ... ok. BOINC:: Setting up semaphores ... ok. BOINC:: Updating status ... ok. BOINC:: Registering timer callback... ok. BOINC:: Worker initialized successfully. Registering options.. Registered extra options. Initializing broker options ... Registered extra options. Initializing core... Initializing options.... ok Options::initialize() Options::adding_options() Options::initialize() Check specs. Options::initialize() End reached Loaded options.... ok Processed options.... ok Initializing random generators... ok Initialization complete. Setting WU description ... Unpacking zip data: ../../projects/boinc.bakerlab.org_rosetta/minirosetta_database_rev33769.zip Setting database description ... Setting up checkpointing ... Setting up graphics native ... BOINC:: Worker startup. Starting watchdog... Watchdog active. # cpu_run_time_pref: 28800 * glibc detected * free(): invalid next size (normal): 0x11212198 * SIGABRT: abort called Stack trace (21 frames): [0x9667f13]
3) Message boards : Number crunching : Is this for real??? (Message 17298) Posted 29 May 2006 by Hefto99 Post: Hi DocMaboul, I don't say that BS is guilty. It is an excellent piece of software, thank you very much again for it's creation. But - as you stated, switching calibration for Rosetta to ON inflates benchmarks. Unfortunatelly, there are many people who abuse this situation... I just point this out as a possible explanation of high credits claimed by the top computers. No offense to you and BS was meant :-) .
4) Message boards : Number crunching : Is this for real??? (Message 17287) Posted 29 May 2006 by Hefto99 Post: I don't think its Boincstudio. I'm crunching Rosetta with it now and it only claimed 78 for 14000sec of work. I think thats inline... If you don't use credit calibration, you report normal benchmarks. Credit calibration inflates benchmarks, therefore those people claim too much. Unfortunatelly it works in this way, although Rosetta doesn't have optimized application and benchmarks should not be increased even calibration is activated... :-(
5) Message boards : Number crunching : Is this for real??? (Message 17197) Posted 27 May 2006 by Hefto99 Post: It seems many of them are using Boinc Studio with credit calibration set to ON for Rosetta... This shall be not allowed. All pleasure for compete is gone :-(