Posts by James W

1) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99400)
Posted 26 Oct 2020 by James W
Post:
Name: CLPPPJS8_255_ClpP1P2_stub_justPHE_0001_SAVE_ALL_OUT_1018533_362_1
Application: Rosetta v4.20 windows_x86_64
Device: 1759960
Task: 1284630939. WU: 1150838856
Status: Error while computing
Exit status: -1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION
Errors: Too many errors (may have bug). Too many total results.
Stderr output:
(unknown error) - exit code -1073741819 (0xc0000005)
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000143141D48

Engaging BOINC Windows Runtime Debugger...

I was wingman on this new for me type WU and we both got same error. Run time about 15 sec., so no big loss. Don't see any more like this in my current queue.
2) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99239)
Posted 4 Oct 2020 by James W
Post:
Name: DNANX53C_DnaN_53C_refine_26_stripped_relax_-1_-1_3_45942938_4mers_0002_SAVE_ALL_OUT_1014073_330_0
Application: Rosetta v4.20 windows_x86_64
Device: 3710630
Task: 1270233986. WU: 1138185669
Status: Error while computing
Exit status: -1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION
Stderr output:
(unknown error) - exit code -1073741819 (0xc0000005)
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000000000017

Engaging BOINC Windows Runtime Debugger...
Also rec'd identical error on host 1759960 for task 1270067381. Will see how wingman fares.

Errors: Too many errors (may have bug) Too many total results.
Well, wingman errored out in same approximate time with same errors. Appears this type of task requiring something many hosts are missing. I do note that at least 1 or 2 of these tasks DID validate on my system(s). Not too many of them rec'd, thank goodness.
3) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99223)
Posted 3 Oct 2020 by James W
Post:
Name: DNANX53C_DnaN_53C_refine_26_stripped_relax_-1_-1_3_45942938_4mers_0002_SAVE_ALL_OUT_1014073_330_0
Application: Rosetta v4.20 windows_x86_64
Device: 3710630
Task: 1270233986. WU: 1138185669
Status: Error while computing
Exit status: -1073741819 (0xC0000005) STATUS_ACCESS_VIOLATION
Stderr output:
(unknown error) - exit code -1073741819 (0xc0000005)
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x0000000000000017

Engaging BOINC Windows Runtime Debugger...
Also rec'd identical error on host 1759960 for task 1270067381. Will see how wingman fares.
4) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99210)
Posted 1 Oct 2020 by James W
Post:
Name: rb_09_28_39311_38407_ab_t000__robetta_cstwt_5.0_FT_IGNORE_THE_REST_08_11_1013728_48_0
Application: Rosetta v4.20 windows_x86_64
Device: 3710630
Task: 1268869051. WU: 1137002647
Status: Error while computing
Exit status: 1 (0x00000001) Unknown error code
Stderr output:
<message>Incorrect function. (0x1) - exit code 1 (0x1)</message>
[ ERROR ]: Caught exception:

File: C:cygwin64homeboinc4.17Rosettamainsourcesrccore/pack/dunbrack/SingleResidueDunbrackLibrary.hh:306
chi angle must be between -180 and 180: -nan(ind)
------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------

AN INTERNAL ERROR HAS OCCURED[sic]. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.
1. Coder/programmer needs to spell "occurred" correctly.
2. Thankful still able to get credit for host's efforts. Note that I rec'd more credit than wingman.
5) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99180)
Posted 29 Sep 2020 by James W
Post:
Name: cd28_1yjd_graft_v1_SAVE_ALL_OUT_IGNORE_THE_REST_7xw0rf6z_1013410_1_0
Application: Rosetta v4.20 windows_x86_64
Device: 3710630
Task: 1267451815. WU: 1135747396
Status: Completed and validated
Peak working set size 1,351.17 MB
Peak swap size 1,324.82 MB
Stderr output:
<stderr_txt>ftMover.cc:537
For this scaffold there are not suitable scaffold grafts within your constrains
------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------

AN INTERNAL ERROR HAS OCCURED[sic]. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.

[ ERROR ]: Caught exception:

File: ......srcprotocolsmotif_graftingmoversMotifGraftMover.cc:537
For this scaffold there are not suitable scaffold grafts within your constrains
------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------

