Greetings.
After several years, I have restarted using Rosetta@Home today (03 Oct. 2021).

[edit] I am running Ubuntu Linux. [end edit]

My first WU failed.
My task list is at https://boinc.bakerlab.org/rosetta/results.php?userid=234922

Looking at the task data, it says:
Name 5nvx_graft_buwei_xac_SAVE_ALL_OUT_IGNORE_THE_REST_5wf5yk4z_1731809_7_0

Workunit 1278490109

It is a Validate error - Missing a constraint file

Stderr output

<core_client_version>7.16.16</core_client_version>
<![CDATA[
<stderr_txt>
command: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.20_x86_64-pc-linux-gnu -run:protocol jd2_scripting -parser:protocol pdblite_boinc_120_10--fuse--predictor_v11_boinc_fix--fuse--tslp_design_v1_boinc_fix_plus6.xml @5nvx_graft_buwei_flags -in:file:silent 5nvx_graft_buwei_xac_SAVE_ALL_OUT_IGNORE_THE_REST_5wf5yk4z.silent -in:file:silent_struct_type binary -silent_gz -mute all -silent_read_through_errors true -out:file:silent_struct_type binary -out:file:silent default.out -in:file:boinc_wu_zip 5nvx_graft_buwei_xac_SAVE_ALL_OUT_IGNORE_THE_REST_5wf5yk4z.zip @5nvx_graft_buwei_xac_SAVE_ALL_OUT_IGNORE_THE_REST_5wf5yk4z.flags -nstruct 10000 -cpu_run_time 28800 -boinc:max_nstruct 20000 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -boinc::cpu_run_timeout 36000 -run::rng mt19937 -constant_seed -jran 1141314
Using database: database_357d5d93529_n_methyl/minirosetta_database

ERROR: [ERROR] Unable to open constraints file: m_15a03ae7649ebbac21f4683df9edff8e_0001_000000086_0001_35_50_H_._HHH_b1_03106_0001_1_0001.MSAcst

ERROR:: Exit from: src/core/scoring/constraints/ConstraintIO.cc line: 457
17:11:07 (12659): called boinc_finish(0)

</stderr_txt>
]]>

I do not know what a constraints file should look like.
I looked into ....database_357d5d93529_n_methyl/minirosetta_database and saw

/database_357d5d93529_n_methyl/minirosetta_database/scoring/constraints/epr_distance_potential.histogram

It looks like:

x_axis	-14.750	-14.250	-13.750	-13.250	-12.750	-12.250	-11.750	-11.250	-10.750	-10.250	-9.750	-9.250	-8.750	-8.250	-7.750	-7.250	-6.750	-6.250	-5.750	-5.250	-4.750	-4.250	-3.750	-3.250	-2.750	-2.250	-1.750	-1.250	-0.750	-0.250	0.250	0.750	1.250	1.750	2.250	2.750	3.250	3.750	4.250	4.7505.250	5.750	6.250	6.750	7.250	7.750	8.250	8.750	9.250	9.750	10.250	10.750	11.250	11.750	12.250	12.750	13.250	13.750	14.250	14.750
y_axis	0.000	0.000	0.000	0.000	0.000	0.000	-0.019	-0.058	-0.097	-0.138	-0.178	-0.220	-0.262	-0.304	-0.347	-0.390	-0.432	-0.476	-0.518	-0.561	-0.604	-0.647	-0.689	-0.731	-0.774	-0.815	-0.856	-0.897	-0.937	-0.977	-0.998	-0.999	-1.000	-0.999	-0.998	-0.995	-0.990	-0.985	-0.977	-0.968	-0.957	-0.943	-0.927	-0.907	-0.884	-0.857	-0.823	-0.784	-0.737	-0.677	-0.602	-0.505	-0.368	-0.157	0.000	0.000	0.000	0.000	0.000	0.000

I see no (apparently) mangled data.
That was the only file in the directory.

Any debug ideas??

Thanks in advance!!
Jay

My first WU failed.
My task list is at https://boinc.bakerlab.org/rosetta/results.php?userid=234922

It's not you, it's the Task.
Some 5nvx_graft_buwei_ Tasks do that, and that's the error they report (some of them will give the same stderr output, but will Validate).

If you get such errors from other non-5nvx_graft_buwei_ Tasks, then you do have a problem.

---

Grant
Darwin NT

Thanks, Grant.

Jay

My first WU failed.
My task list is at https://boinc.bakerlab.org/rosetta/results.php?userid=234922

It's not you, it's the Task.
Some 5nvx_graft_buwei_ Tasks do that, and that's the error they report (some of them will give the same stderr output, but will Validate)

These ae very much like that massive batch pre_clinical bundles tasks from Apr-July.
All the erroring tasks run very short. The slightly longer-running ones validate and give credit for minimal runtime, the very shortest error out with no credit.
As I remember, the runtime is so minimal the project decided it wasn't worth wheedling them out, so it's easier to let them error out at almost zero "cost" to the user than try to find them, maybe taking out good tasks in the process.
So, just don't worry about them

---

Thanks, Grant.

Jay

No worries.


NB- as you are running more than one project, you would be much better off letting the Tasks run for the default Target CPU time (which is 8 hours) instead of for 24hrs.
And if you set your cache to 0 (or pretty much zero), it will allow your Resource share settings to be met much sooner.
0.1 days & 0.01 additional days would be plenty.

---

Grant
Darwin NT