@AndreGraca
Thanks for your patience while we were working on a response (and the code).
The update_all_job_sizes()
was not intended to be manually run, but it may be help in your specific case.
You will want to ensure
- The current CryoSPARC version. At the time of writing, this is v4.4.1 with patch 240110 for v4.4.1 applied. The 240110 includes an update of the
update_all_job_sizes()
function and requires a CryoSPARC restart after patching. - Confirm with reference to the command_core log
that the automatic run ofcryosparcm log command_core | grep -e "update_all_job_sizes + \| Finished updating all"
update_all_job_sizes
at the CryoSPARC startup is complete, based on the timestamp. Look for a log entry like
that is newer than the latest CryoSPARC restart.2024-01-11 22:52:29,322 update_all_job_sizes_run INFO | Finished updating all job sizes (0 jobs updated, 0 projects updated)
- Open a terminal for monitoring the command_core log, in which you run
whose output should automatically be updated as new command_core log entries are recorded.cryosparcm log command_core
- In another terminal, run
This command should immediately “go into the background”, but may take a long time to run.cryosparcm cli "update_all_job_sizes()"
- Monitor, in the former terminal window, the progress and completion of the command you entered in the latter terminal window.
[Edited (again) 2024-01-11]