[ibis-macro] Re: AMI_Flows_6.pdf for today's ATM teleconference

  • From: "Muranyi, Arpad" <Arpad_Muranyi@xxxxxxxxxx>
  • To: "IBIS-ATM" <ibis-macro@xxxxxxxxxxxxx>
  • Date: Tue, 20 Apr 2010 15:30:40 -0700

Ambrish,
 
I think Walter has a point in what he is saying.  The
two sentences in his quote:
 
"|                                               When
| Use_Init_Output is set to "True", the EDA tool is
| instructed to use the output impulse response from the
| AMI_Init function when creating the input waveform
| presented to the AMI_Getwave function."
 
 
"| If the Reserved Parameter, Use_Init_Output, is set to
| "False", EDA tools will use the original (unfiltered)
| impulse response of the channel when creating the input
| waveform presented to the AMI_Getwave function."
 
can be interpreted as if the output of the Init function(s)
is only passed to the GetWave function when this Boolean
is true.  The problem is that these two sentences do not
say anything about what goes from one Init function into
the next Init function, which is what Walter's argument is
all about.
 
I have this feeling that this text was written when the
order of execution was still Tx_Init, Tx_GetWave, Rx_Init,
Rx_GetWave, and when the order was changed to Tx_Init,
Rx_Init, Tx_GetWave, Rx_GetWave we didn't realize that
this text had to be adjusted also.
 
However, whatever the order of the function calls is, the
principle I see in this is that the Boolean has a "bypass
effect" on the Init function, i.e. either use its output
or its input for whatever follows it.
 
With that interpretation and the description in Section 10 2.3
my flow diagram from today seems to be correct.
 
Arpad
===============================================================
 
 
 

________________________________

From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Ambrish Varma
Sent: Tuesday, April 20, 2010 5:11 PM
To: IBIS-ATM
Subject: [ibis-macro] Re: AMI_Flows_6.pdf for today's ATM teleconference



Hi Walter,

I don't believe the spec ever mentions that the input to Rx_Init is
always hAC(t) X hTEI(t). In fact, quite the contrary - 

 

| Step 2. The output of Step 1 is presented to the TX model's AMI_Init 

| call. If Use_Init_Output for the TX model is set to True, the 

| impulse response returned by the TX AMI_Init call is passed 

| onto Step 3. If Use_Init_Output for the TX model is set to 

| False, the same impulse response passed into Step 2 is passed 

 |     on to step 3.

 

| Step 3. The output of Step 2 is presented to the RX model's AMI_Init 

| call. If Use_Init_Output for the RX model is set to True, the 

| impulse response returned by the RX AMI_Init call is passed 

| onto Step 4. If Use_Init_Output for the RX model is set to 

| False, the same impulse response passed into Step 3 is passed 

| on to step 4.

 

This is what Arpad presented today.

-Ambrish.

 

 

________________________________

From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx] On Behalf Of Walter Katz
Sent: Tuesday, April 20, 2010 5:27 PM
To: Arpad_Muranyi@xxxxxxxxxx; IBIS-ATM
Subject: [ibis-macro] Re: AMI_Flows_6.pdf for today's ATM teleconference

 

Arpad,

 

In the IBIS 5.0 specification:

 

|               Use_Init_Output:

|

|               Use_Init_Output is of usage Info and type Boolean.  When

|               Use_Init_Output is set to "True", the EDA tool is

|               instructed to use the output impulse response from the

|               AMI_Init function when creating the input waveform

|               presented to the AMI_Getwave function.

|

|               If the Reserved Parameter, Use_Init_Output, is set to

|               "False", EDA tools will use the original (unfiltered)

|               impulse response of the channel when creating the input

|               waveform presented to the AMI_Getwave function.

|

|               The algorithmic model is expected to modify the waveform
in

|               place.

|  

|               Use_Init_Output is optional. The default value for this

|               parameter is "True".

|

|               If Use_Init_Output is False, GetWave_Exists must be
True.

 

In what was agreed to in November, the input the Rx_Init was always
hAC(t) X hTEI(t).

In what you presented this week, the input to Rx_Init is either hAC(t)
or hAC(t) X hTEI(t), depending on the value of Tx Use_init_Output. I
believe based on the IBIS 5.0 specification above that the November flow
is correct and the Spec. correction flow that you presented this week is
incorrect.

 

Walter

 

Walter Katz

303.449-2308

Mobile 720.333-1107

wkatz@xxxxxxxxxx

www.sisoft.com

 

-----Original Message-----
From: ibis-macro-bounce@xxxxxxxxxxxxx
[mailto:ibis-macro-bounce@xxxxxxxxxxxxx]On Behalf Of Muranyi, Arpad
Sent: Tuesday, April 20, 2010 12:48 AM
To: IBIS-ATM
Subject: [ibis-macro] Re: AMI_Flows_6.pdf for today's ATM teleconference

 

Here is the AMI_Flows_6.pdf file once again.  I made

the changes which were suggested to me in the last ATM

meeting.  This flow includes only the correction we

wanted to make on the existing spec flow.

 

I am not sure what the decision was about the last two

slides which deal with the Rx pad waveform.  Did we

say we would delete these slides altogether and not

address this capability in this BIRD?  As far as I can

tell, we can't achieve this flow without deconvolution...

 

Please familiarize yourselves with these slides, because

I would like to achieve closure on this flow in the ATM

teleconference tomorrow.  Comments are welcome before or

at the meeting.

 

Thanks,

 

Arpad

=========================================================

 

________________________________

From: Muranyi, Arpad 
Sent: Tuesday, April 13, 2010 1:39 PM
To: 'IBIS-ATM'
Subject: AMI_Flows_6.pdf for today's ATM teleconference

For those who are unable to join the meeting via

LiveMeeting, here is a new flow diagram to aid the

discussion on the subject.

 

Arpad

==================================================

Other related posts:

  1. Home
  2. ibis-macro
  3. Archive
  4. 04-2010