Ambrish,
Thanks for yet another draft :)...
The sentence you undeleted:
"When the DC_Offset is usage InOut, the output value of DC_Offset may return a
different value by Rx AMI_Init."
was deleted because it didn't provide any additional information to what we
already know about InOut parameters, namely that the model can return a
different value from what was passed into the model. I don't mind keeping
this sentence, as it does no harm, but what is still missing is a real
DEFINITION
for what the MEANING of this output value is. I thought we made it clear in
our discussion in the meeting that we had to state that the output value was
associated with the Rx GetWave output waveform (as opposed to being
associated with the channel's step response waveform), and I thought you
wrote something into this area during the meeting that I can't find in this
version now. Why did that disappear?
Thanks,
Arpad
==============================================================
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx] ;
On Behalf Of Ambrish Varma
Sent: Tuesday, August 27, 2019 4:20 PM
To: 'IBIS-ATM' <ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] Latest version of DC_Offset BIRD
Hi All,
Attached is the latest version of the BIRD after today's discussion and edits
in the meeting.
I have deleted 1 more line in the Usage Rules as it felt redundant.
I also undeleted this line: 'When the DC_Offset is usage InOut, the output
value of DC_Offset may return a different value by Rx AMI_Init.'
as it clearly says how the DC_Offset value is returned (in the AMI_Init).
Please let me know if there are any comments/questions.
Thanks,
Ambrish.
