Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [10GMMF] Reminder for TP2 call 12/23/04



 
Attached is a file for the TP2 meeting  today .
 
Lew
 

Lew Aronson  (lew.aronson@finisar.com)
Finisar Corporation
1308 Moffett Park Drive
Sunnyvale, CA  94089-1133
408-542-4215 (PH)
408-543-0083 (FAX)
 

-----Original Message-----
From: Tom Lindsay [mailto:tom.lindsay@CLARIPHY.COM]
Sent: Wednesday, December 22, 2004 6:05 PM
To: STDS-802-3-10GMMF@listserv.ieee.org
Subject: [10GMMF] Reminder for TP2 call 12/23/04

All - here are details for 12/23 TP2 call.
  • Date: Thurs, 12/23/04 (regular day/time)
  • Time: 9:00 AM Pacific
  • Duration: 1:30 max
  • Number: 401-694-1515
  • Access code: 421721#
Proposed agenda
  • Attendance
  • Approve agenda
  • Approve old minutes
  • Progress on tasks and distribution of work (see within previous minutes, below)
    • Scope timing, triggering; jitter (Pavel Zivny - ran out of time last week)
    • Test patterns (John Ewen spreadsheet)
    • TP2 test methodology (Norm Swenson)
    • New waveform results (Tom Lindsay - if done in time)
  • Plans for next call (1/6/05)
Thanks, Tom
ClariPhy Communications
tom.lindsay@clariphy.com
phone: (425) 608-0209, or (949) 480-9210
cell: (206) 790-3240
----- Original Message -----
Sent: Monday, December 20, 2004 3:42 PM
Subject: [10GMMF] Notes for TP2 call 12/16/04

Attendees
  • Jan Peeters Weem
  • Ben Wilcox
  • Nick Weiner
  • Tom Lindsay
  • John Jaeger
  • Martin Lobel
  • Pavel Zivny
  • John Ewen
  • Piers Dawe
  • Norm Swenson
  • Lew Aronson
  • Ali Ghiasi
  • Others who did not ID?
Agenda discussed and approved
  • Attendance (see above)
  • Approve agenda (done)
  • Approve old minutes (done, no comments)
  • Progress on tasks and distribution of work (see within previous minutes, below)
  • Plans for next call (12/23)
Tasks and distribution of work
  • Objective - resolve as many details as possible by/before comment deadline Jan 7th, 05
  • Waveform capture method
    • Pattern definition
      • John looked at AnAi and BnBi and found ~600 subpatterns within ~512 and 1024 bits where a block of 7 or higher bits repeats. The repeating block allows the subpattern to be tested or simulated apart from the rest of the longer pattern without concern for "end-effects".
      • John then began some searching for properties of these subpatterns including run lengths, bit combination histograms, autocorrelation, power spectral density, transition density, running disparity, etc. Not clear what most important qualities should be.
      • Suggestion that penalty analysis through Cambridge or Monte Carlo set might be best.
      • ACTIONS
        • Find top 5 patterns with widest variety of 9 bit blocks and top 5 with white power spectral density, send patterns through slow laser and slow Gaussian waveshapes and penalty simulation tools. Compare penalties with PRBS7, 9 and longer(?).
        • John to enter pattern descriptions into spreadsheet and provide options for ranking.
        • ClariPhy and others to run top 5 patterns (per above, plus PRBSn) through waveshapers and simulators.
    • Timing of pattern key.
      • Pavel has uploaded a presentation on this. No time on 12/16, to be discussed on 12/23 call.
    • Trigger block
      • Pavel has uploaded a presentation on this. No time on 12/16, to be discussed on 12/23 call.
    • Waveforms
      • Acquisition details complete.
      • Finisar & Intel have provided several waveforms with a good range of characteristics.
      • ClariPhy and PhyWorks have waveforms.
      • ACTIONS
        • More waveforms from other companies?
        • Tom to forward Finisar waveforms to PhyWorks. Jan to send Intel waveforms to Phyworks. Phyworks and ClariPhy to trade waveforms.
    • EDC simulation
      • Document definitions, references, architecture, and other basic approach and assumptions. Pseudo code?
        • Details must be sufficient to address all key assumptions and give confidence of completeness of test method.
        • ACTION - ClariPhy to provide. Goal by 12/23 call; by early January at latest.
        • Group will review. Once agreed, define and parse up detailed work to complete what goes into document. Some expect MATLAB code is the best final approach.
      • Corroboration
        • Goal to corroborate simulator results. PhyWorks stated they have capability.
        • ACTION - PhyWorks and ClariPhy (and others?) compare results.
    • Noise and jitter control
      • Pavel has uploaded a presentation on this. No time on 12/16, to be discussed on 12/23 call.
  • TP2 peak power limitation.
    • No discussion this call.
  • Statistical quality method (as introduced in dawe_1_1104)
    • No discussion this call.
  • All HW quality method
    • No discussion this call.
Next call, same coordinates
  • Date: Thurs, 12/23/04 (regular day/time)
  • Time: 9:00 AM Pacific
  • Duration: 1:30 max
  • Number: 401-694-1515
  • Access code: 421721#
 
In summary, plan to report progress and proposals on actions on the 12/23 call. Please let me know in advance of any agenda items.
----- Original Message -----
Sent: Wednesday, December 15, 2004 10:34 PM
Subject: [10GMMF] Reminder for TP2 call 12/16/04

Coordinates
  • Date: Thurs, 12/16/04 (regular day/time)
  • Time: 9:00 AM Pacific
  • Duration: 1:30 max
  • Number: 401-694-1515
  • Access code: 421721#
Agenda
  • Attendance
  • Approve agenda
  • Approve old minutes
  • Progress on tasks and distribution of work (see within previous minutes, below)
    • Also, specs on peak power limitation?
  • Plans for next call (12/23???)
There is a Task1 call that conflicts and is scheduled to run until 10 AM. I am not sure what effect that will have on this call.
 
Tom
 

Waveform Capture Data 12-07-04 wtih EDC penalties-4.pdf