Fatal error: Uncaught TypeError: Unsupported operand types: string / int in /projects/boinc/ralph/html/project/project_specific_prefs.inc:53 Stack trace: #0 /projects/boinc/ralph/html/project/project_specific_prefs.inc(157): get_time_str() #1 /projects/boinc/ralph/html/inc/prefs_project.inc(266): project_specific_prefs_show() #2 /projects/boinc/ralph/html/inc/prefs_project.inc(291): prefs_show_project_specific() #3 /projects/boinc/ralph/html/user/prefs.php(60): print_prefs_display_project() #4 {main} thrown in /projects/boinc/ralph/html/project/project_specific_prefs.inc on line 53

What is crazy is when they use a DEPRECATED function and then say that it will only work with the latest drivers.
I am glad they released this screwed up binary on Ralph rather than releasing this junk on Rosetta.

C:ProgramDataBOINCprojectsralph.bakerlab.orgcv1rf2aautil.py:450: UserWarning: Using torch.cross without specifying the dim arg is deprecated.
Please either pass the dim explicitly or simply use torch.linalg.cross.
The default value of dim will change to agree with that of linalg.cross in a future release. (Triggered internally at C:cbpytorch_1000000000000workatensrcATennativeCross.cpp:66.)
  Z = torch.cross(Xn,Yn)

my tasks page shows that i have 3 tasks in progress, but BOINC on the computer shows only one. Nothing in transfers

Sounds like what's known as Ghost Tasks.
Some sort of network issue during contacting the Scheduler & getting the work. The Scheduler thinks you got it, but you didn't.


Looking at my Tasks i've had some weirdness as well.
I had a Task error out with the reason being "Timed out - no response", that was after only 8 minutes after getting it...

I got 6 units of the latest batch and all errored out after 4 seconds because of an access code violation. Same fate for my wingmen. Windows 10, RTX 4080, 32 GB RAM. Anybody who managed to finish off a bunch of them care to share your system details?

<core_client_version>8.0.2</core_client_version>
<![CDATA[
<message>
The access code is invalid.
 (0xc) - exit code 12 (0xc)</message>
<stderr_txt>
C:ProgramDataBOINCprojectsralph.bakerlab.orgcv2rf2aautil.py:450: UserWarning: Using torch.cross without specifying the dim arg is deprecated.
Please either pass the dim explicitly or simply use torch.linalg.cross.
The default value of dim will change to agree with that of linalg.cross in a future release. (Triggered internally at C:cbpytorch_1000000000000workatensrcATennativeCross.cpp:66.)
  Z = torch.cross(Xn,Yn)
usage: predict.py [-h] [-checkpoint CHECKPOINT] [-pdb PDB] [-silent SILENT] [-tmpl_chain TMPL_CHAIN]
                  [-tmpl_conf TMPL_CONF] [-movescale MOVESCALE] [-n_pred N_PRED] [-n_cycle N_CYCLE] [-no_extra_l1]
                  [-no_atom_frames] [-outcsv OUTCSV]
predict.py: error: unrecognized arguments: -z .venv_j_pred_alpha_92.zip

</stderr_txt>
]]>

Target computation time is set at 1 hour.

The 4 running tasks are still "running" with zero estimated time left after 32 hours. I want to just kill the tasks, but also have a bit of morbid curiosity to see if they will actually finish...