When creating custom elements, users can add customized properties to the Compound Elements and Scripted Elements. The customized properties can also be added to Root Elements, but this is generally not used for creating custom elements.
To add a new property to the above mentioned elements, user can either edit the element and use the "Add" button in the "Property Editor" window or, use the addproperty command.
User defined properties have the same general format as primitive properties. However, compared to the latter, all the fields of the Property Editor can be modified for user defined properties.
Since 2019a release, INTERCONNECT enabled the protected property option for Root Element, Compound Element and Scripted Element.
The protected properties are especially useful when building compact models and running Monte Carlo (MC) analysis. When a property is protected, end users cannot see, list or read the property through GUI or script environment, but this property can still be accessed and varied by the simulator in the MC analysis tool. Post-processing and correlation analysis in MC analysis tool will only be provided for generated results.
Enable protected property
To protect a property, users can open the element Edit window and check the corresponding "Protect" box or use the script command protectproperty . After protecting the property, it will be hidden and be invisible for all script commands except for the protectproperty command.
When an element with protected properties is packaged and published, the protected properties then cannot be accessed by any manner, except in Monte Carlo analysis for variations. This is especially useful for varying process data in Monte Carlo analysis, while at the same time the process data and its variation are protected.
Vary protected property in Monte Carlo analysis
Once the element is packaged and published, its protected properties can only be accessed by the .lib file in Monte Carlo analysis. The variation is defined in the .lib file as by the normal way through "model" or "lotgroup". The following example is modified based on the Monte Carlo analysis example in the page Monte Carlo analysis .
We created a Compound element out of the "SW1" element and defined its "model" as "protectWGD". Then we created a new property in the Compound element and named it as "group_index", and passed its value to "SW1" "group index 1". Then we protected the property "group_index" and it became hidden.
In the wgd_protected.lib file, we define the variation of the model "protectWGD" property "group_index" as shown below:
.LIB sigma_1 .LOTGROUP group_a=(uniform,0.2) .MODEL protectWGD "group_index"=2 lotgroup=group_a library="" .ENDL
Create a new Monte Carlo (MC) analysis "MC lib" and upload this wgd_protected.lib file to it. Because the property "group_index" is protected so it won't be shown in the MC Master table. The following figures are the same Monte Carlo simulation with variation on the same property, protected and unprotected, respectively.
Run the MC analysis and the property variation will be invisible but the MC analysis result variation will be shown in the results as normal (Fig 3.). The MC analysis with unprotected property will have the property variation shown together with the result variation (Fig 4.).
Since 2018a release, INTERCONNECT enabled the hide property option for Root Element, Compound Element and Scripted Element.
Hidden properties cannot be seen in the element Property View window but can be accessed through script by "set" commands and "get" commands. Users can hide a property by checking the "Hide" option in the element's Editing window or by using the hideproperty command.