levylabpitt / asylum-api Goto Github PK

Initially, I just used the commands that I saw in the igor command help. I probably should have used the MFP3D XOP Help instead.

What happens when there are multiple instances of Igor installed? Igor v6, v8, v8 64 bit?

@Monkeymerlot the default branch is now main https://github.com/github/renaming. Run the following commands to update your local repository:

git fetch
git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

Using ARExecuteControl(ControlName, Panel, Value, Callback) we can essentially mimic a click event in the UI. The control name needs to be appended with _1 or some other number.

So to show the tip before we move it around, we can use

ARExecuteControl("ShowXYSpotCheck_1", "MasterPanel", 1, "")

Make icon more space efficient?

to:

I don't think error wire data flow is necessary for this function. I view this VI as a special case of "trim whitespace":

@ciozi137 I forgot to make this public before I transferred it over to levylab. Can you give me the access to the settings?

• Previously we were reading the scanner sensitivities from the "InfoBlock" with the command td_ReadValue("XLVDT Sens"). The cypher has a Sensitivity that depends on the sample height, as discussed in the document.
• Instead we should read the sensitivity from the "Global Variable" with the command GV("XLVDTSens") (this needs to be done every time the tip motor changes - it may be possible to use a callback from Igor to notify LabVIEW when it changes, but this is not necessary)
• The change to GV() will work for both the Cypher and MFP3D (the InfoBlock method only worked for MFP3D)

More discussion here:

• Cypher_LVDT_Sample_Height_Compensation-1.pdf
• Asana Discussion

I would like to reuse some of this code for making and modifying Igor graphs (the basic Igor functionality). Does it makes sense to break out the Igor-related part of this project into its own repository/package? And then make Asylum-API depend on "Igor-API".

Relevant VIs:

Currently, the software just returns the command in the debug mode. However, the IBW files that are created from the AFM store all the parameters of the instrument at the time of writing. In a new ReadIBWFile.vi function that I have been working on, I store these notes in a lookup table. I think that we could use this lookup table along with some more advanced logic to read and write these values etc. so that way we could have funcitonal inputs and outputs that changed based on the values input into the functions.

Populated LUT search:

Result:

I propose replacing code that uses large string concatenation,

with "Format into String" function:

I think it is easier to read the function that is being formatted, and has powerful features like automatically formatting numbers (%d, %f, etc) or timestamps (%<>T)

These VIs should be part of "Igor-API". At the very least they should be part of "Asylum-API", not part of Lithography package.