Leginon

Hi, Cheri,

The error is unusual.

Will need a lot more information. In which application, in which node, and what you did in the step before that error pops up? Were you trying a custom camera configuration?

What camera do you have? would it allow more than 4096 pixels? Send me directly also a screenshot of the error and log around it and the settings of that node or the preset it is acquiring the data would help, too. I don't think you can post images here.

Anchi

Hi, Cheri,

From the screen shots you sent, I noticed that you have assigned a number of bad column and rows. The error message comes after Leginon loaded the references. Therefore, my guess is that you might have an out of range column or row assigned in your correction plan. Please check them to find out if I am right.

The coordinates in Leginon is that of python list/sequence. Its index starts at 0 and end at n-1 where n is the number of items in the list. Therefore, for 4096x4096 image, you can only have 0-4095.

Hope I am right or there is a serious problem with the way Leginon work with your camera.

Anchi

Hi, Cheri,

Jim and I did a search on mysqldump you sent and found a bad pixel stored in the database as (3264,4097) at 2010-06-07 15:20:42.
That was the problem. You probably clicked on it by accident. From the database, you have cleared out bad pixel list on 2010-06-08 13:43:24. Therefore, the problem should have gone away by now.

Jim has made changes to the current 2.0 branch and our development trunk so that in the future, these accidents won't get saved.
Sorry that we have not made it more accident safe.

Anchi