![]() What would make this much simpler is if there were a way to just pass any extra arguments on, like most programming languages have some form of *args for functions accepting a variable number of parameters. Everywhere else, spectre is the preferred spelling. This makes a little bit of a headache when creating the macro model, since it looks like I would have to list *all* possible parameters with their default values. For the noun meaning a ghostly apparition or a haunting or disturbing image, American writers use specter. The params that are not specified presumably keep their default values according to the model definition. For example, a regular schematic simulation will specify a certain set of params, but an extracted view will have another (partially overlapping) set. ![]() There is no example on record of a sceptre having ever been actually handled by a Jewish king. The problem I'm running into is that the base transistor device has dozens of parameters, but only some of them are used depending on the context. As a symbol of authority, the use of the sceptre originated in the idea that the ruler was as a shepherd of his people ( Genesis 49:10 Numbers 24:17 Psalms 45:6 Isaiah 14:5 ). I'm then using User-CDF to effect a model swap when netlisting, calling the _macro instead of the base device. ![]() ![]() Something very much like the example from the Spectre reference manual for inline subcircuits. The word or phrase spectre refers to a mental representation of some haunting experience, or a ghostly appearing figure. I'm trying to create a custom parasitic wrapper for a transistor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |