Date: 1st Oct 2009 Dave Cronauer, Synopsys Geoffry Coram, Analog Devices Martin O'Leary, Cadence Dave Miller, Freescale * Meeting was focused on reviewing "Cleanup" Mantis items in AMS-LRM-2.4_DraftA. The following items were discussed: Item 831 - No issues. Item 848 - No issues. was addressed as part of LRM 2.3.1 Item 874 - No issues. Item 876 - The sentence is a little ambiguous. Does identical mean same length or "token for token" identical. Believe that the intention is for it to be "token for token" identical. A simple example would probably be best. Item 1638 - Needs further discussion. Concern was that by changing values in constants.vams would void extractions done with the old values. One suggestion was to have specific defines: `define P_K_SPICE 1.38062e-23 `define P_K_NIST_1998 1.3806503e-23 `define P_K_NIST_2002 1.3806505e-23 An alternative would be to have `ifdef macros, that the user could set before sourcing in constants.vams: `ifdef NIST_1998 ..... `elsif NIST_2002 ...... `else ..... `endif -=-=-=-=-=-=-= `define NIST_2002 `include "constants.vams" For now the change will be reverted till this is addressed. Item 2567 - No issue. We match SV LRM for this rule. Item 2792 - Wrong change, $monitor should be yes for both analog and digital. 2843 $monitorb/h/o and $monitoron/$monitoroff should be yes for digital, no for analog. Was also suggested to include a sentence explaining when a $monitor will fire in Analog. i.e.Once the timestep is accepted, $monitor will only fire if the value is different from the last timestep. It won't fire during iterations when values may vary while converging. Item 2803 - No issues. Change is to remove restriction on probing unnamed flow branches and port branches via OOMR. Item 2806 - No issues. Cheers... Dave -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Wed Oct 7 07:02:31 2009
This archive was generated by hypermail 2.1.8 : Wed Oct 07 2009 - 07:02:54 PDT