As Windows has a path limit of 256 characters and the above path is 228 characters (excluding the file extension and higher levels of the path) you are bound to generate errors on a regular basis.

File names are limited to 255 characters, full paths to 32,767 characters, see http://en.wikipedia.org/wiki/NTFS -> Internals.

---

.

As Windows has a path limit of 256 characters and the above path is 228 characters (excluding the file extension and higher levels of the path) you are bound to generate errors on a regular basis.

File names are limited to 255 characters, full paths to 32,767 characters, see http://en.wikipedia.org/wiki/NTFS -> Internals.

Yes and no.
Yes, the maximum path can be extended to approximately 32,767 characters.
No, the default behaviour in Windows is to limit the path to 256 characters (even under NTFS).

See Naming Files, Paths, and Namespaces for more details.

Unless I'm seeing a lot of old work units, the majority of the ones on my computer do not reflect the "workunit estimated FLOPS value has been doubled." At this point I have 50 work units awaiting processing and only two of them show the longer estimated time.

I am hoping to receive more of the "25 Hour" wu's and not those at 45-50 hours. The latter ones result in errors for me.

Norman, in message 77392, reports a memory leak under OSX. I've been having the same problem for the last few weeks. The problem grows until the system freezes. As a result I've had to shut down R@H computations until the bug is fixed. This is unfortunate.

Sorry about posting this way. I can't see how to comment on a specific message directly.

---

I am hoping to receive more of the "25 Hour" wu's and not those at 45-50 hours. The latter ones result in errors for me.

0 to 100% = (24 hour) minirosetta, (25 Hour) boinc

---

I am still getting a lot of work units for which the "workunit estimated FLOPS value has been doubled" has not happened (tj_ and rb_). My duration correction factor is all over the place. Please make up your mind(s).

I am still getting a lot of work units for which the "workunit estimated FLOPS value has been doubled" has not happened (tj_ and rb_). My duration correction factor is all over the place. Please make up your mind(s).

Thanks for the heads up. New rb_ jobs should be fixed. Older jobs that are still in our system unfortunately will keep the old values. They should gradually get purged out as they complete.

696381923

ERROR: Assertion failure: runtime_assert( ( begin + size - 1 ) <= pose.total_residue() );
ERROR:: Exit from: ......srcprotocolssimple_movesFragmentMover.cc line: 307
std::cerr: Exception was thrown:


[ERROR] EXCN_utility_exit has been thrown from: ......srcprotocolssimple_movesFragmentMover.cc line: 307
ERROR: Assertion failure: runtime_assert( ( begin + size - 1 ) <= pose.total_residue() );

---

Rosettaq mini 3.52
event log: exited with zero status but no finished file
if this happens repeatidly you may need to reset the project.
Well it seems it happens quite a lot! should I reset the project?

Rosettaq mini 3.52
event log: exited with zero status but no finished file
if this happens repeatidly you may need to reset the project.
Well it seems it happens quite a lot! should I reset the project?

That is a random BOINC bug that can affect any project and is not specifically a Rosetta issue.

See this BOINC FAQ page for several tips on how to fix the problem. I've been told that item
7 on the list often turns out to be the correct solution for most people, and it certainly worked
for me.

And this

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x01530DD9 read attempt to address 0x00000000

---

After to restart my PC this morning i get

7 x Client error / Compute error

