Yifan Song Forum moderator Project administrator Project developer Project scientist Joined: May 26 09 Posts: 41 ID: 318024 Credit: 0 RAC: 0
minirosetta 2.00 is now up.
The energy function optimization we've been working on for the last few month are now in.
This version also fixes some stability issues brought in by 1.98.
PPL has a point. Looks like both Linux versions are more then 4x larger then prior releases.
If this is the case I will wait until the size decreases again before I return to this project.
____________
Have a crunching good day!! Live in NZ y not join Smile City?
ID: 63972 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
speedy, I should clarify, we are talking about the download size of the new program version. It most likely is just due to a compiler parameter that incorporated some debug capabilities or something. So, it does not necessarily effect how much memory is required to run.
The concern would just be if you have very limited bandwidth available to perform the initial download. Or perhaps if you have very limited disk space available to BOINC.
____________ Rosetta Moderator: Mod.Sense
Seems to work fine but the graphics lock up and need to be force quitted in activity monitor in OS X 10.6.1.
ID: 63975 | Rating: 0 | rate:
/
Michael G.R. Joined: Nov 11 05 Posts: 249 ID: 11128 Credit: 3,312,155 RAC: 1,653
Seems to work fine but the graphics lock up and need to be force quitted in activity monitor in OS X 10.6.1.
I'm on OS X 10.6.1 and the graphics are fine here (though I haven't left them running for very long -- did you experience a lock up after a long time?).
____________
Did the disk space requirements for this new version change? I'm getting:
09-Nov-2009 09:09:12 [rosetta@home] Message from server: No work sent
09-Nov-2009 09:09:12 [rosetta@home] Message from server: There was work but you don't have enough disk space allocated.
09-Nov-2009 09:09:12 [rosetta@home] Message from server: An additional 8 MB is needed.
Disk tab in BoincMgr only says 10.2 MB used by BOINC, even after resetting the project. How much space needs to be free to run the project?
Did the disk space requirements for this new version change? I'm getting:
09-Nov-2009 09:09:12 [rosetta@home] Message from server: No work sent
09-Nov-2009 09:09:12 [rosetta@home] Message from server: There was work but you don't have enough disk space allocated.
09-Nov-2009 09:09:12 [rosetta@home] Message from server: An additional 8 MB is needed.
Disk tab in BoincMgr only says 10.2 MB used by BOINC, even after resetting the project. How much space needs to be free to run the project?
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
DJStarfox if you have Linux boxes, see the discussion previously in this thread about how the size of the executable seems to have increased significantly in version 2.00.
____________ Rosetta Moderator: Mod.Sense
Can it be that this version delivers somewhat less performance?
I'm down 20% since the introduction of the 2.00 version.
http://tadah.mine.nu/graphs/flushHistoryGraph.php?tabel=subteamoffset&prefix=rah&naam=BaDu&team=[DPC]DeApen
The introduction was on the 6th my queue has 3 days of work, so you can see the preformance decrease since running 2.00
The graph is not showing RAC but daily points over the last 7 days generated bij a stats engine.
True, but when looking up your account at boincstats, I did not see such a drop.
____________
ID: 64009 | Rating: 0 | rate:
/
Yifan Song Forum moderator Project administrator Project developer Project scientist Joined: May 26 09 Posts: 41 ID: 318024 Credit: 0 RAC: 0
The large increase to the executable size could be due to the inclusion of a number of protocols that has been developed over the last 2 years. Those protocols were not able to compile with the boinc build until now.
There shouldn't be any difference in running the tasks though, the only difference is the time it takes to update.
ID: 64012 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
If this is the cause, then how did the Windows version get by without any noticeable increase in size?
____________ Rosetta Moderator: Mod.Sense
ID: 64019 | Rating: 0 | rate:
/
P . P . L . Joined: Aug 20 06 Posts: 365 ID: 105843 Credit: 361,915 RAC: 771
The large increase to the executable size could be due to the inclusion of a number of protocols that has been developed over the last 2 years. Those protocols were not able to compile with the boinc build until now.
There shouldn't be any difference in running the tasks though, the only difference is the time it takes to update.
Hi.
Does that mean that we Linux folk get to do more of the heavy lifting. ;) L.O.L.
____________
ID: 64023 | Rating: 0 | rate:
/
P . P . L . Joined: Aug 20 06 Posts: 365 ID: 105843 Credit: 361,915 RAC: 771
Hi. first error with mini 2.00. well sort of.
This is an odd one only ran for 3 min's, i don't know what happened.
Hi.
I got a lot of errors too :
lr5_dun08_it04_A_rlbd_4icb_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_15799_439_0
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
[2009-11-12 17:51:35:] :: BOINC:: Initializing ... ok.
[2009-11-12 17:51:35:] :: 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
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/yfsong_lr5_dun08_it04_A.zip
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/lr5_4icb.out.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
Fullatom mode ..
# cpu_run_time_pref: 86400
Fullatom mode ..
..
..
..
Fullatom mode ..
SIGSEGV: segmentation violation
Stack trace (27 frames):
[0x9667f13]
.
.
.
[0x8048121]
Exiting...
</stderr_txt>
]]>
And also :
lr5_dun08_it04_A_rlbd_1ugh_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_15799_445_0
<core_client_version>6.10.17</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
[2009-11-12 19:16:30:] :: BOINC:: Initializing ... ok.
[2009-11-12 19:16:30:] :: 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
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/yfsong_lr5_dun08_it04_A.zip
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/lr5_1wdv.out.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
Fullatom mode ..
# cpu_run_time_pref: 86400
Fullatom mode ..
Fullatom mode ..
Fullatom mode ..
*** glibc detected *** free(): invalid next size (fast): 0xef219138 ***
SIGABRT: abort called
Stack trace (30 frames):
[0x9667f13]
.
.
.
[0x8048121]
Exiting...
</stderr_txt>
]]>
Any idea why ?
And I got a lr5_dun08 blocked at 0.310% after 24h...I'm gonna cancel it I guess.
____________
My self hosted blog: www.freelydifferent.com
Learn how to easily self host a website, mail, and others services.
Had some 3gbm WUs bomb out after 100 seconds or so. This was with 32bit Linux. In some cases the other cruncher returned a successful result (with Windows).
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
I got linux 64b too.
I guess there is something wrong with our lib...?
My second laptop with Linux 64b as well, does not have any error calculation...
Do we have to install a particular lib ? Or what is wrong ?
Thanks
Everything needed downloads with the work unit. It appears some specific tasks are having trouble and that is what this thread is for, to collect the descriptions of those so they can be corrected in future releases.
____________ Rosetta Moderator: Mod.Sense
Okay thanks !
I let my second computer running these WUs.
____________
My self hosted blog: www.freelydifferent.com
Learn how to easily self host a website, mail, and others services.
mix_score13_C_rlbd_1ttz__IGNORE_THE_RESTlr13_DECOY_15917_345_1 task 296879164 gave a Validate Error on Mac OS X 10.6 after generating one decoy. "Too many error results" according to the Workunit log: it had been sent out once before with a similar result.
ERROR: res1 != res2
ERROR:: Exit from: ..\..\src\core\kinematics\FoldTree.cc line: 2342
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish
</stderr_txt>
]]>
____________
ID: 64089 | Rating: 0 | rate:
/
Telescope Adrian Joined: Nov 14 06 Posts: 8 ID: 129278 Credit: 280,612 RAC: 280
Anybody noticed a new "facility" with 2.00 yet ?
Run 2 jobs together ( AMD Athlon 64 X 2) and , after a while , one of the jobs goes idle meaning that the system idle process sits at 50% utilisation . Suspending Rosetta , then restarting it makes no difference to this behaviour.
I used to see this feature a while ( many months) ago , but it went away I think at about Version 1.97 .
Anybody noticed a new "facility" with 2.00 yet ?
Run 2 jobs together ( AMD Athlon 64 X 2) and , after a while , one of the jobs goes idle meaning that the system idle process sits at 50% utilisation . Suspending Rosetta , then restarting it makes no difference to this behaviour.
I used to see this feature a while ( many months) ago , but it went away I think at about Version 1.97 .
Has anyone else this yet ?
Best wishes
How much RAM do you have?
Edit: I figured it myself (2GB). I don't know what the problem could be... you could've given Rosetta too little available RAM in your setting, maybe?
____________
ID: 64092 | Rating: 0 | rate:
/
Telescope Adrian Joined: Nov 14 06 Posts: 8 ID: 129278 Credit: 280,612 RAC: 280
Anybody noticed a new "facility" with 2.00 yet ?
Run 2 jobs together ( AMD Athlon 64 X 2) and , after a while , one of the jobs goes idle meaning that the system idle process sits at 50% utilisation . Suspending Rosetta , then restarting it makes no difference to this behaviour.
I used to see this feature a while ( many months) ago , but it went away I think at about Version 1.97 .
Has anyone else this yet ?
Best wishes
How much RAM do you have?
Edit: I figured it myself (2GB). I don't know what the problem could be... you could've given Rosetta too little available RAM in your setting, maybe?
Hello there . It's not a problem of store availability since I allow BOINC to use 75% of my available real store when I'm running projects . ( Virtual storage systems don't work like you seem to think ! ) . On this machine I usually have other jobs from Rosetta and Spinhenge queuing to run , but when the Rosetta job goes " idle " , no other job starts up to take its engine time up , so its nothing to do with OCP time utilisation either .As I said earlier , this facility used to show itself earlier this year , but went away at about Rosetta 1.97 . The workunit seems just to sit waiting for something , but I know not what !
Regards
____________
ID: 64093 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
Adrian, Rosetta does not decide what work runs at what time, BOINC decides this. It does this based on your preferences. Since BOINC does not have a configuration setting called "real store", you haven't really told us much about your settings. Even if you were indicating memory, you didn't tells us if this was the setting for when the machine is in use, or when it is idle.
The main thing to check is... what does BOINC say the reason for not running it is? The task's status or the messages should indicate what's going on. Since you seem familiar with the Windows task manager, another idea would be to suspend the task that is active, and see if the other resumes running. And then look at how much memory it is using. Or easier yet, it should appear in the task list if you sort it alphabetically and show you how much memory it is using.
If it is consuming too much memory then that would be something Rosetta might be able to address.
Do you know which task name is causing you problems?
____________ Rosetta Moderator: Mod.Sense
ID: 64096 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
Notes for Project Team:
Looking at Adrian's task list, it looks like this one had a very long running model on the third decoy
threading_bong_promals_4_hb_t328__IGNORE_THE_REST_16074_67_0
http://boinc.bakerlab.org/rosetta/result.php?resultid=297460595
Target runtime 14,400, 3 decoys ran in 23,000. The first two must have been done within 9,600 or it would have ended the task before starting the third. So that means the third ran for at least 13,400, which is nearly 4 hours.
____________ Rosetta Moderator: Mod.Sense
ID: 64097 | Rating: 0 | rate:
/
Telescope Adrian Joined: Nov 14 06 Posts: 8 ID: 129278 Credit: 280,612 RAC: 280
Adrian, Rosetta does not decide what work runs at what time, BOINC decides this. It does this based on your preferences. Since BOINC does not have a configuration setting called "real store", you haven't really told us much about your settings. Even if you were indicating memory, you didn't tells us if this was the setting for when the machine is in use, or when it is idle.
The main thing to check is... what does BOINC say the reason for not running it is? The task's status or the messages should indicate what's going on. Since you seem familiar with the Windows task manager, another idea would be to suspend the task that is active, and see if the other resumes running. And then look at how much memory it is using. Or easier yet, it should appear in the task list if you sort it alphabetically and show you how much memory it is using.
If it is consuming too much memory then that would be something Rosetta might be able to address.
Do you know which task name is causing you problems?
Yes , I am aware that BOINC is what is loosely termed a High - Level Scheduler .
You seem to be expert at reading the bleeding obvious , there is no message from Boinc and I 've already checked all the obvious parameters that you've mentioned . Please be advised that I was a senior operating systems software engineer prior to my retirement , so I'm not one of the average computer illiterate cretins posting inane problems .
____________
ID: 64099 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
Adrian, I'm simply trying to understand what you've got set up there, and what you are expecting the behavior to be. Is Rosetta the only BOINC project with work on your machine? How many tasks do you have waiting to run? Has it begun each, run for about 30 seconds and then suspended it? Do you leave tasks in memory when suspended?
As a senior operating systems software engineer, you must realize that the questions I've asked are highly relevant, and that you've answered none of them. Not even the task name and how much memory it is using. So I am still unable to use your report to build any theories about specific tasks consuming excessive memory.
Doctors make the worst patients, and the ole "...it broke. I did everything and nothing worked" problem description certainly sounds familiar.
Since you speak English, and don't have to translate the displays for us, and you realize the how intricate the configuration of the system can be, please use the terms written on the screen and describe your situation. Otherwise none of us cretins are going to be able to help you.
____________ Rosetta Moderator: Mod.Sense
So we're up to v2.00 on the Mini. I'm hoping that we're building upon a good foundation and cleaning up problems as we go... not just patching up this problem and that or finding work-arounds. I am very satisfied with the main bulk of the project, the computation... the graphic side isn't as important to me, but error creep, as it were, could always happen.
To perfection and no bugs :D
____________
The lovely lady you see is Hayley Westenra, an amazing pop-classical singer from Christchurch, New Zealand. She doesn't cure disease, but her songs will make you feel better. Basically, she's God's pure voice incarnate; she belongs with the seraphim.
Task 3a9bB_rebuild_loop_no_no_relax_16088_612_0 ( 297537645 ) hung on Windows 7 at 18% completion. According to BOINC it was still going but the Task Manager said it was getting 0% time. Invoking Graphics showed a blank black screen and had to be aborted.
Restarting the computer caused the task to start behaving normally again, but it soon hung (with the same symptoms) and I aborted it.
i have my computer which crach with few mns of "Rosetta mini 2.0".
I know IT it's Mini 2.0 which cause crach (no BSOD), just PC is as sleep, i push button power and PC STOP.
i do severales tests
Do you know which work unit you had problems with? Have you had this happen with more then one work unit?
hum i believe it is with: frb_0_8_mike_chosen_csts.noloopclose_ideal_hb_t369__IGNORE_THE_REST_1RXQA_8_16202_22_0, but note sure. it's an appli which is suspend.
i have not really saw the project, i have saw while minirosetta running, after few mns (2 or 3) my PC crach.
i can reset project and begin a new project without problem (crach) ?
____________
ID: 64150 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
i'm french, so.... ?
i can reset project and begin a new project without problem (crach) ?
Rosen, often people trying to translate BOINC terms, come up with words that do not match the English BOINC displays, so let me answer the two possible ways I see to interpret your question.
"Project" is Rosetta@home.
"Task" is one of the things your machine has downloaded from Rosetta.
If you "reset" the project, it aborts all of the tasks you have, and downloads all of the programs and files again (about 20MB of downloads), this is generally not necessary. If you "abort" a task, BOINC will try to download more work when it updates with the project the next time.
So, either way, your machine won't crash. But you will not get any credit for the aborted tasks. In general, you should not have to reset or abort anything. Perhaps you could post (en Francais if you must) what you are seeing that causes you to want to force a change.
____________ Rosetta Moderator: Mod.Sense
Confirmed.
11/24/2009 2:47:59 PM rosetta@home Task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 exited with zero status but no 'finished' file
11/24/2009 2:47:59 PM rosetta@home If this happens repeatedly you may need to reset the project.
11/24/2009 2:48:00 PM rosetta@home Restarting task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 using minirosetta version 200
11/24/2009 2:48:14 PM rosetta@home Computation for task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 finished
11/24/2009 2:48:14 PM rosetta@home Output file lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1_0 for task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 absent
TONS of this.
____________
ID: 64182 | Rating: 0 | rate:
/
P . P . L . Joined: Aug 20 06 Posts: 365 ID: 105843 Credit: 361,915 RAC: 771
Wed 25 Nov 2009 09:31:16 EST|rosetta@home|Starting task lr8_combine_smooth_torsion_it00_rama02_A_rlbd_1bgf_IGNORE_THE_REST_DECOY_14887_508_1 using minirosetta version 200
Wed 25 Nov 2009 09:31:29 EST|rosetta@home|Output file lr8_combine_smooth_torsion_it00_rama02_A_rlbd_1bgf_IGNORE_THE_REST_DECOY_14887_508_1_0 for task absent
=================================================================================
Wed 25 Nov 2009 09:31:29 EST|rosetta@home|Starting task lr8_combine_smooth_torsion_it00_rama09_A_rlbd_1b3a_IGNORE_THE_REST_DECOY_14894_617_1 using minirosetta version 200
Wed 25 Nov 2009 09:31:42 EST|rosetta@home|Output file lr8_combine_smooth_torsion_it00_rama09_A_rlbd_1b3a_IGNORE_THE_REST_DECOY_14894_617_1_0 for task absent
<core_client_version>6.2.14</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
ERROR: Value of inactive option accessed: -score:dun08_dir
____________
Confirmed.
11/24/2009 2:47:59 PM rosetta@home Task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 exited with zero status but no 'finished' file
11/24/2009 2:47:59 PM rosetta@home If this happens repeatedly you may need to reset the project.
11/24/2009 2:48:00 PM rosetta@home Restarting task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 using minirosetta version 200
11/24/2009 2:48:14 PM rosetta@home Computation for task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 finished
11/24/2009 2:48:14 PM rosetta@home Output file lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1_0 for task lr8_combine_smooth_torsion_it00_rama08_A_rlbd_2acy_IGNORE_THE_REST_DECOY_14893_560_1 absent
TONS of this.
can you post the links to those tasks that errored out like that?
there is usually an underlying cause in the task status report.
ID: 64190 | Rating: 0 | rate:
/
P . P . L . Joined: Aug 20 06 Posts: 365 ID: 105843 Credit: 361,915 RAC: 771
Wed 25 Nov 2009 12:03:07 EST|rosetta@home|Starting task lr8_combine_smooth_torsion_it00_rama03_A_rlbd_1kpe_IGNORE_THE_REST_DECOY_14888_508_0 using minirosetta version 200
Wed 25 Nov 2009 12:03:19 EST|rosetta@home|Output file lr8_combine_smooth_torsion_it00_rama03_A_rlbd_1kpe_IGNORE_THE_REST_DECOY_14888_508_0_0 for task absent
Wed 25 Nov 2009 11:43:49 EST|rosetta@home|Starting task lr8_combine_smooth_torsion_it00_rama07_A_rlbd_1kpe_IGNORE_THE_REST_DECOY_14892_659_0 using minirosetta version 200
Wed 25 Nov 2009 11:44:10 EST|rosetta@home|Output file lr8_combine_smooth_torsion_it00_rama07_A_rlbd_1kpe_IGNORE_THE_REST_DECOY_14892_659_0_0 for task absent
Wed 25 Nov 2009 11:44:11 EST|rosetta@home|Starting task lr8_combine_smooth_torsion_it00_rama07_A_rlbd_1ig5_IGNORE_THE_REST_DECOY_14892_659_0 using minirosetta version 200
Wed 25 Nov 2009 11:44:18 EST|rosetta@home|Output file lr8_combine_smooth_torsion_it00_rama07_A_rlbd_1ig5_IGNORE_THE_REST_DECOY_14892_659_0_0 for task absent
____________
ID: 64191 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
Many of these lr8_combine_smooth_torsion_it00_rama##... work units seem to be failing in first 30 seconds of execution with:
ERROR: Value of inactive option accessed: -score:dun08_dir
The messages tab then shows no output file was present as well.
I'm also seeing a considerable number of WUs with errors similar to those posted by others recently.
Here is an example of the messages on the client:
11/25/2009 1:10:59 PM rosetta@home Starting sel_core_1.0_low200_beta_low200_nostart_hb_t313__IGNORE_THE_REST_16216_654_1
11/25/2009 1:11:00 PM rosetta@home Starting task sel_core_1.0_low200_beta_low200_nostart_hb_t313__IGNORE_THE_REST_16216_654_1 using minirosetta version 200
11/25/2009 1:12:43 PM rosetta@home Computation for task sel_core_1.0_low200_beta_low200_nostart_hb_t313__IGNORE_THE_REST_16216_654_1 finished
11/25/2009 1:12:43 PM rosetta@home Output file sel_core_1.0_low200_beta_low200_nostart_hb_t313__IGNORE_THE_REST_16216_654_1_0 for task sel_core_1.0_low200_beta_low200_nostart_hb_t313__IGNORE_THE_REST_16216_654_1 absent
stderr is slightly different though. stderr from my WUs is like:
<core_client_version>6.6.38</core_client_version>
<![CDATA[
<message>
Funzione non corretta. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
[2009-11-24 9:22: 6:] :: BOINC:: Initializing ... ok.
[2009-11-24 9:22: 6:] :: 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
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/yfsong_lr8_combine_smooth_torsion_it00_rama06_A.zip
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/lr8_1shf.out.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active. Fullatom mode ..
ERROR: Value of inactive option accessed: -score:dun08_dir
</stderr_txt>
]]>
while the one from some of bruce's WUs is like:
<core_client_version>6.10.18</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
[2009-11-25 13:11: 0:] :: BOINC:: Initializing ... ok.
[2009-11-25 13:11: 0:] :: 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
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/sel_core_1.0_low200_beta_low200_nostart.broker_corebuild.t313_.olange.boinc_files.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
ERROR: res1 != res2
ERROR:: Exit from: ..\..\src\core\kinematics\FoldTree.cc line: 2342
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish
</stderr_txt>
]]>
____________
ID: 64232 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
darkpella, all four of the tasks you linked are the known problem described here with "...rama..." in the name. These tasks were later corrected and reissued with "...redo..." in the name.
____________ Rosetta Moderator: Mod.Sense
which gave the same res1 != res2 error but ran for half an hour and returned an error status of success.
Again, it seems it's those tasks with t331 and t297 in their names that are causing problems.
____________
ID: 64345 | Rating: 0 | rate:
/
P . P . L . Joined: Aug 20 06 Posts: 365 ID: 105843 Credit: 361,915 RAC: 771
Mod Sense, Here you go.
These are the only ones still in my list.
Credit was about normal, mostly get less than claimed anyway.
Don't think there was any double headers as you call them, some may have restarted.
===============================================================
This one did 135 models. - CC_101.22 / GC_83.32
http://boinc.bakerlab.org/rosetta/workunit.php?wuid=275075567
---------------------------------------------------------------
This did 112. - CC_101.69 / GC_81.83
http://boinc.bakerlab.org/rosetta/workunit.php?wuid=274576093
---------------------------------------------------------------
This did 153. - CC_102.90 / GC_86.03
http://boinc.bakerlab.org/rosetta/workunit.php?wuid=273886738
---------------------------------------------------------------
This did 116. - CC_103.40 / GC_85.25
I have WU 3gbm_3g0l_0264_revert.php_dock_rmsd.xml__16270_181_1 now elapsed 13:25:10 with 0.789% progress. Should I let it go or delete it?
With a 3-hour default runtime the watchdog ought to have closed it down already, but if you click properties on that WU I would expect the CPU time is minimal, so something seems to have stalled with that one. I'd abort it and hope the next person that picks it up has more success with it.
____________
Done, thanks. You were right, only 3 min of CPU time.
Valter.
____________
ID: 64396 | Rating: 0 | rate:
/
Mod.Sense Forum moderator Project administrator Joined: Aug 22 06 Posts: 2397 ID: 106194 Credit: 0 RAC: 0
...and so it becomes a question of whether your machine has something else going on at a higher priority that is causing BOINC not to get any CPU time? Or is there a problem with BOINC or the task?
All other things being equal, starting a new task would also be impacted by other activity on the system (assuming the other activity is still running). Is your next task running normally? (i.e. check properties or task manager and see how many actual CPU seconds it has now used).
[edit] I don't see this task in your results and off-hand, the naming doesn't look like a Rosetta task. Can you post a link?
____________ Rosetta Moderator: Mod.Sense
...and so it becomes a question of whether your machine has something else going on at a higher priority that is causing BOINC not to get any CPU time? Or is there a problem with BOINC or the task?
All other things being equal, starting a new task would also be impacted by other activity on the system (assuming the other activity is still running). Is your next task running normally? (i.e. check properties or task manager and see how many actual CPU seconds it has now used).
[edit] I don't see this task in your results and off-hand, the naming doesn't look like a Rosetta task. Can you post a link?
I've seen this kind of thing very occasionally, even while other WUs appear to be running fine. In this case Valter appears to have been the wingman where the original cruncher failed as well.
____________
I've had a couple of tasks with names like 3a9bB* fail on Windows 7. In both cases I had to abort them as no progress was being made, even though they weren't getting any CPU time. My wingman in both cases successfully completed the tasks, one on Max OS X and the other on Win XP. The first one's reported above: the second is 271436170
Validate errors in workunits with the name: mix_score13_hb_rlbd_1ttz__IGNORE_THE_RESTlr13_DECOY_16324_*
- 1. ----------------------------------------------------------
Task: 303144429
Workunit: mix_score13_hb_rlbd_1ttz__IGNORE_THE_RESTlr13_DECOY_16324_936_0
CPU time: 85.64598
stderr out:
...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
Fullatom mode ..
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 1201 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================
BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish
- 2. ----------------------------------------------------------
Task: 302775198
Workunit: mix_score13_hb_rlbd_1ttz__IGNORE_THE_RESTlr13_DECOY_16324_508_1
CPU time: 75.6415
stderr out:
...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
Fullatom mode ..
# cpu_run_time_pref: 43200
======================================================
DONE :: 1 starting structures 1201 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================
BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish
AdeB
____________
ID: 64406 | Rating: 0 | rate:
/
Yifan Song Forum moderator Project administrator Project developer Project scientist Joined: May 26 09 Posts: 41 ID: 318024 Credit: 0 RAC: 0
Validate errors in workunits with the name: mix_score13_hb_rlbd_1ttz__IGNORE_THE_RESTlr13_DECOY_16324_*
...
AdeB
Thanks!
There was a bug when we combine lr5, 8, 10 and 13 to make a large test. As a result, a few lr13 ones end up with too small input file and running too fast for the validation server.
This should be fixed soon.