Leginon

"WVNicholson" wrote: I installed Leginon 1.4.1 on a new SUSE 10.3 system. When I run start-leginon.py it gets through the wizard at the start; but when I pick an application to launch it appears that it does not launch completely. The progress bar for launching the application never gets completed. (It stops part of the way through.) I've confirmed that this occurs with a number of the applications including Calibration, MSI-Edge and Manual. Also, the microscope and camera cannot be selected within the presets manager either when creating new presets or searching for old presets to import. In both cases the only option for TEM and CCD camera is "None",
William

I've just checked and it turns out the applications do start up completely if I do not select a client in the Leginon startup wizard. Obviously I will need to be able to successfully run when selecting a client for normal use (and also the only presets available when no client is selected are just those for a simulated microscope and camera),

William

"WVNicholson" wrote: > "WVNicholson" wrote: I installed Leginon 1.4.1 on a new SUSE 10.3 system. When I run start-leginon.py it gets through the wizard at the start; but when I pick an application to launch it appears that it does not launch completely. The progress bar for launching the application never gets completed. (It stops part of the way through.) I've confirmed that this occurs with a number of the applications including Calibration, MSI-Edge and Manual. Also, the microscope and camera cannot be selected within the presets manager either when creating new presets or searching for old presets to import. In both cases the only option for TEM and CCD camera is "None",
William

I've just checked and it turns out the applications do start up completely if I do not select a client in the Leginon startup wizard. Obviously I will need to be able to successfully run when selecting a client for normal use (and also the only presets available when no client is selected are just those for a simulated microscope and camera),
William

Also, I've noticed that I get errors from the client with a traceback that goes into wxPython. I was able to fix the problem by downgrading to an earlier version of wxPython. However, I now notice that presets appear to be broken in a different way - similar to those that occurred with an earlier upgrade to pyScope that were fixed then by modifying code relating to the energy filter. I suppose these problems have not been fixed in pyScope 1.0.8. I need to see if the earlier local modifications made to pyScope 1.0.6 can get pyScope 1.0.8 to work with our combination of hardware,

William

"WVNicholson" wrote: > "WVNicholson" wrote: > "WVNicholson" wrote: I installed Leginon 1.4.1 on a new SUSE 10.3 system. When I run start-leginon.py it gets through the wizard at the start; but when I pick an application to launch it appears that it does not launch completely. The progress bar for launching the application never gets completed. (It stops part of the way through.) I've confirmed that this occurs with a number of the applications including Calibration, MSI-Edge and Manual. Also, the microscope and camera cannot be selected within the presets manager either when creating new presets or searching for old presets to import. In both cases the only option for TEM and CCD camera is "None",
William

I've just checked and it turns out the applications do start up completely if I do not select a client in the Leginon startup wizard. Obviously I will need to be able to successfully run when selecting a client for normal use (and also the only presets available when no client is selected are just those for a simulated microscope and camera),
William

Also, I've noticed that I get errors from the client with a traceback that goes into wxPython. I was able to fix the problem by downgrading to an earlier version of wxPython. However, I now notice that presets appear to be broken in a different way - similar to those that occurred with an earlier upgrade to pyScope that were fixed then by modifying code relating to the energy filter. I suppose these problems have not been fixed in pyScope 1.0.8. I need to see if the earlier local modifications made to pyScope 1.0.6 can get pyScope 1.0.8 to work with our combination of hardware,
William

Yes, the energy filter code does seem to fix the later problem,

William