1)
Message boards :
Number crunching :
Only 20 credits for 25,000 seconds
(Message 75847)
Posted 18 Jul 2013 by TechGuru Post: I take it no one else has any insight into what the above bold phrase is referring to correct? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? |
2)
Message boards :
Number crunching :
Only 20 credits for 25,000 seconds
(Message 75840)
Posted 15 Jul 2013 by TechGuru Post: I have had 2 of them lately, more than 25000 seconds for 20 credits. I noted the amount of requests for investigation into various bugs with crediting. Which is merely bragging rights for most anyway. I guess what I was trying to get across was that the science is well worth the effort. It would be a nice idea to get more then just communication from the project team. They have ton's of people with coding knowledge contributing to their project I would assume. If they are lacking in hardware I'm sure there is a good reason for it. Server pricing can range widely depending on what you wish them to do. 20 grand or more, which is why a lot of companies lease the server instead of buying it. Perhaps a meter on the home page listing a donation meter towards upgrading said hardware to rule out these problems. Since they are a non profit organization I would imagine it is in their best interests to run some of the equipment until it does die. In the IT world if it's not broken don't fix it. Mainly because of the total cost of ownership tends to go up and the equipment will breakdown more rapidly in some cases. Which means more breakdowns more often. You seem to have some insight TJ into what servers they are using along with coding I assume from your previous statements. Could you prey tell me what they are using that is so obviously outdated? Perhaps someone might be able to offer some support free of charge from the community. Also since we are in the right section for this. I noticed this on one of my WU's after it completed. <core_client_version>7.0.64</core_client_version> <![CDATA[ <stderr_txt> [2013- 7-10 15:49: 4:] :: BOINC:: Initializing ... ok. [2013- 7-10 15:49: 4:] :: 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. 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_rev54943.zip Unpacking WU data ... Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/fold_and_dock_frxtrimer2_dock2_10135_data.zip Setting database description ... Setting up checkpointing ... Setting up graphics native ... BOINC:: Worker startup. Starting watchdog... Watchdog active. # cpu_run_time_pref: 86400 hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? hey is this the right thing to be doing??? ====================================================== DONE :: 99 starting structures 13359.7 cpu seconds This process generated 99 decoys from 99 attempts ====================================================== BOINC :: WS_max 4.55877e+008 BOINC :: Watchdog shutting down... BOINC :: BOINC support services shutting down cleanly ... called boinc_finish </stderr_txt> ]]> |
3)
Message boards :
Number crunching :
Only 20 credits for 25,000 seconds
(Message 75836)
Posted 13 Jul 2013 by TechGuru Post: I have had 2 of them lately, more than 25000 seconds for 20 credits. They will get it fixed, it is imperative to the science circles to be precise. I'm sure they are working as quickly and as diligently as possible to correct issues with their coding or incompatibilities problems. Rosetta will always have 100% of my cores. The breakthrough's in disease's alone, make up for waiting for them to work out some of their kinks. I don't abort even if I suspect a WU has failed. If anything so they can at least have a chance to try an extrapolate as much data as possible from the failed units so hopefully they are able to figure out what went wrong in the first place faster. Stay positive, you wouldn't here in the first place if you didn't think it was worth while research and everything you donate whether credited or not helps the project. That being said provide as much information as possible to help solve the issue. Such as Client versions for Boinc and O/S system for the PC MAC or Linux system that you are operating. Cheers |
©2024 University of Washington
https://www.bakerlab.org