*****************************************************************************
*****************************************************************************

BIRD ID#:        114.3
ISSUE TITLE:     IBIS-AMI Definition Clarifications
REQUESTER:       Arpad Muranyi, Mentor Graphics, Inc.
DATE SUBMITTED:  August 24, 2010
DATE REVISED:    September 8, 2010,  October 20, 2010,  November 8, 2010
DATE ACCEPTED BY IBIS OPEN FORUM:  December 10, 2010

*****************************************************************************
*****************************************************************************

STATEMENT OF THE ISSUE:

Section 6c of the IBIS v5.0 specification does not define several items
which leaves the parser developer, EDA vendor and model maker with
unanswered questions.

*****************************************************************************

STATEMENT OF THE RESOLVED SPECIFICATIONS:

Remove the following text from the beginning of the "DEFINITIONS" section
on pg. 140:

| DEFINITIONS: 
| 
| The following 'Usage, Type Format and Default definitions are used 
| throughout the following sections. 


Add to the beginning of the "DEFINITIONS" section the following text on
pg. 140:

| DEFINITIONS and RULES: 
|
| The information provided in this section is applicable to the content of
| the parameter definition file (.ami).   Note that the rules described
| below deviate from the rules for .ibs files.
|
| The content of the parameter definition file (.ami) is case sensitive.
|
| Only the pipe ("|") character is acceptable as a comment character
| regardless of what the calling IBIS file uses for the comment character.
|
| The line length of the parameter definition file (.ami) is not limited
| to a specific number of characters.
|
|*** The root name in the file may contain an arbitrary string and does not
| need to match the file name.
|
| A white space in the parameter definition file (.ami) may be one or more
| space, tab, and/or line termination characters.
|
| Integers are numbers which are written without a fractional or decimal
|*** component, and fall within -2147483648 and 2147483647.  If scientific
|*** notation is used then the exponent must be positive.  For example, 65,
|*** 7, and -756, 123e3 are integers, 1.6, 123e99 or 123e-2 are not integers.
|
| Float numbers are in general represented by a floating point number that
| may be scaled using a decimal exponent.  A floating point number is
| represented by the significant digits, and optionally a sign and decimal
| point.  For example, -1.23e-3, 123e-3, 1.23, 1 are all of type float.
|
|*** String is a sequence of ASCII characters enclosed in double quotes (").
|*** As defined in ANSI Standard X3.4-1986, the allowable ASCII characters
|*** consist of hexadecimal 20, 21, 23 to 7E, and the ASCII control
|*** characters 09 (HT), 0A (LF), and 0D (CR) for defining tabs and line
|*** termination sequences.  The double quote character 22 (") is not
|*** allowed inside string literals.

|
| Scaling factors or suffixes, such as p, n, etc... are not permitted in
| the parameter definition file (.ami).  Scientific and floating point
| notation is permitted.


On pg. 141 remove:

|                                                          ...The entire 
| line has to be limited to IBIS line length specification. String 
| literals begin and end with a double quote (") and no double quotes are 
| allowed inside the string literals. 


On the top of pg. 141 replace:

|                 (Rx_Clock_PDF
|                   (Usage Info)
|                   (Type Float)
|                   (Format Table
|                     (Labels Row_No Time_UI Density)

with:

|                 (Rx_Clock_PDF
|                   (Usage Info)
|                   (Type Float)
|                   (Format Table
|*                     (Labels "Row_No" "Time_UI" "Density")


On pg. 146 replace:

|               (Tx_Jitter (Usage Info)(Type Float)
|                          (Format Table
|                            (Labels Row_No Time Probability)

with:

|               (Tx_Jitter (Usage Info)(Type Float)
|                          (Format Table
|*                            (Labels "Row_No" "Time" "Probability")


On pg. 147 replace:

|               (Rx_Clock_PDF (Usage Info)(Type Float)
|                             (Format Table
|                               (Labels Row_No Time Probability)

with:

|               (Rx_Clock_PDF (Usage Info)(Type Float)
|                             (Format Table
|*                               (Labels "Row_No" "Time" "Probability")



*****************************************************************************

ANALYSIS PATH/DATA THAT LED TO SPECIFICATION

Most of these questions were raised by the IBIS v5.0 parser's developer
during the development of the parser, but other discussions in the IBIS-ATM
Task Group revealed additional questions and issues.  The solutions were
defined during the IBIS v5.0 parser development project and in subsequent
IBIS-ATM meetings.

BIRD 114.1 was issued because it was noted that the specification had
several examples which included "Labels" where the strings were not
enclosed in double quotes.  These examples became inconsistent with the
definitions regarding strings in BIRD 114.  BIRD 114.1 corrects this by
putting double quotes around these strings.

BIRD 114.2 was issued because there was a request for a clarification on
what characters are allowed in strings.  In addition, the mention of
Description and its line length rules was removed from this version of
the BIRD because this text is better placed under the description of
Description which is addressed in another BIRD.

BIRD 114.3 was issued with a few editorial modifications on the suggestions
made by Bob Ross and Radek Biernacki.

*****************************************************************************

ANY OTHER BACKGROUND INFORMATION:

An Adobe PDF version is available at:

http://www.eda.org/ibis/birds/bird114.1/bird114.1.pdf

*****************************************************************************