(r1) TDMMtgMinutesAug2211 < P10761

P10761 Web>ProjectsArea>ProjectTableDrivenModeling>TDMMtgMinutesAug2211 (revision 1) (raw view)~~EditAttach~~
-- Main.JoachimHaase - 2011-08-23
---++ IEEE P1076.1 Working Group - Table-Driven Modeling Project - Telco Meeting Minutes of August 22, 2011

*Status:* <em>approved on September 19, 2011<br /></em>

<br />%TOC%
---+++ Attendees
   * Arpad Muranyi
   * Ernst Christen
   * Joachim Haase (meeting convener, note taker)
---+++ Agenda
   * Call to order
   * Volunteer for minutes
   * Approval of agenda
   * Review and approve minutes from the last meeting
   * Discussion on action items of the last meeting
   * Discussion on VHDL Type to Hold Table Data (see paper of Ernst Christen)
   * Discussion on implementation for the 1D case
   * Next meeting
   * AOB
   * Adjourn
---+++ Call to order on August 22, 2011 at 8:05am PDT (17:05 CEST)

Joachim welcomes Ernst and Arpad.
---+++ Volunteer for minutes

Joachim takes the notes.
---+++ Approval of agenda

Agenda unanimously approved.
---+++ Review and approve minutes from last meeting

Ernst agreed to approve the Minutes of the June 14, 2011 meeting. The meeting announced for July 25, 2011 was cancelled.
---+++ Discussion on action items of the last meeting

Ernst prepared a paper "VHDL Type on Hold Table Data" ([[%PUBURL%/%WEB%/ProjectTableDrivenModeling/TDMTypes.pdf][pdf]]) on how to check possibilities to &bdquo;hide&ldquo; declaration of a type like TABLE_DATA_REAL in the standard proposal. Joachim started the work on the reference implementation.
---+++ Discussion on VHDL Type to Hold Table Data

Ernst presented his paper on "VHDL Type on Hold Table Data" ([[%PUBURL%/%WEB%/ProjectTableDrivenModeling/TDMTypes.pdf][pdf]]). There are two possible solutions
   * VHDL Composite Type
   * Protected Type

Data of a protected type could be hold by shared variables that can be updated in a process. Data of a composite type can be assigned to objects as constants and signals. Their internal structure cannot be hidden. However from a user's point of view, it seems that for the reference implementation the composite type should be preferred to hold the information of the run-time form.

Because the use of a composite type requires to fix the type declaration there remains a conflict concerning the requirements 5. and 6. of the cited paper
   * A user should be able to extend the standard by defining a setup subprogram to support an additional format of the raw data.
   * An implementor should be able to implement run time functions as efficiently as possible.

As a result of the discussion, this problem could be overcome in the following way
   * The reference implementation provides functions to evaluate objects saved in a run-time format.
   * The reference implemenation provides functions to convert data given in a raw format (e.g. as n-tupels) into the run-time data format.
   * There must be provided a setup function that converts Verilog-AMS readable files into the raw-data format.
   * It must be explained how the user can establish his own setup functions. However, these setup functions will not be part of the standard proposal.

Concerning the last topic, Ernst reminded the possibilities of the VHPI to start setup routines within VHDL/VHDL-AMS programs.
---+++ Discussion on implementation for the 1D case

Joachim presented slides on how to use functions for evaluation (LOOKUP_TABLE_DATA) and conversion (PREPARE_TABLE_DATA) ([[%PUBURL%/%WEB%/ProjectTableDrivenModeling/1076.1_table_driven_modeling_2011_08_22.ppt][meeting slides]]). The identifier LOOKUP_TABLE_DATA replaces the identifier INTERPOLATION_xD.
---+++ Next meeting

The next web meeting is planned on September 19, 2011 at 8am PDT or 17:00 CEST.
---+++ AOB

None.
---+++ Adjourn

Joachim adjourns the meeting at 18:05 CEST.
---+++ Action items

Joachim:
   * Update of the reference implementation
Topic revision: r1 - 2016-01-24 - 02:03:01 - TWikiGuest
P10761