Project

General

Profile

Bad array shape during Bright correction

Added by Bob Grassucci over 8 years ago

We are getting a bad array shape error when trying to do a bright field correction. See below.

More details. When we collect at the same format on the K2 in counting but shorter exposure time we get the correct image array back. 100000ms works, 600000ms works, 800000ms does not.

File "/usr/local/lib/python2.7/site-packages/leginon/correctorclient.py", line 577, in storeCorrectorImageData
raise RuntimeError('%s: bad array shape: %s' % (type, shape,))
RuntimeError: bright: bad array shape: (0, 0)


Replies (9)

RE: Bad array shape during Bright correction - Added by Bob Grassucci over 8 years ago

we have used the 600 sec bright image for correction. It is an interesting observation that could be related to data trasfer. Thanks.
Bob

RE: Bad array shape during Bright correction - Added by Anchi Cheng over 8 years ago

I think there is a limit to exposure time, or simply how many frames Gatan software can process. Try taking an image in Digital micrograph for 800000 ms. It probably won't let you set that number at all.

From gain reference point of view 8 of 100000 ms image gives the same count statistics as one 800000 image. So you can get around this problem that way.

RE: Bad array shape during Bright correction - Added by Bob Grassucci over 8 years ago

We have used 800 sec before and it worked which is why I was concerned. If we have problems we will take 8 X 100 sec exposures.

RE: Bad array shape during Bright correction - Added by Bob Grassucci over 8 years ago

We got another occurrence of zero array shape when leginon was in the targeting node. I have attached a screen capture. thanks.
Bob

RE: Bad array shape during Bright correction - Added by Anchi Cheng over 8 years ago

Did you observe any error log in DM ? Zero-size array is returned to Leginion usually when DM is not able to give back the image.

RE: Bad array shape during Bright correction - Added by Bob Grassucci over 8 years ago

I don't think so but the results file is very long. Is there a specific message I should be looking for?

RE: Bad array shape during Bright correction - Added by Anchi Cheng over 8 years ago

No much idea. "Error" ? Might be able to match timestamp.

RE: Bad array shape during Bright correction - Added by Bob Grassucci over 8 years ago

I am not seeing any obvious time stamp unless the format is: 1030.668 which is a sequential number printed in the result file but what that is in the real world I am not seeing how to translate that to 3:47:57. There are many places where error is printed with this context.

SetupFileSaving called with flags 0 rf 3 frf 3 MRC fpi N pix 1.000000 ER N A2R N sum 65535 grab 0
copy NO
dir W:\frames\ root dummy
1631.592 DMCamera Debug : Trying to create W:\frames\
1631.607 DMCamera Debug : SetupFileSaving error is 12

There is nothing obvious in the results file.

RE: Bad array shape during Bright correction - Added by Anchi Cheng over 8 years ago

error 12 has to do file saving permission which may be a bug since the files are saved. I will have to think of another way to debug.

    (1-9/9)