Attendees:
  Mark Hahn, Cadence (Chair)
  Bob Dilly, IBM
  Jeff Handong, Cadence
  Vikas Sharma, IBM
New action items:
      Who         When     What
      ----------  ------   --------
 1.   Mark        5/4      Work with Jeff and Ed to come up with
                           the golden DCDL script for the demo
Open action items:
      Who         When     What
      ----------  ------   --------
 1.   Mark        4/20     Close on DAC demo participation from
                  -> 5/4   Synplicity, Altera
 2.   Bob         4/20     Determine whether an NDA is required for the
                  -> 4/27  library data
 3.   Mark        3/2      Add operating conditions to the taxonomy
                  -> 3/30
                  -> 4/13
                  -> 5/4
 4.   Mark        4/27     Send example of how the DAC demo subset
                  -> 5/4   would be extended with typical values
Closed action items:
      Who         When     What
      ----------  ------   --------
 1.   Mark        4/27     Send modified version of processor design
                           to IBM
Next Meeting:
  The next meeting will be a teleconference on 5/4
  from 9-11 am (PDT).
Details:
  1. Review action items
     The library NDA question is not yet fully resolved, but we're
     proceeding with the assumption that no NDA is required.
  2. Discuss typical values for environment conditions
     We talked briefly about this, pending completion of Mark's
     action item.  This will not be part of the DAC subset, in
     any case.  This is a complicated topic, involving multiple
     operating conditions, correlated versus uncorrelated variation,
     the ability to generate SDF, and the implications on the internal
     data structures required within tools.
  2. Discuss DAC demo
     The IBM library was successfully translated to TLF using a
     workaround.  Cadence will enhance the next version of the
     translator to address the limitations.
     IBM is mostly done with the support for the BuildGates
     commands in their translator, and adding the DCDL support
     is expected to take a couple of days.
     We talked about units: should there be default units or not?
     The advantage of having a default is that it's easier for
     designers when the default matches the units the designer
     wants.  The disadvantage is that the designer may not realize
     that the default doesn't match the units they want, leading
     to erroneous results.
     Mark proposed defining a set of default units, but requiring
     that the units be explicitly specified.  As a shorthand for
     saying that the default units are desired, there would be a
     "units -default" command.  We talked briefly about what the
     default values should be: time is a tricky one, because over
     the next couple of years the natural units for time will
     shift from ns to ps for many designs.  However, many libraries
     use ns today.
Thanks,
Mark
-- Mark Hahn phone: (408) 428-5399 Senior Architect fax: (408) 428-5959 Cadence Design Systems email: mhahn@cadence.com