Hi Kevin, The $table_model() function currently provides two ways to specify the data - from a file or from an array. Most uses of the function that I've seen so far rely of a file source. Rather than dropping a file based data source I think we need to add flexibility and allow the use of other common data formats (and possibly introduce the concept of a table handle where we can hang not only the data but attributes of that data). The proposed meta-data may go directly in the data file or go in a separate file. The latter option provides backward compatibility with the 2.2 solution and may also be used with other formats (where you cannot modify the data file). I consider things like what interpolation scheme to use, how the extrapolate, etc to be attributes of the data and so it's natural to keep that information in one place with the data rather than on every $table_model() call. It also has the benefit of keeping the $table_model() call clean and simple. Regards, Patrick -----Original Message----- From: owner-verilog-ams@eda.org [mailto:owner-verilog-ams@eda.org] On Behalf Of Kevin Cameron Sent: Thursday, May 10, 2007 9:59 AM To: verilog-ams@eda.org Subject: Re: $table_model() requirements Can we do this without requiring a file format, i.e. can the $table functions just work off arrays and leave it up to the user how they populate those arrays (from files)? - you could just generate the table model directly as Verilog-AMS source, no need for splitting it into a Verilog wrapper around a .dat file - less chance you'll get the wrong file (or not find it). Kev. ... >> >> Hi All, >> >> It's been a long time since we discussed improving the $table_model() >> function in LRM 2.3 so I thought it would be best to start by reviewing all >> of the requirements gathered from the reflector and from users. Slides >> attached. >> >> Regards, >> Patrick >> >> Patrick O'Halloran >> Tiburon Design Automation >> > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.Received on Thu May 10 22:54:15 2007
This archive was generated by hypermail 2.1.8 : Thu May 10 2007 - 22:54:29 PDT