ISSUES:

7/25/2000 meeting:

- The ".vcg" element is a Voltage Controlled Conductance. Stephen Nolan
  pointed out that the "dot" name does not conform to the convention that
  "dot" statements are not circuit elements. But the alphabet does not have
  enough letters to represent every element type with one initial letter, so
  the "dot" syntax is used as an escape to introduce longer type names.
  - ISSUE: Al will consider renaming ".vcg", especially since we reached
    consensus on NOT restricting ourselves to SPICE single letter type codes
    for elements.

- The word "Mosfet" after ".vcg" is an instance name. At this point Stephen
  Nolan started the discussion that lead to a consensus on part of the
  statement format.
  - ISSUE: Can connections be named instead of positional (Arpad)?
  - ISSUE: Where is whitespace required?
  - ISSUE: Should assignment expression values be quoted?
  - ISSUE: How do we format statements that are longer than the line limit?

- Mike questioned the "Vo=Vds" declaration, which means something like
  "Use the circuit node voltage Vo as the value for Vds in table lookups".
  Maybe the expression should be "Vds=Vo", since Vo is the given value and
  Vds is the symbolic variable? There are other examples of this "reversal"
  in the macro examples.
  - ISSUE: Al will consider changing this format.

- We reached consensus on use of the ".correlate" statement, details TBD.
  - ISSUE: Do ".correlate" parameter name patterns work like file globbing?
    Like regular expressions?

8/8/2000 meeting:

- ISSUE: Should pin be die in the "model_base" macro?
  Rpc     (pin power_clamp_ref)   I = POWER_Clamp[-V]

- ISSUE: We need to resolve how time will be handled. For elements that
  work with time parameters (such as the trigger), is time relative to
  a local event, or is it absolute simulation time?

- ISSUE: should we use !power_clamp_ref, or something more verbose
  like exist(power_clamp_ref,) or connected(power_clamp_ref) ? This
  relates to a general debate about whether we should be using
  syntax familiar to C programmers, or something less cryptic.

- Exactly what does the "inherit" keyword do?
  It copies in all statements from the base macro.
  ISSUE: How to "disinherit" element instances?
  ISSUE: Do named instances override inherited instance of the same name?

- The output of a trigger is a time value that can be used in the expressions
  of other elements. But what is the time value before the trigger triggers?
  This also leads us back to the issue of relative vs. absolute time.
  ISSUE: Al will consider time value of a trigger before it triggers

- ISSUE: We need to clarify how the simulator receives instructions for
  wiring macromodels into the entire simulation circuit. Since the macros
  can define any number of terminals, with any node names in any order,
  there must be some convention for this.

8/29/2000 meeting:

- One issue is the baggage of writing a parser that understands new IBIS
  format as well as the existing "sloppy" format:
  - A translator could be used to convert existing "sloppy" files to new
    format.
    - ISSUE: where will the code come from?