AN INTERNAL ERROR HAS OCCURED. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.
And continues repeating above until apparently runs out of space.
FYI -- Just noting we have another new task type with these same errors/exceptions which still create valid results. The similarity appears to be that these tasks all involve "scaffold grafts."
6) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 99163)
Posted 27 Sep 2020 by James W
Post:
Name: vegf_site1_graft_v1_SAVE_ALL_OUT_IGNORE_THE_REST_3vc7wl1o_1013290_1
Application: Rosetta v4.20 windows_x86_64
Device: 3710630
Task: 1266413150. WU: 1134838287
Status: Completed and validated
Peak working set size 1,234.59 MB
Peak swap size 1,209.23 MB
Stderr output:
<stderr_txt>aftMover.cc:537
For this scaffold there are not suitable scaffold grafts within your constrains
------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------

AN INTERNAL ERROR HAS OCCURED. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.

[ ERROR ]: Caught exception:

File: ......srcprotocolsmotif_graftingmoversMotifGraftMover.cc:537
For this scaffold there are not suitable scaffold grafts within your constrains
And continues repeating above until apparently runs out of space.

Just noting we have a new task type with these same errors/exceptions which still create valid results. FYI. Get these same results on both of my hosts.
7) Message boards : Number crunching : Record days. (Message 99162)
Posted 27 Sep 2020 by James W
Post:
That would make sense.

It is interesting that the lower numbers are later. I guess the initial surge of interest in Corona faded somewhat. I guess some crunchers thought they'd done their bit.

The lowering of credit numbers might not be due solely to there being less "crunchers" or less hosts working on R@H. With my 2 moderately powered hosts running with 4 cores (one physical and one Hyper-threaded) and 8 G RAM each I can process about 18 WUs per day, though the amount of credit varies widely depending on the type of task being crunched. Viewing the statistics chart in BOINC manager shows this.

However, are you looking at number of credits, number of hosts in service, or a combination?
8) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98923)
Posted 9 Sep 2020 by James W
Post:
Name: kp8RjDVk_fold_and_dock_SAVE_ALL_OUT_1009390_4466
Application: Rosetta v4.20 windows_x86_64
Device: 1759960
Task: 1255806099. WU: 1125665905
Status: Error while computing
Exit status: -529697949 (0xE06D7363) Unknown error code
Errors: Too many errors (may have bug). Too many total results.
Peak working set size 5,967.66 MB
Peak swap size 8,158.26 MB
Peak disk usage 26.02 MB
Stderr output:
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x000007FEFD27B87D

Engaging BOINC Windows Runtime Debugger...
This was one of 3 errors today with my two hosts, working the above "fold and dock" series. This particular host has 8 GB RAM. It held out for 18+ minutes before the memory demand noted above overwhelmed it and it errored out the task. My host was the first to crunch and the wingperson with 16 GB RAM also errored for same reason. This is the same series of tasks which many here have commented on -- memory gobblers.
9) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98643)
Posted 24 Aug 2020 by James W
Post:
Device: 1759960
Task: 1245719883. WU: 1115277497
Puzzling credit amount.
I was assigned this task after the original host did not complete by deadline. The original host and I both rec'd 26.22 credits. My host worked almost 8 hrs (CPU time) whereas original host only worked less than 1 hr., with same results. Unsure of logic of this.
Computer ID 5135728
Run time 1 hours 0 min 1 sec
CPU time 58 min 1 sec
======================================================
DONE :: 1 starting structures 3480.83 cpu seconds
This process generated 14 decoys from 14 attempts
======================================================
BOINC :: WS_max 3.11939e+08
And my Stderr output, etc.:
Computer ID 1759960
Run time 8 hours 37 min 35 sec
CPU time 7 hours 58 min 28 sec
======================================================
DONE :: 1 starting structures 28708.7 cpu seconds
This process generated 145 decoys from 145 attempts
======================================================
BOINC :: WS_max 3.30969e+08
10) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98593)
Posted 19 Aug 2020 by James W
Post:
The recent posts are all rather peculiar to me.
I thought I must have missed these tasks going through, but there are none at all in my recent history.
And today is the first day i don't have any in my current Task list either, after having them continuously for over a week and a half.
Even the number of errored/Invalid Tasks for the top systems has dropped off a lot over the last few hours.

