Best way to parse cryosparc log files / project folders?

[marinegor]

Hi everyone,

after posting this request, I’m actually thinking that the prototype could be easily implemented myself, based on the cryosparc folder structure and state of the log files for each job.

Hence, I’m curious if the standard cryosparc module has any build-in methods to fetch the project/job info, or I must try parsing the log files manually? Sure the log files are just simple text files, but it probably would be better to re-use already existing code for that matter.

[wtempel]

Please can you list the specific information items that you seek to extract.

[marinegor]

For starters, it’d be nice to have:

• a job status – if it has completed or failed.
• who created the project, workspace and the job – to send the notifications only to the people in need.

[wtempel]

@marinegor

a job status – if it has completed or failed.

cryosparcm cli "get_job_status()"

@marinegor

who created the project, workspace and the job – to send the notifications only to the people in need.

• project info:
  cryosparcm cli "get_project()" (look for "owner_user_id":)
• job info:
  cryosparcm cli "get_project('P1','J2','created_by_user_id')"
• workspace info:
  cryosparcm cli "list_workspaces()" (look for "created_by_user_id": of each listed item)
• user lookup:
  cryosparcm cli "get_email_by_id()"

This is just a sample of possibly useful functions (methods); cryosparcm cli just one way to call them. You may alternatively write python scripts that you could execute like:
cryosparcm call python <path_to_script> (see related post).

[marinegor]

Thanks, I’ll try working with that!