================================================================================ IBIS INTERCONNECT TASK GROUP Mailing list: ibis-interconnect@freelists.org ================================================================================ Attendees from November 15, 2023 Meeting (* means attended at least using audio) ANSYS Curtis Clark Broadcom James Church Intel Corp. Michael Mirmak* Michael Brownell Keysight Technologies Ming Yan Marvell Steve Parker MathWorks Walter Katz* Micron Technology Justin Butterfield Siemens EDA Weston Beal*, Arpad Muranyi*, Randy Wolff* ST Microelectronics Aurora Sanna Teraspeed Labs Bob Ross* University of Illinois Jose Schutt-Aine Zuken USA Lance Wang Michael Mirmak convened the meeting and took minutes. No patents were declared. Michael reviewed the minutes. No comments were received. Weston Beal moved to approve the minutes; Randy Wolff seconded. No objections were raised and the minutes were approved. During AR review, Michael noted that he was still monitoring updates to the IBIS Interconnect website. In addition, he expected Pete, Steve - still open After brief discussion, the team decided to cancel the Nov. 22 meeting due to the US holidays that week. The next meeting will be Nov. 29. Arpad Muranyi sent out draft 11 of the pole-residue proposal. He has duplicated keyword rules in the text in multiple places. There is still a need to fix the units used throughout the document. Michael asked whether the units issue is part of a known issues list for Touchstone. Randy noted that something like this already exists, but in text format. Randy took the AR to create a known-issues list formal document for Touchstone [AR]. Arpad described needing to make required [Network Data] and [Noise Data] keywords conditional when pole-residue data is present. Bob Ross suggested ensuring usage of Touchstone 1.0 and 2.0 is consistent. The team also discussed formatting of option line rules, as well as which subparameters of [Begin Pole-Residue Data Source] should be required. Arpad noted that the date keyword format is being locked to a particular ordering. Bob expressed disagreement with this approach. He noted the use of military formatting for date, which Weston agreed is the least-confusing format. Arpad will add text noting which formats are required. Michael mentioned that IEEE 370 includes considerable header information and uses Touchstone (with comments) as a way of communicating measurement collection specifics. Michael took the AR to provide the IEEE 370 formatting to the reflector [AR]. The team then discussed line length requirements. Arpad clarified that the Number of Pole-Residue Keywords really refers to pole-residue- related keywords; Weston identified this as ambiguous. Should the keyword be replaced with "entries" (per Randy) or "blocks"? Arpad clarified that N and M in the equations provided correspond to the following concepts: N = ports M = number of lines In the current draft, the cyan highlights are from draft 10 and are unchanged since that version. The current version maintains pole-residue data as unnormalized. Weston noted that Touchstone 2.0 Y- and Z-parameters are unnormalized anyway. Weston asked whether an entry that does not have data is set to zero. What does this mean to a tool that encounters this data? Arpad suggested this is similar to a polynomial without a coefficient. Bob replied that diagonal ports should be required, with off-diagonals optional and set to zero. Arpad stated that rules for generating data are more appropriate for a cookbook than the specification. Weston clarified that the concern is not with regard to generating data but instead rules for what model data is minimally needed. Arpad asked whether, if all data was always required, would use of zero be a question. Weston replied probably not. Arpad also pointed out added rules to the [Number of Pole-Residue Blocks] keyword. Bob noted that rules for sparse and reciprocal matrices will be complex as a result; some discussion ensued as to whether this is explicitly supported yet or not. Michael suggested capitalization corrections, including "Ohm" being replaced with "ohm". Bob also noted a similar issue with "siemens" as a unit. Arpad also mentioned that he had moved some information to the background section. Randy suggested re-reading the keyword descriptions in light of upper and lower matrix possibly being supported. Weston observed that symmetry is an open question due to the passivity assumption. Do we need a specific keyword for symmetry as opposed to reciprocity? Reciprocal networks are described using symmetrical matrices. Arpad took the AR to address the question to the Interconnect reflector [AR]. The draft will be updated for the next meeting. Arpad moved to adjourn; Weston seconded. The meeting adjourned. The next meeting will be held Wednesday, November 29, 2023. ================================================================================ Bin List: 1) [Complete draft Touchstone document separating version 1.0 and 2.0 into their own chapters] - REMOVED 2) Create structures to encapsulate Touchstone 1.0 data in Touchstone 2+ specifications - TABLED 3) Complete draft Touchstone 2.0 document containing TSIRD3 and TSIRD4 draft (Muranyi) – COMPLETED IN DRAFT 10 4) Complete pole-residue format BIRD draft (Muranyi) 5) Complete port naming proposal (Katz) 6) Create alternatives to the Touchstone 1.0 option line before the "R" character - TABLED 7) Complete ISS-IRD 1 Draft - Enable Cascading of S-parameters Through W-element (Mirmak) - TABLED 8) Complete/revise Touchstone 3.0 draft outline (Mirmak) – dependent on several items above Tabled ARs: - Arpad to give an example of the physical connectivity needed for EMD automation.