To get back into the subject of the thread (Rosetta 4.2+), I rec'd 5 more foldit1 validation errors for one of my Android devices. However, these were all resent tasks for not starting by deadline, first sent 8/15. This is forgivable, as would be difficult for system to screen for problematic tasks in this case. These had all originally been sent to Windows or Linux systems. It appears that these are slowly getting cleaned out of the system thankfully.
11) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98537)
Posted 16 Aug 2020 by James W
Post:
And again I continue to receive validation errors (another 8 total today, 8-15-20,) on my Android device (3396190) for the foldit1 tasks. Again I question why these clearly erroneous tasks continue to be created! The batch in question today were created during the day of 8/15. The admins and researcher(s) involved with this particular set of tasks must know by now that this particular set of tasks won't produce anything useful! Of note, I've only recently seen these errors/tasks on my Android devices -- not on my PCs -- for whatever reason.

Examples of the specific validation errors have previously been quoted by myself and others in this thread. Today's errors include the following tasks:
1. Name: foldit1_2008762_0003_00_asym_dock_SAVE_ALL_OUT_1005836_4487
Task: 1241587912
2. Name: foldit1_2008835_c016_00_asym_dock_SAVE_ALL_OUT_1005885_4489
Task: 1241587932
3. Name: foldit1_2008835_0008_00_asym_dock_SAVE_ALL_OUT_1005883_4423
Task: 1241586218

Thank you, Grant, for your expert logical arguments regarding this continued issue!
12) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98513)
Posted 15 Aug 2020 by James W
Post:
I continue to receive validation errors (8 total today) on my Android devices (3182472 and 3396190) for the foldit1 tasks. Again I question why these clearly erroneous tasks continue to be created! The batch in question today were created the morning of 8/14. What is to be gained by this waste of time, effort, and resources? The admins must know by now this particular set of tasks won't produce anything useful!

Examples of the specific validation errors have previously been quoted by myself and others in this thread. Today's errors include the following tasks:
1. Name: foldit1_2008707_s008_00_asym_dock_SAVE_ALL_OUT_1005682_1795
Task: 1240650010
2. Name: foldit1_2008707_s007_00_asym_dock_SAVE_ALL_OUT_1005684_1795
Task: 1240650112
3. Name: foldit1_2008663_y239_00_asym_dock_SAVE_ALL_OUT_1005837_1622
Task: 1240466476

Etc.
13) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98505)
Posted 14 Aug 2020 by James W
Post:
Re: WU 1110767160 -
simsjn_out_Protein_A_v5_contacts_36_7_L20L2L1L2L2L2L2L3L20_fragments_abinitio_SAVE_ALL_OUT_1006608_826_0

Just wanted to note that my wingman also got the same error as I, with notation "Too many errors (may have bug) Too many total results."
14) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98499)
Posted 13 Aug 2020 by James W
Post:
Name: simsjn_out_Protein_A_v5_contacts_36_7_L20L2L1L2L2L2L2L3L20_fragments_abinitio_SAVE_ALL_OUT_1006608_826_0
Application: Rosetta v4.20 windows_x86_64
Device: 1759960
Task: 1238685086. WU: 1110767160
Status: Error while computing
Exit status: 1 (0x00000001) Unknown error code
Stderr output:
Incorrect function.
(0x1) - exit code 1 (0x1)
ERROR: ERROR: FragmentIO: could not open file 00001.200.9mers
ERROR:: Exit from: ......srccorefragmentFragmentIO.cc line: 233
BOINC:: Error reading and gzipping output datafile: default.out
00:45:27 (8780): called boinc_finish(1)
15) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98498)
Posted 13 Aug 2020 by James W
Post:
I continue to receive validation errors (36 total today!) on my Android devices for the foldit1 tasks, today adding my Samsung phone (3182472). The only difference in the error descriptions of the 2 devices so far is that the Amazon tablet (3396190) includes the added remarks:
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x28ac
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
not mentioned in the Samsung error. Of interest is the fact that Rosetta has not elected to rerun these particular validation errors with a wingperson. They have marked all these errors as "canonical." Also of interest is that all these errored tasks were created just this morning, despite the many reports of problems with this series of tasks!!! Doesn't appear anyone in "authority" bothers to read these posts, or just ignores them!!

