================================================================================ IBIS INTERCONNECT TASK GROUP Mailing list: ibis-interconnect@freelists.org ================================================================================ Attendees from February 14, 2024 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 Synopsys Ted Mido, Edna Moreno 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 noted that the minutes of the last meeting were not yet available for review. Both the minutes of this meeting and the February 7 meeting will be reviewed at the February 21 meeting. Michael noted that his AR related to IEEE 370 sampling information was still being completed. In addition, he cannot complete his AR to contact the Quality Task Group regarding parser outputs until the meeting re-convenes. Arpad Muranyi reviewed his latest draft of the pole-reside proposal. Changes and comments include: - Arpad is making lists of required keywords that will change when the TSIRD is combined with the existing specification; this includes [Number of frequencies], [Network Data], [Noise Data]. We will need additional adjustments to the text to address required/optional rules scattered throughout. - [Number of frequencies] will have a counterpart in [Number of Pole-residue Indices] - a full example has been added, which uses upper matrix data Arpad also mentioned that that some issues remain with the [Reference] keyword. To ensure that the option line requirement can be removed and [Reference] supports all the features that exist and are needed, three new keywords will be needed to replace the option line plus clarify the data type, units, scale, etc. Walter Katz asked whether can you have reference information on the option line and the [Reference], or just the [Reference] keyword line. Arpad replied that the reference keyword requires all ports to have a value (not just a single value for all ports); currently the option line is still required. Michael suggested that Arpad write a second TSIRD to support a single port reference value on the [Reference] line, removing the option line requirement. Michael asked whether the upper/lower matrix keyword should be reused. Arpad expressed support for this. [Matrix Format] has been reused in the draft, but is still not required. If yes, the indexing for that arrangement is used. Randy Wolff asked whether to enforce in the parser that the file has the right number of indices if the keyword is used. Weston Beal suggests this is already strongly implied. Michael asked if we change [Reference] whether there is a need to alter anything in this TSIRD. Arpad replied that no change is needed. Michael asked whether numeric formatting rules were needed outside of existing Touchstone rules. Arpad replied that no changes were necessary. Walter asked whether a fit figure of merit was needed. The consensus was not to add one. Weston asked whether the draft should include a fit quality number. The general consensus was no. Weston asked whether any fit quality metric exists in 370. Walter replied that there is none there. Michael added that equations for other quality metrics are there, such as passivity, causality and reciprocity. Arpad asked what should be done if the fit is bad. Michael noted that approach of IEEE 370 is to identify quality issues by the fact of including them in the model or measurement data; the very act of including this data implies bad instances will never be released by the vendor. Arpad suggested that the specification could add these metrics later. Walter suggested that fit metric and fit quality could be added as two related but separate strings. Arpad noted that this could even be a comment. Randy noted that he found a typographical error in the min valid/max valid range text. Arpad moved to submit the draft text to the IBIS Open Forum as a TSIRD for an approval vote. Weston seconded the motion. No objections were raised and the motion was approved. Arpad will accept all document changes and send the final version to Lance for consideration in the next Open Forum meeting. The port-mapping issue will be addressed in upcoming meetings. However, the [Reference] keywords still need Michael asked whether the team should focus on port mapping next, or resolve the reference issue next. Weston advocated resolving the Reference issues first. Walter noted that there are two port mapping formats on the table, Walter's and Arpad's. He proposed coming up with examples of each and conversion procedures between them. The team can then vote on which is preferred. Arpad will send his examples for conversion first. Arpad moved to adjourn; Walter seconded. The meeting adjourned without objection. The next meeting will take place on February 21, 2024. ================================================================================ 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 4) Complete pole-residue format BIRD draft (Muranyi) - COMPLETED 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.