The Verilog-A standard (http://www.accellera.org/images/downloads/standards/v-ams/VAMS-LRM-2-4.pdf, section 3.2.1) states that module-scoped variables that have "desc" and/or "units" attributes should be considered "output variables". Output variables would typically be used for .OP output and other purposes.
ADMS does NOT set the "output" field of the variableprototype at all, even though the commentary in the adms.xml file indicates that this is what it should mean.
For Xyce, we're looking into how to add capability to our back-end to generate appropriate code to provide access to such variables from a netlist. Having this output field set right would have helped.
For the time being, we're working around it by having a little preprocessing template that sets the "output" flag ourselves. This is it:
One would simply apply this template at the top of a back-end to get all the output marking right.
It would be good if adms.implicit.xml did something like this already.
The Verilog-A standard (http://www.accellera.org/images/downloads/standards/v-ams/VAMS-LRM-2-4.pdf, section 3.2.1) states that module-scoped variables that have "desc" and/or "units" attributes should be considered "output variables". Output variables would typically be used for .OP output and other purposes.
ADMS does NOT set the "output" field of the variableprototype at all, even though the commentary in the adms.xml file indicates that this is what it should mean.
For Xyce, we're looking into how to add capability to our back-end to generate appropriate code to provide access to such variables from a netlist. Having this output field set right would have helped.
For the time being, we're working around it by having a little preprocessing template that sets the "output" flag ourselves. This is it: