| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Hi Mike,
Can you explain then your comment #308 against draft 3.0, in which you proposed to eliminate reference to the 0.45 and 0.55 position of the zero crossing ? I interpreted this suggestion as an acknowledgement that the position of the histogram is not necessarily
tied to the middle of the eye, as determined by the sampling phase selected to reconstruct the eye.
Laurent
![]() From: Mike Dudek <mdudek@xxxxxxxxxxx>
Sent: Saturday, July 11, 2026 2:10 PM To: norm.swenson@xxxxxxxx <norm.swenson@xxxxxxxx>; Alloin, Laurent <laurent.alloin@xxxxxxxxxxxxxxxxxxxxxxxx>; 'Hansel DSilva' <Hansel.D'Silva@xxxxxxxxxxxxxxxx>; 'Richard Mellitz' <richard.mellitz@xxxxxxxxxx>; Mahadevan, Amitkumar <amahadev@xxxxxxxxx>; 'Roberto Rodes' <roberto.rodes@xxxxxxxxxxxx>; 'Mark Nowell (mnowell)' <mnowell@xxxxxxxxx>; 'Ali Ghiasi' <ali@xxxxxxxxxxxxxxxxx>; 'Adee Ran (aran)' <aran@xxxxxxxxx>; miguangcan@xxxxxxxxxx <miguangcan@xxxxxxxxxx>; 'Adam Gregory' <adam.gregory@xxxxxxxxxx>; 'Heck, Howard' <howard.heck@xxxxxx>; 'Samuel Kocsis' <Samuel.Kocsis@xxxxxxxxxxxxxxxx>; 'Ahmad El-Chayeb' <ahmad.el-chayeb@xxxxxxxxxxxx> Cc: STDS-802-3-B400G-OPTX@xxxxxxxxxxxxxxxxx <STDS-802-3-B400G-OPTX@xxxxxxxxxxxxxxxxx>; STDS-802-3-B400G-ELEC@xxxxxxxxxxxxxxxxx <STDS-802-3-B400G-ELEC@xxxxxxxxxxxxxxxxx> Subject: Re: [EXTERNAL] RE: [**EXTERNAL**] RE: IEEE 802.3 TDECQ: Clarification on Histogram Window positioning
I agree with Norm's interpretation and also have a comment to delete "nominally".
From: norm.swenson@xxxxxxxx <norm.swenson@xxxxxxxx>
Sent: Saturday, July 11, 2026 09:03 To: 'Alloin, Laurent' <laurent.alloin@xxxxxxxxxxxxxxxxxxxxxxxx>; 'Hansel DSilva' <Hansel.D'Silva@xxxxxxxxxxxxxxxx>; 'Richard Mellitz' <richard.mellitz@xxxxxxxxxx>; Mike Dudek <mdudek@xxxxxxxxxxx>; 'Mahadevan, Amitkumar' <amahadev@xxxxxxxxx>; 'Roberto Rodes' <roberto.rodes@xxxxxxxxxxxx>; 'Mark Nowell (mnowell)' <mnowell@xxxxxxxxx>; 'Ali Ghiasi' <ali@xxxxxxxxxxxxxxxxx>; 'Adee Ran (aran)' <aran@xxxxxxxxx>; miguangcan@xxxxxxxxxx <miguangcan@xxxxxxxxxx>; 'Adam Gregory' <adam.gregory@xxxxxxxxxx>; 'Heck, Howard' <howard.heck@xxxxxx>; 'Samuel Kocsis' <Samuel.Kocsis@xxxxxxxxxxxxxxxx>; 'Ahmad El-Chayeb' <ahmad.el-chayeb@xxxxxxxxxxxx> Cc: STDS-802-3-B400G-OPTX@xxxxxxxxxxxxxxxxx <STDS-802-3-B400G-OPTX@xxxxxxxxxxxxxxxxx>; STDS-802-3-B400G-ELEC@xxxxxxxxxxxxxxxxx <STDS-802-3-B400G-ELEC@xxxxxxxxxxxxxxxxx> Subject: [EXTERNAL] RE: [**EXTERNAL**] RE: IEEE 802.3 TDECQ: Clarification on Histogram Window positioning
Prioritize security for external emails:
Confirm sender and content safety before clicking links or opening attachments
Hi Laurent
Adding the reflectors to try to save time discussing this at the face-to-face meeting.
The sentences under discussion in D3.1 are: “Two vertical histograms are measured through the eye diagram, nominally centered 0.05 UI before and after sampling phase \phi_0 … The precise time position of the pair of histogram windows is adjusted to minimize TDECQ while keeping the histogram windows spaced 0.1 UI apart." I do agree that the second sentence was in D3.0 and I recall discussing the meaning of it with you in Munich. I interpret that sentence a bit differently than you do. You believe this means optimizing the taps at \phi_0 then sliding the two histogram windows across the entire \phi_0 -T/2 to \phi_0 + T/2 range to find their optimal location. (Please restate if I have not stated your position accurately.) I interpret those sentences to place the histogram windows, separated by 0.1UI, approximately centered at \phi_0 (from the word nominally) and make fine adjustments as necessary to optimize the symbol error rate. I do not interpret that to mean sliding the center of the windows across the entire unit interval.
I am interested in how others interpret those sentences. Again, since we are searching for the best \phi_0, I don’t think this adjustment of the histogram locations is necessary, which is why I have comments suggesting that the word “nominally” and the second sentence should be deleted. But if others disagree, I think we should try to make the meaning of those sentences clear so that there is no ambiguity in how it should be interpreted.
Regards, Norm
From: Alloin, Laurent <laurent.alloin@xxxxxxxxxxxxxxxxxxxxxxxx>
Yes, Norm,
I think that this degree of freedom has been part of the specification for a long time, and the zero-crossing reference in the figure was obsolete for some time. I must admit it was before my time, but I see that this degree of freedom brings benefit when the transmitter has group delay distortion or when equalized eyes show some nonlinear skew, which a well-designed receiver can take advantage of. But foremost, I believe that at this point, we do not want to change the measurement results of the TDECQ specification as compared to what it yields prior to the effort of rewriting the specification for clarity, which I think was your goal in Draft D3.1.
Laurent
PS: The exert of D3.0 spells out clearly that this degree of freedom exists in the prior specification.
From:
norm.swenson@xxxxxxxx <norm.swenson@xxxxxxxx>
HI Laurent
Do you interpret that line to mean that you choose a \phi_0 (at which you optimize the taps), you place the windows at \phi_0 +/- .04T and measure TDECQ there, then you scan the center of those windows across the entire range of 0 to T, but keep the same \phi_0 for the tap optimization purposes? That adds yet another parameter to search over and I am not sure that buys us anything.
I believe the original TDEC or TDECQ did not have that in there, as they assumed zero crossings defined 0UI and 1UI, and the histograms were placed around the midpoint between 0UI and 1UI. So I am not so sure that that wisdom would apply here.
Regards, Norm
From: Alloin, Laurent <laurent.alloin@xxxxxxxxxxxxxxxxxxxxxxxx>
Hi Norm,
Yes, I think we need to retain this wording from 2 perspectives. First, the rewrite of the TDECQ procedure that you pursue and that I support to a certain extent should not change the outcome of the measurement at this point in the project. Secondly, a well-designed receiver may well have the capability to determine the optimum slicer time stamp independently of the CDR phase selection. I rely on the wisdom of those individuals who wrote the original TDECQ specification to know that it matters.
Laurent
From:
norm.swenson@xxxxxxxx <norm.swenson@xxxxxxxx>
Laurent
Do you think we really need that line in the standard:
“The precise time position of the pair of histogram windows is adjusted to minimize TDECQ while keeping the histogram windows spaced 0.1 UI apart."
We test at \phi_0 +/- .05T, then we scan T_0 to find the best TDECQ. Do we need further optimization then that? It seems that this would represent the operation of the clock recovery and then looking at the values .05 UI early and late would account for jitter. Why would we need to do more than that?
Thanks, Norm
From: Hansel DSilva <Hansel.D'Silva@xxxxxxxxxxxxxxxx>
Hi Laurent,
Thank you for the feedback you provided on the presentation shared in the email titled "IEEE 802.3dj: Script in calculating TDECQ".
I would like to clarify my understanding of the following comment by you: "You have to make sure that the histograms are 0.1 UI apart, and not necessarily tied to phase0UI = phase0 / sps."
I am trying to reconcile this comment with the draft text in Clause 180, which states "Two vertical histograms are measured through the eye diagram, nominally centered 0.05 UI before and after sampling phase 0. Each of the histogram windows spans all of the modulation levels of the eye diagram, as illustrated in Figure 180-11. The precise time position of the pair of histogram windows is adjusted to minimize TDECQ while keeping the histogram windows spaced 0.1 UI apart."
When you mention that the histograms should not necessarily be tied to phase0/samples_per_ui, are you suggesting that the histogram-pair center should be treated as an additional optimization variable that is independent of the sampling phase phase0?
Wherein, instead of forcing: left= phase0- 0.05UI and right= phase0+ 0.05UI it should be left= phase_hist- 0.05 UI and right= phase_hist+ 0.05 UI where phase_hist may differ from phase0 and is adjusted to minimize TDECQ while maintaining the required 0.1 UI sepetation?
In my current implementation, the histogram locations are determined in extract_historgrams():
phase0UI= phase0/ samples_per_ui leftCenter = mod(phase0UI - 0.05,1); rightCenter = mod(phase0UI + 0.05,1);
Background, - For every phase: phase0= 0, 1, 2, ..., samples_per_ui-1 - Then phase0UI= phase0/ samples_per_ui - Then leftCenter= mod(phase0UI - 0.05,1) and rightCenter= mod(phase0UI + 0.05,1) - Hence, the histogram pair moves around the eye as phase0 changes. - For example, samples per UI= 8 phase0= 0; phase0UI= 0.000; left= 0.950; right= 0.050. phase0= 1; phase0UI= 0.125; left= 0.075; right= 0.175. phase0= 2; phase0UI= 0.250; left= 0.200; right= 0.300. phase0= 3; phase0UI= 0.375; left= 0.325; right= 0.425. phase0= 4; phase0UI= 0.500; left= 0.450; right= 0.550. phase0= 5; phase0UI= 0.625; left= 0.575; right= 0.675. phase0= 6; phase0UI= 0.750; left= 0.700; right= 0.800. phase0= 7; phase0UI= 0.875; left= 0.825; right= 0.925. Comment. The histogram windows are therefore phase-dependent, but their sepeartion is always 0.1 UI.
Regards, Hansel D'Silva
To unsubscribe from the STDS-802-3-B400G-OPTX list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-B400G-OPTX&A=1 |