Exposure targetting threshold display
Added by Bob Grassucci about 10 years ago
We are getting the error below when trying to display the threshold image in exposure targetting. This is still MSI-T 1.6. I suspect some problems with the data base connection as we are also getting strange behaviors elsewhere since we upgraded the Polara to 3.0.
Traceback (most recent call last):
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/SelectionTool.py", line 158, in onDisplay
self._setDisplayed(evt.name, evt.value)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/SelectionTool.py", line 152, in _setDisplayed
self.parent.setImage(image)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanel.py", line 297, in setImage
self.setNumericImage(imagedata)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanel.py", line 373, in setNumericImage
self.contrasttool.setRange((stats['min'], stats['max']), value)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanelTools.py", line 245, in setRange
self.setSliders(value)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanelTools.py", line 196, in setSliders
self._setSliders(value)
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanelTools.py", line 179, in _setSliders
self.minslider.SetValue(self.getSliderValue(value0))
File "/usr/local/lib64/python2.6/site-packages/leginon/gui/wx/ImagePanelTools.py", line 223, in getSliderValue
return int(round((self.slidermax - self.slidermin)*scale + self.slidermin))
ValueError: cannot convert float NaN to integer
Replies (2)
RE: Exposure targetting threshold display - Added by Anchi Cheng about 10 years ago
Bob,
While this error itself is a scaling problem, the basis of the problem is probably that it is not getting the images or dark reference correctly so the array it is trying to
display has all values as NaN (not a number). Confirm that you can get a raw image in Correction Node.
Does this old version uses the same database as the new version ? If so, it is a very bad combination whenever it needs to do a query because all the dbschema updates that are performed for 3.0 is undermined by the new insert of the old version data.
If you must keep some instrument on the old version, could you separate the database (and web server to go with it) ? For good and bad, Leginon database is tightly coupled with its version, especially with major update like this.
RE: Exposure targetting threshold display - Added by Bob Grassucci about 10 years ago
Anchi,
That is what I suspected as all of these new issues started when we upgraded the F30 to 3.0. We were waiting to upgrade the F20 in a step wise fashion to ensure the new version was stable but probably caused more problems by having 2 separate versions then we avoided. We will upgrade the F20 ASAP. Thanks.
Bob