AMSMinutes03Mar2011 < VerilogAMS

VerilogAMS Web>Meetings>AMSMeetingMinutes>AMSMinutes03Mar2011 (2011-03-04, DavidMiller) (raw view)EditAttach
Date: Thursday 3rd March 2011 <br /> <br /><strong>Attendees: </strong>
| Sri Chandra | Freescale |
| Dave Cronaur | Synopsys |
| Achim Bauer | EXL Modeling |
| Scott Morrision | TI |
| Graham Helwig | ASTC |
| David Miller | Freescale |
---+++ Discussion in todays call was centered around the recent enhancements that Achim put forward (Mantis: 3392)

*Enhancement #1:* request for an event driven solver for implicit non-linear equation systems. This sort of solver would be very useful with respect to initial parametrization and would allow us to map the high level input parameters into a low level representation. <br /> <br />Would also also optimisations where the equations inside the discrete event are not even solved unless the event fires. <br /> <br />Would constant UDF's allow you to do some of this? <br />Not really, having the initialization of certain functions using static input parameters is very limiting. <br /> <br />Achim to provide a more detailed proposal of what he would like to have for this enhancement. <br /> <br />A subrequest of this enhancement is to remove the restriction on the laplace/zi transform filters to contain "constant" pole/zero vectors. Scott mentioned that this is very useful for models that have characteristics of the filter changing over time. <br /> <br />This issue will be tracked separately, there doesn't seem to be any reason why these filters need this restriction. <br /> <br />Another possible change was to allow the use of the transform filters within the digital domain. <br />We would need to investigate this. <br /> <br /><strong>Enhancement #2:</strong> Dynamic arrays <br />Would this be useful. Sometimes it is painful to pre-determine the size of the array. It ends up that the user stores the largest array they ever need which can take up a lot of space. <br />Would be nice to be able to define the array size on the fly. <br /> <br />This is something that we will look at with SV merge. System Verilog has this concept as a Dynamic Array (Sect. 7.5 P1800-2009) <br /> <br /><strong>Enhancement #3:</strong> OOMR read&write for logic, real, electrical <br />Request is to remove the limitations from writing to OOMR's of analog quantities (branch, variables). <br /> <br />We currently have very strict limitations on OOMR's, specifically you can't access analog variables (read or write) and you can't assign to branches. (LRM 2.3.1 Sect: 6.7.1) <br /> <br />The reason these restrictions were put in place is because we couldn't resolve some of the issues before LRM 2.3 was finalised. <br /> <br />Most of the issues revolve around "race" conditions, and how to prevent them. <br />However "race" conditions exist in digital today. <br />Should we be trying to stop race conditions from occurring? Or is it simply a matter of user beware. <br /> <br />Specifically in analog, the race condition we are most concerned with, is when does the OOMR assignment take place? Does an OOMR assignment only take affect the next time step or does it modify the value of the object during the iteration cycle. If both a module and an OOMR are modifying a local variable, does the module assignment take precedence? <br /> <br /><strong>Enhancement 4:</strong> Bind <br />This is in the System Verilog language so will be part of the merged language. <br /> <br />However the concern is that the bind as defined in SV is quite static. It would be quite useful if we allowed a more flexible way to perform the bind with wildcards etc. (note, as I write these minutes, I am not very familiar with SV bind and the restrictions, so some research is needed). <br /> <br />However just to caution, we need to be very careful if we start discussing enhancements or changes to existing SV features. These may not be possible/accepted by the SV committee. <br /> <br />Our changes to bind may be also useful to pure SV, it may be something that we want to propose and pursue via that committee instead. <br /> <br />All of these enhancements are listed in Mantis item 3392: <br /> [[http://www.verilog.org/mantis/view.php?id=3392]] <br /> <br />David will update Mantis to split these enhancements into separate items to allow for individual tracking.

*Next Call*

The next call will be Thursday 17th March. <br /> <br />An agenda will be distributed two days prior to the call. <br /> <br /><strong>Dialin Details: </strong><br />San Francisco, 11.30a <br />Austin, 1.30p <br />Boston, 2.30p <br />Amsterdam, 8.30p <br />Tel Aviv, 9.30p <br />New Delhi, 1a (next day) <br />Adelaide, 6a <br /> <br /><strong>Call-In Details: </strong><br />USA Toll Free : 8008671147 <br />Australia Toll Free: 1800009128 <br />India Toll Free : 0008006501482 <br />Netherlands : 08002658223 <br />Passcode: 0970751#

-- Main.DavidMiller - 2011-03-04
Topic revision: r1 - 2011-03-04 - 20:56:37 - DavidMiller
VerilogAMS