Attendees:
  Mark Hahn, Cadence
  Tim Baldwin, Cadence
  Bob Dilly, IBM
  Jim Engel, IBM
  Vassilios Gerousis, Infineon
  Vikas Sharma, IBM
New action items:
      Who         When     What
      ----------  ------   --------
 1.   Mark        10/26    Revise the operating conditions proposal
Open action items:
      Who         When     What
      ----------  ------   --------
 1.   Bob, Vikas  5/25     Review the GCF 2.0 draft on operating conditions
                  -> 7/6
                  -> 8/10
                  -> 9/28
                  -> 10/12
 2.   Mark        7/27     Prepare Microsoft Project schedule for the
                  -> 11/9  second half of '99.
 3.   Tom         10/12    Prepare skeleton for the DCDL spec
                  -> 10/15
 4.   Tom         10/12    Try to get permission to use diagrams from the
                           Velocity documentation
Closed action items:
      Who         When     What
      ----------  ------   --------
 1.   Mark        10/12    Send GCF 2.0 draft to Tom
 2.   Bob         10/12    Prepare a proposal for DCDL operating conditions
                           commands
 3.   Mark        10/12    Prepare a proposal for DCDL commands to specify
                           physical supply names and the relationship between
                           them and logical/library rails
Next Meeting:
  The next meeting will be a teleconference on 10/26
  from 9-11 am (PDT).
Details:
  1. Review action items
     Jim Engel and Mark sent proposals for the operating conditions
     to the reflector.
     Bob Dilly sent an item on DC-WG to the ESNUG mailing list, although
     this hasn't appeared yet.
     We talked again about including wildcards in the DCDL standard,
     and there was good support for doing so, to avoid a large increase
     in constraint file size as tools read and then write out constraints.
  2. Discuss operating conditions proposals
     We had a good discussion on this, with general agreement with Mark's
     proposal.  Supporting back-annotation of instance-specific voltage
     and temperature values in DCDL was a question raised in the proposal,
     and there was agreement that DCDL should.
     There were a few issues that still need to be addressed:
       - whether and how to specify a 4 point analysis
         (min best case, max best case, min worst case, max worst case)
       - whether and how to specify three operating points for
         use in generating SDF min:typ:max triplets.
     After some discussion, sentiment was leaning towards supporting the
     4 point and 3 point specifications in a similar way as described in
     the GCF 2.0 draft.  Mark took an action item to update the proposal
     to address this.
Thanks,
Mark
-- Mark Hahn phone: (408) 428-5399 Senior Architect fax: (408) 428-5959 Cadence Design Systems email: mhahn@cadence.com