Task:
https://boinc.bakerlab.org/rosetta/result.php?resultid=696831411
https://boinc.bakerlab.org/rosetta/result.php?resultid=696830180
https://boinc.bakerlab.org/rosetta/result.php?resultid=696823199
https://boinc.bakerlab.org/rosetta/result.php?resultid=696820951
https://boinc.bakerlab.org/rosetta/result.php?resultid=696819719
https://boinc.bakerlab.org/rosetta/result.php?resultid=696815927
https://boinc.bakerlab.org/rosetta/result.php?resultid=696812279

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
Unzulässige Funktion.
(0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
[2014-10-18 23:33:27:] :: BOINC:: Initializing ... ok.
[2014-10-18 23:33:27:] :: 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.
command: projects/boinc.bakerlab.org_rosetta/minirosetta_3.52_windows_x86_64.exe @6htube8_53_fold_and_dock_flags -silent_gz -mute all -out:file:silent default.out -in:file:boinc_wu_zip fold_and_dock_6htube8_53_data.zip -nstruct 10000 -cpu_run_time 21600 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 3669074
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_3d2618f.zip
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/fold_and_dock_6htube8_53_data.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
[2014-10-19 8:43:40:] :: BOINC:: Initializing ... ok.
[2014-10-19 8:43:40:] :: 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.
command: projects/boinc.bakerlab.org_rosetta/minirosetta_3.52_windows_x86_64.exe @6htube8_53_fold_and_dock_flags -silent_gz -mute all -out:file:silent default.out -in:file:boinc_wu_zip fold_and_dock_6htube8_53_data.zip -nstruct 10000 -cpu_run_time 21600 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 3669074
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_3d2618f.zip
error: cannot create ./minirosetta_database/chemical/mm_atom_type_sets/fa_standard/top_all27_prot_na.rtf
error: cannot create ./minirosetta_database/rotamer/ExtendedOpt1-5/asn.bbdep.rotamers.lib.gz
error: cannot create ./minirosetta_database/rotamer/ExtendedOpt1-5/asp.bbdep.rotamers.lib.gz
error: cannot create ./minirosetta_database/rotamer/ExtendedOpt1-5/cys.bbdep.rotamers.lib.gz
error: cannot create ./minirosetta_database/rotamer/ExtendedOpt1-5/his.bbdep.rotamers.lib.gz
error: cannot create ./minirosetta_database/rotamer/ExtendedOpt1-5/lys.bbdep.rotamers.lib.gz
error: cannot create ./minirosetta_database/sampling/fragpicker_rama_tables/H_dcP.counts.gz
error: cannot create ./minirosetta_database/sampling/orientations/orientgridall/data/c48u54799.grid.gz
error: cannot create ./minirosetta_database/sampling/spheres/sphere_17282_neighbors.dat.gz
error: cannot create ./minirosetta_database/scoring/score_functions/etable/etable.twobead.dlj.dat.gz
error: cannot create ./minirosetta_database/scoring/score_functions/goap/angle_table.dat.gz
error: cannot create ./minirosetta_database/scoring/score_functions/goap/dist_table.dat.gz
error: cannot create ./minirosetta_database/sequence/genome_9mers/Homo_sapiens.GRCh37.66.pep.all.9mers.sort.refscore.gz
error: cannot create ./minirosetta_database/sequence/genome_9mers/Mus_musculus.NCBIM37.66.pep.all.9mers.sort.refscore.gz
error: cannot create ./minirosetta_database/sequence/tcell_ep_9mers/HLA-DRB10701.refscore.gz
Unpacking WU data ...
Unpacking data: ../../projects/boinc.bakerlab.org_rosetta/fold_and_dock_6htube8_53_data.zip
Setting database description ...
Setting up checkpointing ...
Setting up graphics native ...
BOINC:: Worker startup.
Starting watchdog...
Watchdog active.
Continuing computation from checkpoint: chk_S_00006_FragmentSampler__stage1 ... success!
Continuing computation from checkpoint: chk_S_00006_FragmentSampler__stage2 ... success!
Continuing computation from checkpoint: chk_S_00006_FragmentSampler__stage3 ... success!
Continuing computation from checkpoint: chk_S_00006_FragmentSampler__stage4_kk_1 ... success!
Continuing computation from checkpoint: chk_S_00006_FragmentSampler__stage4_kk_2 ... success!

ERROR: std::abs( coordsys_rot.det() - 1.0 ) < 1e-6
ERROR:: Exit from: ......srccoreposesymmetryutil.cc line: 889

ERROR: Unable to open database file for Dun10 rotamer library: minirosetta_databaserotamer/ExtendedOpt1-5/cys.bbdep.rotamers.lib
ERROR:: Exit from: ......srccorepackdunbrackRotamerLibrary.cc line: 1145

ERROR: Energies:: operation NOT permitted during scoring.
ERROR:: Exit from: ......srccorescoringEnergies.cc line: 372
std::cerr: Exception was thrown:

[ERROR] EXCN_utility_exit has been thrown from: ......srccorescoringEnergies.cc line: 372
ERROR: Energies:: operation NOT permitted during scoring.

</stderr_txt>
]]>

