Done tab closes the exe. completely

[aditi-nethwewala]

Done function is used under few cases:

To stop the lithography in between ( I think we discussed making abort button functional regarding this)
Once we are done using the AFM
Sometimes before writing the barriers, we need to press done and restart the program, otherwise the program does not respond to making the small barriers properly (ot sure why, can be interpolation distance problem too or something else)

[Monkeymerlot]

Re Cases:

1. Abort should do this properly now, but you will need to test it.
2. This is when this function should be used. The program should stop and exit. Closing the exe completely is the expected functionality in this case. In the development environment, it is expected to finish and stop execution.
3. Please open up a new issue with the Label "Type: Bug" for this. That should not be happening and we shouldn't need to abort the software to get this to run properly.

To add onto number two, it not possible for the program to shut down and window stay open with an exe. Windows (Microsoft) can only draws programs that are running. You can go the other way around and tell windows to stop drawing a window for a period of time (intended for use when dragging and dropping, taking screenshots etc) but you cannot force it to draw something that doesn't exist.

[aditi-nethwewala]

I will create a new issue, but I think this is a difficult one to figure out. Also, it does not happen all the time. I will test the rest.

[Monkeymerlot]

Clarification on 2: when I say the development environment is expected to "finish", it will abort the lithgraphy with a hard abort. Ie a forced shutdown.

[Monkeymerlot]

@aditi-nethwewala can you try writing a small barrier that smaller than half of the interpolation distance? I think I might have found the bug that you are talking about.

Here is the old driver's interpolation if the distance was twice the length:

And the new driver also suffers this fate:

Thankfully there is a fix:

Also what are the units for interpolation on the front panel? I realized I never scaled them so nothing is probably going to work unless you scale them manually yourself as they are currently in meters...

[aditi-nethwewala]

Interpolation distance is in micrometers, so I think the above mentioned thing shouldn't be an issue. We keep our interpolation distance to be 0.001 um which is 1 nm for writing max. 50 nm wide barriers.

[Monkeymerlot]

Ok but you will still need to put them in in as meters for now in the new driver.

[aditi-nethwewala]

Ok, right now I am just testing the programs, not making it open for everyone. Also, I suggest to change it in the next version. Two reasons:

• we do not want to do unnecessary conversions, right now it is nice because we enter interpolation in the order of um and nm
• we want to keep few things consistent with before and not cause confusion, interpolation distance would be one of them

[Monkeymerlot]

Oh I totally agree, it'll definitely be fixed before the next release. I just dont want you to not be able to do anything while you're testing.