Re: Verilog-AMS Committee Meeting Reminder - 25 Jan 2007

Hi, Marq -

In 3.1.1, option 2 suggests use of an attribute for marking
race conditions.  In 1364, attributes are not supposed to
be used for anything that can change simulation results;
they are in some sense "hints" to be used to help the
simulator perform more efficiently.  I think your option 2
would violate this definition.

The diode example (Ex 3 in 2.3) is not a very good one for
justifying multiple analog blocks.  For example, the 
initialization block would not satisfy Martin's need to
have a way to $strobe a warning about a parameter only
once -- unless you add some semantics about how to 
determine "sensitivity lists" for the blocks.  In the
noise section, the sensitivity list would indicate that
the block needs to be computed; if the pow() function 
causes a math error, is this reported even if not doing
a noise analysis?

I thought the more compelling example was the non-quasi-static
(NQS) part of the PSP mos model, where based on a parameter
(SWNQS) one could have 0 to 9 points in or the spline
collocation method (and, with use of idt(), each point might
require 2 internal nodes).

-Geoffrey

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.