Michael,
I would make the changes now on the working "draft7", but hold off
announcing or uploading it
This is really a minor change in the Example to clarify the string content
for an Out parameter.
I do not know if anything else needs to be stated to clarify this.
Bob
From: ibis-editorial-bounce@xxxxxxxxxxxxx
[mailto:ibis-editorial-bounce@xxxxxxxxxxxxx] On Behalf Of Mirmak, Michael
Sent: Thursday, January 12, 2023 9:37 AM
To: Randy Wolff; weston.beal@xxxxxxxxxxx; walter.m.katz@xxxxxxxxx; Muranyi,
Arpad; ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: [EXT] Re: PAM_Thresholds interpretation
Thanks! Do we want to make those two edits now? Or wait until next week?
* MM
From: Randy Wolff <rrwolff@xxxxxxxxxx>
Sent: Thursday, January 12, 2023 9:35 AM
To: weston.beal@xxxxxxxxxxx; walter.m.katz@xxxxxxxxx; Mirmak, Michael
<michael.mirmak@xxxxxxxxx>; Muranyi, Arpad <arpad.muranyi@xxxxxxxxxxx>;
ibis-editorial@xxxxxxxxxxxxx
Subject: RE: [EXT] [ibis-editorial] Re: PAM_Thresholds interpretation
I agree with Walter's suggestion of "0.0". If we touch that section again,
I'd also like to see the ending ")" moved to the previous line in all new
PAMn examples for consistency with other AMI parameter examples.
Michael, I added your 3 more items to the change list doc and will keep
track of that document for now.
Thanks,
Randy
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Beal, Weston
Sent: Thursday, January 12, 2023 8:08 AM
To: walter.m.katz@xxxxxxxxx; Mirmak, Michael <michael.mirmak@xxxxxxxxx>;
Muranyi, Arpad <arpad.muranyi@xxxxxxxxxxx>; ibis-editorial@xxxxxxxxxxxxx
Subject: [EXT] [ibis-editorial] Re: PAM_Thresholds interpretation
CAUTION: EXTERNAL EMAIL. Do not click links or open attachments unless you
recognize the sender and were expecting this message.
I agree that making the value a single number or empty string would help the
implication of a value. I often look at the examples in the specification as
a guide to what syntax a file should have. Even if it's not required, the
example text should be the common usage.
Later,
Weston
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of walter.m.katz@xxxxxxxxx
Sent: Thursday, January 12, 2023 7:52 AM
To: michael.mirmak@xxxxxxxxx; Muranyi, Arpad (DI SW EBS PST AV)
<arpad.muranyi@xxxxxxxxxxx>; ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: PAM_Thresholds interpretation
All,
Note the example for PAM_Thresholds:
(PAM_Thresholds (Usage Out) (Type String)
(Description "Thresholds for waveform and eye processing.")
(Value "0.00 0.00 0.00")
)
And PAM_Offsets
(PAM_Offsets (Usage Out) (Type String)
(Description "Clock timing offsets for waveform and eye processing.")
(Value "0.0e-12 0.0e-12 0.0e-12 0.0e-12")
They could both have a single value of "0.0"
Walter
Walter Katz
720.417-3762
walter.m.katz@xxxxxxxxx
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Mirmak, Michael
Sent: Wednesday, January 11, 2023 8:50 PM
To: arpad.muranyi@xxxxxxxxxxx; ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: PAM_Thresholds interpretation
I elected to use Arpad's version, but can switch as the group decides.
Enclosed please find the updated draft 6.
Note that, in addition to the modified PAM_Thresholds text, we need to add
three more items to the Change list:
* Table 28 updated for PAM_Thresholds requirements
* Figure 44 caption added and related broken cross-references fixed
* Minor grammatical corrections (e.g., inappropriate use of
"parentheses" rather than "parenthesis" in some areas, at least one
incorrect dash when an underscore was needed)
Hopefully that's it.
* MM
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Muranyi, Arpad
Sent: Wednesday, January 11, 2023 5:41 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: PAM_Thresholds interpretation
All,
I just saw Walter's email from about 4 hours ago (it landed in my junk box
for some reason).
His response and mine are pretty much in agreement using different wording.
I prefer my
wording but I am not stuck on it, as long as the message is that the EDA
tool takes what the
model returns (and not what is in the .ami file's placeholder).
Thanks,
Arpad
============================================================================
From: Mirmak, Michael <michael.mirmak@xxxxxxxxx>
Sent: Wednesday, January 11, 2023 7:17 PM
To: Muranyi, Arpad (DI SW EBS PST AV) <arpad.muranyi@xxxxxxxxxxx>;
ibis-editorial@xxxxxxxxxxxxx
Subject: RE: PAM_Thresholds interpretation
Arpad,
This certainly makes sense.
I have made all the other corrections needed and am ready to distribute the
updated file once we decide this issue.
* MM
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Muranyi, Arpad
Sent: Wednesday, January 11, 2023 3:11 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] Re: PAM_Thresholds interpretation
Weston, and Everyone,
Reading that sentence in context tells me that instead of:
"The EDA tool uses the voltages passed in through this parameter"
we should have written:
"The EDA tool uses the voltages returned by the executable model through
this parameter"
The reason I think this is because the first sentence in "Definition" says:
"Voltages used by EDA tools for PAMn waveform and eye processing."
and combining that with the parameter being Usage Out, the only way
the EDA tool can receive this value is if it is returned by the executable
model.
If we agree on this, I would suggest that Michael should change this
sentence as I propose above.
Thanks,
Arpad
==============================================================
From: ibis-editorial-bounce@xxxxxxxxxxxxx
<ibis-editorial-bounce@xxxxxxxxxxxxx> On Behalf Of Beal, Weston
Sent: Wednesday, January 11, 2023 3:18 PM
To: ibis-editorial@xxxxxxxxxxxxx
Subject: [ibis-editorial] PAM_Thresholds interpretation
All,
After Walter asked about the interpretation of the PAM_Thresholds parameter
this morning, I thought I should look into it to increase my understanding.
While the specification does not explicitly say that the string in the AMI
file must contain anything, the description and the example imply that the
string should have n-1 numbers in it. The description says, "The EDA tool
uses the voltages passed in through this parameter", which implies to me
that the string value in the AMI file should have n-1 numbers in it. Then in
the example code the string has 3 numbers in it.
(PAM_Thresholds (Usage Out) (Type String)
(Description "Thresholds for waveform and eye processing.")
(Value "0.00 0.00 0.00")
)
Maybe this needs a BIRD to clarify that the Value in the AMI file is only a
placeholder and the string value is ignored. On the other hand, the
description and the example imply that the model might use these numbers in
some way. This conflicts with the Usage Out syntax. So, either way, it seems
to be inconsistent.
Regards,
Weston