Examples of the validation errors previously quoted by myself in this thread, as well as by Grant. Today's errors include the following tasks:
1. Name: foldit1_2008492_0006_00_asym_dock_SAVE_ALL_OUT_1005840_1234
Task: 1239403625 on Amazon.
2. Name: foldit1_2001822_s003_00_asym_dock_SAVE_ALL_OUT_1005892_1233
Task: 1239397848 on Samsung.
16) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98488)
Posted 12 Aug 2020 by James W
Post:
More tasks which failed to validate for my Amazon tablet (3396190), as noted in message 98480, include:
    1. Name: foldit1_2008835_0007_00_asym_dock_SAVE_ALL_OUT_1005865_1042_0
    Task: 1238599419
    2. Name: foldit1_2008899_0006_00_asym_dock_SAVE_ALL_OUT_1005735_1039
    Task: 1238585227
    3. Name: foldit1_2008762_s009_00_asym_dock_SAVE_ALL_OUT_1005863_1039
    Task: 1238585235
    4. Name: foldit1_2001822_0008_00_asym_dock_SAVE_ALL_OUT_1005689_1031
    Task: 1238545676
    5. Name: foldit1_2001209_0006_00_asym_dock_SAVE_ALL_OUT_1005688_1031
    Task: 1238545660
    6. Name: foldit1_2008663_y239_00_asym_dock_SAVE_ALL_OUT_1005837_947
    Task: 1238195355
    7. Name: foldit1_2008663_s004_00_asym_dock_SAVE_ALL_OUT_1005838_947
    Task: 1238195616
    8. Name: foldit1_2008663_y688_00_asym_dock_SAVE_ALL_OUT_1005783_946
    Task: 1238189780

Plus 5 more tasks.

17) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98482)
Posted 11 Aug 2020 by James W
Post:
Other tasks which failed to validate for my Amazon tablet (3396190) included:
    1. Name: foldit1_2008663_y688_00_asym_dock_SAVE_ALL_OUT_1005783_946
    Task: 1238189780

    2. Name: foldit1_2001331_0004_00_asym_dock_SAVE_ALL_OUT_1005656_946
    Task: 1238189817

    3. Name: foldit1_2001734_0007_00_asym_dock_SAVE_ALL_OUT_1005855_931
    Task: 1238132060

    4. Name: foldit1_2001331_0005_00_asym_dock_SAVE_ALL_OUT_1005726_931
    Task: 1238131939

    5. Name: foldit1_2008899_c029_00_asym_dock_SAVE_ALL_OUT_1005801_931
    Task: 1238130586

    6. Name: foldit1_2004919_s004_00_asym_dock_SAVE_ALL_OUT_1005802_931
    Task: 1238130600


All of the above tasks had the same basic validation errors as posted in my previous message.

18) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98480)
Posted 11 Aug 2020 by James W
Post:
Another set of Foldit1 invalidation errors on my Android tablet (an Amazon Fire tablet):
Name: foldit1_2008663_y688_00_asym_dock_SAVE_ALL_OUT_1005783_946_0
Application: Rosetta v4.20 arm-android-linux-gnu
Device: 3396190
Task: 1238189780. WU: 1110337695
Status: Validate error
Exit status: 0 (0x00000000)
Stderr output:
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x28ac
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2

[ ERROR ]: Caught exception:

File: src/protocols/rosetta_scripts/RosettaScriptsParser.cc:1313
Input Rosetta scripts XML file "asym_dock_global.xml" failed to validate against the Rosetta scripts schema. Use the option -parser::output_schema <output filename> to output the schema to a file to see all valid options.
Your XML has failed validation. The error message below will tell you where in your XML file the error occurred. Here's how to fix it:

1) If the validation fails on something obvious, like an illegal attribute due to a spelling error (perhaps you used scorefnction instead of scorefunction), then you need to fix your XML file.
2) If you haven&#226;&#128;&#153;t run the XML rewriter script and this might be pre-2017 Rosetta XML, run the rewriter script (tools/xsd_xrw/rewrite_rosetta_script.py) on your input XML first. The attribute values not being in quotes (scorefunction=talaris2014 instead of scorefunction="talaris2014") is a good indicator that this is your problem.
3) If you are a developer and neither 1 nor 2 worked - email the developer&#226;&#128;&#153;s mailing list or try Slack.
4) If you are an academic or commercial user - try the Rosetta Forums https://www.rosettacommons.org/forum

Error messages were:
Error: AttValue: " or ' expected
<dock_design> errors included:
1. Error: attributes construct error
2. Error: Couldn't find end of Start Tag fullatom line 3
3. Error: Opening and ending tag mismatch: SCOREFXNS line 2 and fullatom
4. Error: Opening and ending tag mismatch: dock_design line 1 and SCOREFXNS
5. Error: Extra content at the end of the document
------------------------------------------------------------
Warning messages were:
------------------------------------------------------------

------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------
DummyMover::apply() should never have been called! (JobDistributor/Parser should have replaced DummyMover.)

