I come from a background where pretty much all aspects of a simulation were controlled via scripts and not GUIs. Is there a way in OCEAN to define and manipulate the simulation views e.g. as the hierarchy is traversed use a Verilog-A model if found otherwise keep traversing until you find a primitive device model? You would also be able to accumulate a few such commands to define a default precedence followed by other commands targeting different hierarchical levels to explicitly define different precedences for those levels. For example, let the digital & timing blocks (and all of their hierarchy) be modeled in Verilog-A, let this analog block use a structural schematic view (made up of VCVS's etc.), and let the remaining analog signal chain blocks and all of their hierarchy be modeled as transistors (even though they may have existing Verilog-A models). You could quickly define and implement large scale changes to the simulation environment with just a couple commands. I find when I use GUIs that things can become obfuscated - in a script I can add comments and stuff to self-document the process and that kind of gets lost in the GUI world. I hope the above made sense...![]()
↧