nSpec v0.22.1.1 External Release Notes
nSpec Version 0.22.1.1
Release Date:
Documentation Updated:
Major Features: Interlock Bug Fixes, Custom Exporter (JSON, KLARF, XML)
Overview
This patch build contains two main highlights:
Fixes for some Interlock Systems
Additional export file options for the Custom Exporter
As a patch build, QA testing has been limited to new feature tests, and did not include all regression tests.
Upgrading to v0.22.1.1
Library Update Not Required
If upgrading from a version more than 1 release prior, please reference all intermediate release notes for upgrade steps for each version.
New Features
Highlights
NSPEC-5594: New Custom Exporter Outputs (KLARF, JSON, XML)
The Custom Exporter launched in nSpec version v0.22.1.0 with support for CSV exports. With this change the Custom Exporter now supports KLARF, JSON, and XML exports as well. For full documentation on this feature please see the page at Custom Exporter
New Features Changelog
Bug Fixes
Highlights
NSPEC-6267: Interlocks don’t re-engage Stage
When the interlock on an enclosure unlocks, power is killed to the stage for safety reasons. However, when the door is shut and the interlock is locked again, the stage is not re-engaged until after the first motion. This causes a few problems:
The first scan after the interlock was touched was captured at the incorrect position
If the first motion is for an alignment job, first alignment mark will be missed
These problems have now been fixed! After open an interlock-equipped system door and closing it, stage motion will be immediately reset.
Make sure to set the program option in the PMD category called Use Interlock Recovery to 1
Changelog
Appendices
Custom Exporter
Overview
The Custom Exporter allows users to build highly customizable exports that report on all the desired defect information collected during any previously-run analysis. Like other analyses like the Custom Reporter and Dislocation Analyzer, the Custom Exporter requires an nJson file loaded with relevant SQL scripts.
Configuring the nJson File
The nJson file must be written and configured by Nanotronics Technical Service or Applications Engineers. To request a new custom reporting application that may require assistance, please contact support@nanotronics.ai to request support.
Core Features
CSV column headers are completely configurable. No matter what nSpec calls a defect attribute, users have the ability to rename them to align with the customer vernacular. For example, within nSpec databases we might refer to defect width as “W”, but in this export we can rename that to “width” or “defectWidth”, or anything else that is required for smooth integration with the user’s application.
Embedding math and custom calculations
In addition to simply exporting columns directly, the Custom Exporter will allow us to perform any operation that is legal within SQL code. This gives enormous flexibility in reporting exactly what is needed.
For more information on embedded calculations via the custom exporter, please contact the applications team.
Parameters
Param Name | Options |
|
|---|---|---|
Base Analysis IDs Mode | Absolute, Relative | See Post-Analysis Referencing for more information and usage. |
Base Analysis IDs |
| See Post-Analysis Referencing for more information and usage. |
Export Setting |
| Select a nJson file of the Report setting If you have a new request for a new functionality, please request support from support@nanotronics.ai |
Export Type | CSV, KLARF, XML, TDX, JSON, UserDefined | Export file format. See Custom Export File Formatting with String Templates if you choose to created a custom UserDefined file export. |
Export File Full Path |
| Dynamically name export files with string templates. See Export File Full Path Parameter for more information and usage. |
[DEPRECATED] Custom Filename Suffix | Optional | Deprecated with introduction of Export File Full Path parameter. If non-empty, this suffix will be directly added to filename. If using nSpec v0.23.1.0 or earlier, the suffix will be added following an underscore. |