Bug #4794: Need more than 3 values to unpack error during data collection - Leginon - Electron Microscopy Group

Actions

Copy link

Bug #4794

closed

Need more than 3 values to unpack error during data collection

Added by Ed Eng almost 8 years ago. Updated almost 7 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Target version:

Start date:

02/28/2017

Due date:

% Done:

Estimated time:

Affected Version:

Appion/Leginon 2.2.0

Show in known bugs:

Workaround:

Description

2017/02/28
Collecting at -30 degree tilt
Session: 17feb28b

Priyamvada encountered a few errors:

preset request to "hln" failed, waiting 60 seconds to try again
Move to target failed: unable to set instrument
need more than 3 values to unpack

No errors within Leginon clients. Sequenced paused within K1n_Z_Focus sequence at hln step.

Restarted Leginon and continuing data collection.

Files

Download all files

Screenshot-8.png (117 KB) Screenshot-8.png		Ed Eng, 02/28/2017 11:37 AM
Screenshot-9.png (163 KB) Screenshot-9.png		Ed Eng, 02/28/2017 11:37 AM
201720308-1037-Leginoncomerror (183 KB) 201720308-1037-Leginoncomerror		Ed Eng, 03/10/2017 11:42 AM
20170308-1558_Leginon_alpaerror.png (549 KB) 20170308-1558_Leginon_alpaerror.png		Ed Eng, 03/10/2017 11:42 AM

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Anchi Cheng almost 8 years ago

Status changed from New to Assigned

lost communication to scope. may need to add a retry.

Actions

Copy link

Updated by Anchi Cheng almost 8 years ago

unpack error may be in pyscope/tecnai.py _setStagePosition function unpacking exc. Need to check on scope

Actions

Copy link

Updated by Anchi Cheng almost 8 years ago

Project changed from 138 to Leginon
Subject changed from Leginon error during Krios1 tilt data collection to Need more than 3 values to unpack error during data collection
Affected Version set to Appion/Leginon 2.2.0

The root problem is lost of communication to COM, resulting a COMError. The exception raised do not seem to have a fixed format or has been changed since the pyscope code handling it was written.

Actions

Copy link

Updated by Alex Noble almost 8 years ago

I can confirm that for the past 3-4 months this error has been showing up during tilt-series collection on Krios1 and has increased with time. I don't think I've seen it on Krios2, and I'm pretty sure I haven't seen it on non-Krios scopes. When Krios1 gets a PM this should be brought up.

Actions

Copy link Download all files