ERROR: Function not implemented.
ERROR:: Exit from: src/apps/public/boinc/minirosetta.cc line: 101
19) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98439)
Posted 8 Aug 2020 by James W
Post:
First Android task I've processed in ages (also first Android error in ages).
Also had a similar Validate Error for another Android "foldit" task.

Name: foldit1_2001331_0001_00_asym_dock_SAVE_ALL_OUT_1005715_293_0
Application: Rosetta v4.20 arm-android-linux-gnu
Device: 3396190
Task: https://boinc.bakerlab.org/rosetta/result.php?resultid=1235917770]1235917770[/url]. WU: 1108336404
Status: Validate error
Exit status: 0 (0x00000000)
Stderr output:
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x28ac
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
command: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_arm-android-linux-gnu @foldit1_2001331_0001_global_dock_flags -in:file:boinc_wu_zip asym_dock_foldit1_2001331_0001_data.zip -patchdock foldit1_2001331_0001_patchdock.patchdock -patchdock_random_entry 1 3912 -in:file:s foldit1_2001331_0001_patchdock.pdb -nstruct 10000 -cpu_run_time 28800 -boinc:max_nstruct 20000 -checkpoint_interval 120 -mute all -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -boinc::cpu_run_timeout 36000 -run::rng mt19937 -constant_seed -jran 1396632
Using database: database_357d5d93529_n_methyl/minirosetta_database

[ ERROR ]: Caught exception: File: src/protocols/rosetta_scripts/RosettaScriptsParser.cc:1313
Input Rosetta scripts XML file "asym_dock_global.xml" failed to validate against the Rosetta scripts schema. Use the option -parser::output_schema <output filename> to output the schema to a file to see all valid options.
Your XML has failed validation. The error message below will tell you where in your XML file the error occurred. Here's how to fix it:

1) If the validation fails on something obvious, like an illegal attribute due to a spelling error (perhaps you used scorefnction instead of scorefunction), then you need to fix your XML file.
2) If you haven&#226;&#128;&#153;t run the XML rewriter script and this might be pre-2017 Rosetta XML, run the rewriter script (tools/xsd_xrw/rewrite_rosetta_script.py) on your input XML first. The attribute values not being in quotes (scorefunction=talaris2014 instead of scorefunction="talaris2014") is a good indicator that this is your problem.
3) If you are a developer and neither 1 nor 2 worked - email the developer&#226;&#128;&#153;s mailing list or try Slack.
4) If you are an academic or commercial user - try the Rosetta Forums https://www.rosettacommons.org/forum

Error messages were:
Error: AttValue: " or ' expected
Number of <dock_design> errors skipped
------------------------------------------------------------
Warning messages were:
------------------------------------------------------------

------------------------ Begin developer's backtrace -------------------------
BACKTRACE:
------------------------- End developer's backtrace --------------------------
DummyMover::apply() should never have been called! (JobDistributor/Parser should have replaced DummyMover.)

ERROR: Function not implemented.
ERROR:: Exit from: src/apps/public/boinc/minirosetta.cc line: 101
called boinc_finish(0)
20) Message boards : Number crunching : Rosetta 4.1+ and 4.2+ (Message 98438)
Posted 8 Aug 2020 by James W
Post:
Name: foldit0_2001734_0009_relax_dock_SAVE_ALL_OUT_1005379_3
Application: Rosetta v4.20 windows_x86_64
Device: 1759960
Task: 1234502102. WU: 1107127887
Status: Error while computing.
Exit status: -1 (0xFFFFFFFF) Unknown error code
Errors: Too many errors (may have bug) Too many total results.
Stderr output: (unknown error) - exit code -1 (0xffffffff)
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.20_windows_x86_64.exe @foldit0_2001734_0009_local_dock_flags -in:file:boinc_wu_zip asym_dock_foldit0_2001734_0009_data.zip -nstruct 10000 -cpu_run_time 28800 -boinc:max_nstruct 20000 -checkpoint_interval 120 -mute all -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -boinc::cpu_run_timeout 36000 -run::rng mt19937 -constant_seed -jran 2032508

[ ERROR ]: Caught exception:

File: ......srcutilityoptionsOptionCollection.cc:1398
Option matching -boinc:score_cut_smart_throttle not found in command line top-level context

AN INTERNAL ERROR HAS OCCURED. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.
Appears quite similar to Grant's reported error. Wingman also failed, but different error code (Signal 11). Note my system Windows and that system Apple.


Next 20



©2024 University of Washington
https://www.bakerlab.org