To download the examples for Module 5, click Module_5_Examples.zip.
In this topic:
There are several ways to pass parameters into subcircuits. In the previous topic, 5.0 About Parameters, you used the .GLOBALVAR statement to define a global parameter. A drawback to global parameters is that every instance uses the same parameter value. In this topic, you will learn how to pass parameters through the symbol-to-subcircuit interface, which allows you to pass the same parameter name with different values for each instance.
The single property method stores all model parameters on a single property as a parameter string. The individual parameter names and values are concatenated with an equal sign, then the three name-value pairs are joined with a space. The final parameter string is FC=10k R_VAR=1k GAIN=1.
In the first exercise, you will store a parameter string on a single symbol property and pass it into the subcircuit using the SIMPLIS_TEMPLATE property. This is the single-property parameterization method.
To use the single property method, you will add a PARAMETERS property with the parameter string value: FC=10k R_VAR=1k GAIN=1 and then add a SIMPLIS_TEMPLATE property to pass the PARAMETERS property to the subcircuit as a set of parameters.



Using the single property method, you have passed the PARAMETERS property value to the subcircuit using the SIMPLIS_TEMPLATE property. This explicit passing of parameters is a good design practice and makes symbols and models easier to understand.
The single-property and multi-property methods have several advantages and drawbacks as itemized below:
| Attribute | Single-Property | Multi-Property |
| Number of properties | Only one symbol property needs to be added for any number of parameters. | One property per parameter requires more work to define the symbol. |
| Symbol reusability | One symbol can work for multiple models since the number and parameter type can vary. | Symbols are customized to a model. |
| Editing speed with a dialog | Fast - one property to define. | Slower - multiple properties to define. |
| Ability to display individual parameters | Not possible - all parameters are displayed at once in a long parameter string. | Individual parameters can be displayed or hidden, which is a good reason to use the multi-property method. |
| Ease of manually editing the parameter values | Poor - need to search through the string for the correct parameters. | Easy - each property holds one parameter. |
The multi-property method of parameterization is the recommended approach. Despite the extra work to define a multi-property symbol, the result provides a better user experience since individual symbol properties can be displayed or hidden.
When the number of parameters exceeds 50, the single-property method is recommended since the parameter-editing scripts can save the properties to the symbol faster after the you close the dialog.
At the end of the module, please fill out the Module # 5 Evaluation form.