[ibis-editorial] Re: BIRD 127.4 vs. BIRD 140.2
- From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
- To: "ibis-editorial@xxxxxxxxxxxxx" <ibis-editorial@xxxxxxxxxxxxx>, 'IBIS-ATM' <ibis-macro@xxxxxxxxxxxxx>
- Date: Thu, 12 Jan 2012 08:06:36 +0000
Mike,
I tend to agree with Walter. The two statements are not
contradictory, and we can retain them both. There was
no scientific reason behind what went into these two BIRDs.
We simply didn't remember that we already wrote something
on it in the other BIRD.
What Walter actually did in his response is an "or-ing"
of the text in the two BIRDs which is in agreement with
the consensus we had when either of these BIRDs were written.
So for this reason I don't think that this question needs
to be brought back to the ATM committee...
Thanks,
Arpad
=============================================================
From: Walter Katz [mailto:wkatz@xxxxxxxxxx]
Sent: Wednesday, January 11, 2012 1:42 PM
To: ibis-editorial@xxxxxxxxxxxxx; Muranyi, Arpad; 'IBIS-ATM'
Subject: RE: [ibis-editorial] Re: BIRD 127.4 vs. BIRD 140.2
MM,
Both description of Value are not contradictory. The following is correct.
|* Value <value> Single value data.
|* The user may assign any value without any restrictions
|* within the constraints of the Type of the variable.
|* Note that Value and Default (defined below) are mutually
|* exclusive, and must not be used together for the same parameter.
Walter
From:
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
On Behalf Of Mirmak, Michael
Sent: Wednesday, January 11, 2012 2:28 PM
To: Arpad_Muranyi@xxxxxxxxxx<mailto:Arpad_Muranyi@xxxxxxxxxx>;
ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>; IBIS-ATM
Subject: [ibis-editorial] Re: BIRD 127.4 vs. BIRD 140.2
Thanks. Between the two BIRDs, which "Value" text should be retained? Also,
should the new "Format" description lines ("Where Format is optional...") be
retained?
|* Where Format is optional and <data_format> and <data> are required.
|* <data_format> and <data> must be substituted with one of the following:
|* Value <value> Single value data. Note that Value and Default
|* (defined below) are mutually exclusive, and must not be used
|* together for the same parameter.
Or
| Value <value> Single value data
?
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]>
On Behalf Of Muranyi, Arpad
Sent: Wednesday, January 11, 2012 10:29 AM
To: ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>; IBIS-ATM
Subject: [ibis-macro] Re: BIRD 127.4 vs. BIRD 140.2
Mike,
This was just an editorial oversight. When making suggestions
for changes, we usually quote blocks from the original (instead
of only the lines being changed) so that the reader would
understand the context better, and we mark the changed text with
asterisks "*" at the beginning of each line.
What happened here is that on BIRD 140.2 we quoted from the original
text a block and made changes to certain lines in that block, but
BIRD 127.4 was also making changes to the same block on different
lines.
In BIRD 127.4 we corrected the heading from:
| Format: (default is range)
to:
|* Format <data_format> <data>:
but in BIRD 140.2 we still quoted the original text and marked
this particular line unchanged because the changes in BIRD 140.2
were on different lines. This was simply an oversight, because
we probably forgot what BIRD 127.4 did in the same area.
Conclusion:
On this particular line, BIRD 127.4 should be kept for the new
version of the spec.
In different words, apply an "OR" function and use the changes
from both BIRDs... Please let me know if I am not clear on this...
Thanks,
Arpad
==================================================================
From:
ibis-editorial-bounce@xxxxxxxxxxxxx<mailto:ibis-editorial-bounce@xxxxxxxxxxxxx>
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]<mailto:[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx]>
On Behalf Of Mirmak, Michael
Sent: Wednesday, January 11, 2012 12:10 PM
To: IBIS-ATM; ibis-editorial@xxxxxxxxxxxxx<mailto:ibis-editorial@xxxxxxxxxxxxx>
Subject: [ibis-editorial] BIRD 127.4 vs. BIRD 140.2
(cross-posting to two lists, due to related subject matter)
BIRD 127.4 and BIRD140.2 both alter the same portion of Section 6c. The
affected text in both cases begins with the following line:
| Format: (default is range)
The relevant portions of both BIRDs are quoted below. The question: which BIRD
text reflects the current intent for IBIS 5.1?
- MM
BIRD127.4
-------------
On pg. 140 replace the following lines:
| Format: (default is range)
| Value <value> Single value data
| Range <typ value> <min value> <max value>
| List <typ value> <value> <value> <value> ... <value>
with these lines:
|* Format <data_format> <data>:
|*
|* Where Format is optional and <data_format> and <data> are required.
|* <data_format> and <data> must be substituted with one of the following:
|* Value <value> Single value data. Note that Value and Default
|* (defined below) are mutually exclusive, and must not be used
|* together for the same parameter.
| Range <typ value> <min value> <max value>
| List <typ value> <value> <value> <value> ... <value>
BIRD140.2
-------------
On pg. 140 replace these lines:
| Format: (default is range)
| Value <value> Single value data
| Range <typ value> <min value> <max value>
| List <typ value> <value> <value> <value> ... <value>
| Corner <typ value> <slow value> <fast value>
with these lines:
| Format: (default is range)
| Value <value> Single value data
|* The user may assign any value without any restrictions
|* within the constraints of the Type of the variable
| Range <typ value> <min value> <max value>
|* This defines a continuous range for which the user may
|* select any value greater than or equal to <min value>
|* and less than or equal to <max value> within the
|* constraints of the Type of the variable
| List <typ value> <value> <value> <value> ... <value>
|* This defines a discrete set of values from which the user
|* may select one value
| Corner <typ value> <slow value> <fast value>
|* The selection of one value is automatically carried out
|* by the EDA tool based on its internal simulation corner
|* setting
Other related posts:
