Project

General

Profile

Forums » Leginon »

Configuration questions

Added by Morgan Beeby about 3 years ago

Hi Anchi,

I'm making slow progress upgrading to Leginon 3.5 for our Glacios (the Selectris remains in boxes awaiting an engineer to install it). I have a few questions on configuration.

1. Do you have a template fei.cfg for a setup like our Glacios with Falcon4EC and Ceta? (and Selectris to be installed imminently)

2. I wanted to sanity check on my instruments.cfg: I am putting our Ceta and Falcon4EC with the same Z-index. Presume this is OK?

[TEM]
class: fei.Glacios
cs: 2.7e-3

[Falcon4EC]
class: feicam.Falcon4EC
zplane: 50
width: 4096
height: 4096

[Ceta]
class: tia.TIA_Ceta
zplane: 50
width: 4096
height: 4096

3. Finally, when I run updatecom.py (which I understand is required after installing on a new instrument computer), I get the following error:

from win32com.client import selecttlb
Import Error: No module named win32com.client

Looking through Leginon bugfixes, I see a note that win32com.client was replaced with comtypes. Did I do something wrong somewhere...?

thanks,

Morgan


Replies (7)

RE: Configuration questions - Added by Anchi Cheng about 3 years ago

Hi, Morgan,

1. fei.cfg_glacios is attached.
The most important settings are 

# Lens normalization is usually set in TUI but there are cases that
# they are not desirable, for example on Talos column. This force
# the normalization after setting mag, spotsize, or beamsize differently.
FORCE_NORMALIZE_ALL_AFTER_SETTING = True

# Falcon image storage path if default does not work
FALCON_IMAGE_STORAGE_PATH = z:\TEMScripting\BM-Falcon\

You might not need the path set.

2. Your instruments.cfg looks fine. We sometimes put Falcon4EC at higher zplane so that we control its retraction and insertion timing since the automated one is not a blocking call.

3. You won't need to run updatecom.py any more. We use comtypes now. You can run checkcom.py for testing but it will generate python files when it is first used regardless.

RE: Configuration questions - Added by Morgan Beeby about 3 years ago

Thanks, Anchi,

We have VPP installed, so our objective aperture list is 100um, 70um, php1, php2, php3, php4, php5, php6, none.

I don't see any details on configuring for VPP on the wiki. Can I designate VPP in fei.cfg? (or do we switch to them outside of Leginon?)

thanks,

Morgan

RE: Configuration questions - Added by Anchi Cheng about 3 years ago

If you search phase plate in wiki, you should get several related pages. Here is a good starting page Volta_Phase_Plate_Usage

The control of phase plate, i.e., switching patch was done through AutoIt since that was all that was available. I did not switch to use TEM Advanced Scripting after the new option becomes available. I will add that as an option later.

When MSI-T-PP was developed, we could not change aperture automatically. Therefore, it was assumed that you use the same phase plate during the session. It is probably better that way, anyway so that you stay on-plane.

RE: Configuration questions - Added by Morgan Beeby about 3 years ago

Hi Anchi,

Sorry, I was vague in my previous post. I'm wondering about how to edit the following line in fei.cfg:

OBJECTIVE = 100, 70, 30, open

Can I simply replace with...

OBJECTIVE = 100, 70, php1, php2, php3, php4, php5, php6, open

...or do I need specific keywords other than arbitrary 'php1', etc?

Morgan

RE: Configuration questions - Added by Anchi Cheng about 3 years ago

Please use the names you see in your Aperture TUI tab.

RE: Configuration questions - Added by Anchi Cheng about 3 years ago

The AutoIt script for controlling apertures actually check your selection against the gui.

    (1-7/7)