Project

General

Profile

Actions
Copy link

Bug #3537

open

substack creation issue caused by mixed use of directq dictionary and sinedon data

Added by Priyamvada Acharya about 9 years ago. Updated about 9 years ago.

Status:
In Test
Priority:
Normal
Assignee:
Priyamvada Acharya
Category:
-
Target version:
-
Start date:
09/08/2015
Due date:
% Done:

0%

Estimated time:
Affected Version:
Appion/Leginon 3.2
Show in known bugs:
Workaround:

Description

Session: 15aug31a

Issue occurs when I try to make a substack by excluding some images from an aligned stack

Directory: /emg/data00/appion/pacharya/15aug31a/stacks/alignsub37

Last few lines of logfile:
Traceback (most recent call last):
File "/opt/myamisnap/bin/alignSubStack.py", line 293, in <module>
subStack.start()
File "/opt/myamisnap/bin/alignSubStack.py", line 285, in start
apStack.commitSubStack(self.params,included=includeParticle)
File "/opt/myamisnap/lib/appionlib/apStack.py", line 541, in commitSubStack
v = v.dbid
AttributeError: 'long' object has no attribute 'dbid'

Actions
Copy link
 #1

Updated by Anchi Cheng about 9 years ago

  • Project changed from 138 to Appion
  • Subject changed from stack creation issue to substack creation issue caused by mixed use of directq dictionary and sinedon data
  • Status changed from New to Assigned
  • Affected Version set to Appion/Leginon 3.2
Actions
Copy link
 #2

Updated by Anchi Cheng about 9 years ago

  • Status changed from Assigned to In Test
  • Assignee changed from Anchi Cheng to Priyamvada Acharya

r19137 checks whether the dictionray like object is sinedon data in which values in reference is another sinedon data, or a simple dictionary returned by directq.complexMysqlQuery which is a long integer.

Gabe, if you use the same mechanism at other places, this may happen as well.

Actions
Copy link

Also available in: Atom PDF