Bug #3537
opensubstack creation issue caused by mixed use of directq dictionary and sinedon data
0%
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'
Updated by Anchi Cheng over 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
Updated by Anchi Cheng over 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.