feature request: currently target run time can be selected in even increments e.g. 2 hours, 4 hours, 6, 8, 10, 12, etc
however, i may like to specify 3,5,7,9 etc

could kindly allow the target run time to be selected for each hour instead rather than even hours?

that'd allow finer granuality to find the tradeoff between number of models completed each run, the processing prowess of each cpu and personal preferences dependent on the situation (e.g. the max run time available for the evening before deciding to shutdown the pc)

Hi! When Boinc screensaver is on with pictures of proteins, numeric details etc. I can see also infomation of the calculation and the project itself. What puzzles me is the discontinuity of the calculation. Even if the computer is obviousaly idle otherwise. The calculation starts and stops, starts and stops,
about a half second and a second each phase. >Is this normal < or is perhaps the antiviral surveillance program or the firewall defence (Avast, Comodo resp.) to be suspected? The os is Win 7 and Boinc v.7.4.27 x64.

-At least Comodo does some harm to Boinc and often isolates minirosetta (v.3.52) projects as unknown programs. I've decreased the safety level of Defence+ module and this seems help somewhat.

---

In order to ensure the majority of the idle computing power goes to useful work, the resources devoted to the graphic are limited, so it is not constantly refreshed.

In order to ensure the computing resources are available for whatever the primary purpose of the machine is, the tasks run at low priority, so if any other task on the machine pops in wanting CPU, it will take precedence. This can result in the CPU allocation being choppy as other, higher priority tasks request CPU.

---

Rosetta Moderator: Mod.Sense

I just got a new computation error. I recently switched to running work units for 2 days in the middle of running result 707976354 from one day, so I don't know if this is a problem caused by switching in the middle of the work unit or a bug in Minirosetta 3.52.

I just got a new computation error. I recently switched to running work units for 2 days in the middle of running result 707976354 from one day, so I don't know if this is a problem caused by switching in the middle of the work unit or a bug in Minirosetta 3.52.

No, I've not seen changing the runtime preference cause any problem. Only issue with that might be if you made it shorter than an active task had already run.

[edit]...But now I see similar errors on other tasks that tried to run with the 48hr runtime preference, so I've sent a note to the Project Team to look in to that. Appears the tasks have an internal runtime limit that may need to be extended to match the 48hrs (plus the 4hr watchdog).

Until they get a chance to resolve it, I'd suggest going back to the 24hr runtime preference.

---

Rosetta Moderator: Mod.Sense

I just got a new computation error. I recently switched to running work units for 2 days in the middle of running result 707976354 from one day, so I don't know if this is a problem caused by switching in the middle of the work unit or a bug in Minirosetta 3.52.

No, I've not seen changing the runtime preference cause any problem. Only issue with that might be if you made it shorter than an active task had already run.

[edit]...But now I see similar errors on other tasks that tried to run with the 48hr runtime preference, so I've sent a note to the Project Team to look in to that. Appears the tasks have an internal runtime limit that may need to be extended to match the 48hrs (plus the 4hr watchdog).

Until they get a chance to resolve it, I'd suggest going back to the 24hr runtime preference.

Thanks!

By the way, since you noticed that the 2 day limit apparently causes errors, you might want to have that option edited to tell users to not use it or better yet to remove that option and force everyone on the 2 day limit to the 1 day limit and announce why it was done on the message board and news sections.

Hi.

I just checked why my RAC has gone down, it seems to be because of these type of tasks are all getting Validate errors.

For my rigs and the others that have done the same tasks.

This is just a few that I found of mine.

=======================================

svm_above_15_v2_1Q9BA_abinitio_SAVE_ALL_OUT_236779_94


svm_both_v2_1M8AA_abinitio_SAVE_ALL_OUT_235545_52


svm_above_15_v2_1OKSA_abinitio_SAVE_ALL_OUT_236783_53


svm_both_3AUBA_abinitio_SAVE_ALL_OUT_235153_97

---