Same Job UIDs when running create_job()

Scripting
1

Dear CS team,

we sporadically experience problems when creating mutiple jobs via CS tools using create_job() inside the same project. In one case we got back the same job uid (J12170) from two different jobs:

  • one created 10:54:29 : volume import
  • and one created 10:55:00 : class_3D

The front end only displays the later job, started at 10:55:00.

Both were part of there respective workflows, where some import jobs (maps and particles) are followed by a big job, e.g. hetero_refine or class_3D. Having the same job_uid around multiple times causes problems since we are running checks against there status to continue other wrapper scripts.

I would like to flag that behaviour and ask if there are any ways in the future /version 5.0 to avoid it? We are running several thousand jobs per month via CS tools via our in-house pipeline. Currently we are still using version 4.7.1 for CS and CS tools.

Thanks

Ferdinand

2

@fkrupp Thanks for reporting. Please can you send us the tgz file created with the command

cryosparcm snaplogs

I’ll send you a PM with the email address.