1)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7851)
Posted 5 Sep 2024 by mikey Post: I STILL get this error on all my pc's!! Stderr output <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_m_pred_alpha_358.zip </stderr_txt> ]]> |
2)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7661)
Posted 15 Jun 2024 by mikey Post: Mikey said: The other thing I'm seeing is that the Ralph tasks are taking about 10gb of ram for EACH task so I had to limit my running tasks accordingly. I'm running 1 cpu core per task and they are taking over 2 days to finish. I'm still getting some errors but have not ruled out it being a pc problem as yet. Grant SSF said: The most i've seen for a CPU processed Task in use is a bit over 1.5GB. mikey said: Application Generalized biomolecular modeling and design with RoseTTAFold All-Atom 0.02 Name RF_SAVE_ALL_OUT_NOJRAN_IGNORE_THE_REST_validation_env_g_pred_171_16903_6 State Running Received 6/14/2024 3:05:08 AM Report deadline 6/15/2024 3:05:09 AM Estimated computation size 80,000 GFLOPs CPU time 00:03:30 CPU time since checkpoint 00:03:30 Elapsed time 1d 07:17:48 Estimated time remaining --- Fraction done 100.000% Virtual memory size 12.77 GB Working set size 4.75 GB Directory slots/16 Process ID 8508 Progress rate 3.240% per hour Executable w_0.02_windows_x86_64.exe |
3)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7659)
Posted 15 Jun 2024 by mikey Post: Already done that, but just using max_concurrent. Even so, that doesn't limit the number of threads per Task, just the number of Tasks.There needs to be a way to limit the number of threads a single Task can use. Thank you, I will un-suspend the Project then. |
4)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7658)
Posted 15 Jun 2024 by mikey Post: Rosettafold doesn't suspend whend told do. give it time, mine does the same thing but does suspend eventually |
5)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7657)
Posted 15 Jun 2024 by mikey Post: Look at the Einstein GPU tasks, they use BOTH the cpu and gpu. Just like Ralph, precisely no difference.That shows just how confused you are. The GPU processes the Task, the CPU supports the GPU by keeping it fed. The CPU doesn't actually do any processing, the GPU does that. Depending on the Task, with a very well written application, CPU support can be next to nothing. Actually Peter is right about the Einstein gpu tasks, the newer tasks pause gpu crunching for a bit at 2 different times and process stuff on the cpu then go back to running more of the task on the gpu again. They said the reason is the gpu isn't as accurate as the cpu is and they need the more accurate cpu numbers. |
6)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7622)
Posted 15 Jun 2024 by mikey Post: There needs to be a way to limit the number of threads a single Task can use. And at the moment, the indications are that 1 Task using 8 threads performs no better than when 12 Tasks were trying to use 8 threads each, when there were only 12 threads available. I'll keep an eye on things to see if they don't slow down later, but the initial signs are that the extra threads are providing not even the slightest improvement in processing time- they're just being wasted.[/quote] Try this: <app_config> <project_max_concurrent>1</project_max_concurrent> </app_config> Save it as 'app.config.xml' in each project folder in C:programdata/boinc/projects/project name and adjust the number to reflect how many tasks of each project you want to run, ie 1 of this project, 2 of that project and 7 of that project. The other thing I'm seeing is that the Ralph tasks are taking about 10gb of ram for EACH task so I had to limit my running tasks accordingly. I'm running 1 cpu core per task and they are taking over 2 days to finish. I'm still getting some errors but have not ruled out it being a pc problem as yet. |
7)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7554)
Posted 13 Jun 2024 by mikey Post: Mine are using almost 6gb of ram for EACH task so that could be why some are failing, I had to limit the 8 that were running to only 3 because of the ram usage but those 3 ARE running into the 3+ minutes so far!! |
8)
Message boards :
RALPH@home bug list :
RoseTTAFold All-Atom
(Message 7512)
Posted 30 May 2024 by mikey Post: I got 43 tasks and every single one of them errored out like this task: 5439065 4838692 30 May 2024, 0:25:01 UTC 30 May 2024, 0:57:18 UTC Error while computing 0.00 0.00 --- Generalized biomolecular modeling and design with RoseTTAFold All-Atom v0.00 windows_x86_64 https://ralph.bakerlab.org/results.php?hostid=49186&offset=0&show_names=0&state=6&appid= |
9)
Message boards :
Feedback :
Ideas for a better Ralph
(Message 7049)
Posted 2 Sep 2021 by mikey Post: One more thing I would love to see if finer control over the tasks we get ie the option to unselect the 9 day Theory tasks as some pc's just can't finish them in time. |
©2024 University of Washington
http://www.bakerlab.org