Cryosparc live problems in v4.6.2

Hi,

We are having issues with running cryosparc live on one of our systems running 4.6.2. These files can be processed fine in the cryosparc job interface on this system and fail only in a live session. System has slurm installed. Files are EER movies. On three other different systems, one running 4.3.0 and the other two running 4.6.2 these files are able to be processed in live.

Any help would be appreciated to solve this, this is what we are getting in the job.log:

================= CRYOSPARCW ======= 2024-12-09 12:03:16.862227 =========

Project P20 Job J7

Master allspark.structbio.pitt.edu Port 39002

===========================================================================

MAIN PROCESS PID 1140532

========= now starting main process at 2024-12-09 12:03:16.862655

rtp_workers.run cryosparc_compute.jobs.jobregister

MONITOR PROCESS PID 1140534

========= monitor process now waiting for main process

========= sending heartbeat at 2024-12-09 12:03:18.613453

Exception ignored in: <cyfunction Prefetch.del at 0x7fca2ad168e0>

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 74, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.del

AttributeError: ‘Prefetch’ object has no attribute ‘handle’

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/jobs/rtp_workers/run.py”, line 100, in cryosparc_master.cryosparc_compute.jobs.rtp_workers.run.RTPExposureCache.prefetch_exposure

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 41, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.init

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 94, in cryosparc_master.cryosparc_compute.blobio.prefetch.validate_read_parameters

AssertionError


Transparent hugepages setting: [always] madvise never

========= sending heartbeat at 2024-12-09 12:03:28.632482

Exception ignored in: <cyfunction Prefetch.del at 0x7fca2ad168e0>

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 74, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.del

AttributeError: ‘Prefetch’ object has no attribute ‘handle’

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/jobs/rtp_workers/run.py”, line 100, in cryosparc_master.cryosparc_compute.jobs.rtp_workers.run.RTPExposureCache.prefetch_exposure

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 41, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.init

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 94, in cryosparc_master.cryosparc_compute.blobio.prefetch.validate_read_parameters

AssertionError

========= sending heartbeat at 2024-12-09 12:03:38.652097

Exception ignored in: <cyfunction Prefetch.del at 0x7fca2ad168e0>

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 74, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.del

AttributeError: ‘Prefetch’ object has no attribute ‘handle’

Traceback (most recent call last):

File “cryosparc_master/cryosparc_compute/jobs/rtp_workers/run.py”, line 100, in cryosparc_master.cryosparc_compute.jobs.rtp_workers.run.RTPExposureCache.prefetch_exposure

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 41, in cryosparc_master.cryosparc_compute.blobio.prefetch.Prefetch.init

File “cryosparc_master/cryosparc_compute/blobio/prefetch.py”, line 94, in cryosparc_master.cryosparc_compute.blobio.prefetch.validate_read_parameters

AssertionError


========= main process now complete at 2024-12-09 12:03:45.159638

Total: 21.092s

MAIN THREAD:

@jcoleman Please can you post a screenshot of the affected Live session Configuration section’s Parameters panel (with the Show advanced box checked).

Ah, I think you solved it. Thank you! The EER upsampling factor was set accidentally to -1. That would do it. It is now running as expected. Could there be something printed out that would tell the user that this was set to a nonsensical value?

You are right! We made a note of that.