================================================================================

IBIS INTERCONNECT TASK GROUP
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibis.org_interconnect-5Fwip_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=5BFd4DjqDBYI8X3Hg6d3goiFAs7jnraEVf8Z8wzTFUgMhP2s18nIc4H3KQJnIaYe&s=FU4H7qVckQjdY0VFMq9ZgcfBoivJXpvczvgGAMTVHvw&e=  
Mailing list: ibis-interconnect@freelists.org 
Archives at https://urldefense.proofpoint.com/v2/url?u=http-3A__www.freelists.org_archive_ibis-2Dinterconn_&d=DwIGAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DcQR-qLpQg5lIreuM6-NYECRIAFXt268PRNS5WO043M&m=5BFd4DjqDBYI8X3Hg6d3goiFAs7jnraEVf8Z8wzTFUgMhP2s18nIc4H3KQJnIaYe&s=nKDMk1u9PxjrhAgJYmVlVKi1lN7RMpCy94q9o8YIIMM&e=  

================================================================================

Attendees from February 16, 2022 Meeting (* means attended at least using audio)

ANSYS                                Curtis Clark
Intel Corp.                          Michael Mirmak*
Marvell                              Steve Parker
MathWorks                            Walter Katz*
Micron Technology                    Justin Butterfield*
                                     Randy Wolff*
Siemens EDA                          Arpad Muranyi*
ST Microelectronics                  Aurora Sanna
Teraspeed Labs                       Bob Ross*
University of Illinois               Jose Schutt-Aine
Zuken USA                            Lance Wang*


Michael Mirmak convened the meeting.  No patents were declared. 
Justin Butterfield took minutes.


Review of Minutes:
- Michael called for review of the minutes from the February 9, 2022 meeting.  
  Michael displayed the minutes.  Randy Wolff commented "ISSRD" should be 
  "ISSIRD" to be consistent with other issue resolution document format 
  naming.  Bob Ross commented "ISSRD" appears in the bin list and should be 
  changed as well.  Randy moved to approve the minutes with the change from 
  "ISSRD" to "ISSIRD".  Lance Wang seconded.  The minutes were approved 
  without objection.


Review of ARs:   
- None.


Opens:
- None.


Discussion:

Network Data in Multiple Lines:
Walter Katz shared an email regarding the network data format.  In Touchstone 
2, there are a fixed number of values based on the number of ports.  These 
values can be broken across multiple lines, and they can be split at any 
point.  He asked if his interpretation is correct.  Randy noted Mike Labonte 
sent out an email about how the parser checks this.  The parser allows network 
data to be split, but the real and imaginary cannot be split.  Bob asked if 
this is defined in the specification.  Walter replied the examples suggest you 
cannot split a real and imaginary number across a new line.  Arpad Muranyi 
asked, if the real and imaginary are broken up, how would you know if the data 
is a frequency value or port data.  Michael suggested it could be a matter of 
efficiency, since you would have to read the file twice to parse the data if 
we allow real and imaginary numbers to be split.  Walter noted the 
specification is not clear on this.  Bob would like to double check how the 
parser behaves if you split the real and imaginary data.

Walter stated parsers will be much more difficult to write if the real and 
imaginary can be broken up, and he recommended not allowing this.  If you 
preserve the real and imaginary on one line, the parser can tell at which 
frequency an error in the data occurs.  Bob commented you have the number of 
frequency points and the number of ports.  Michael asked if the concern is for 
Touchstone 1 or Touchstone 2.  Walter replied that Touchstone 1 has very 
strict rules on the number of data on each line.  Bob will create a test case 
for the parser with network data on multiple lines [AR].

Arpad moved to table this topic.  Randy seconded.


Editorial TSIRD:
Michael sent out a TSIRD draft proposal on the [End] keyword which is missing 
from several of the examples in Touchstone 2.  There are also several other 
issues that he found by parsing the examples in the Touchstone 2 parser.  Bob 
had sent comments and suggested additional edits to the TSIRD.  Randy asked 
about Example 15.  Michael replied that Example 15 was not edited.  Bob asked 
what was the issue.  Randy replied one issue was the commas in the port 
names.  Michael thought the commas are legitimate, but he was not sure of a 
better way to express the port numbers.  Walter suggested to separate all the 
port numbers with a period or colon.  Michael asked if we want to add this in 
the draft.  Randy agreed.  Michael will propose changes to Example 15 [AR].


Designator Pin List Relaxation:
Michael asked if there are any updates to the BIRD drafts from ATM.  Arpad 
replied we still have open items to discuss on the Designator Pin List 
Relaxation BIRD draft.  He sent out a new draft to deal with the NC pins and 
changes based on Randy's feedback.  Arpad also added rules for the NC pins.  
Randy commented, in the sentence about the NC signal_type, we may want to add 
why you would want to do that.  Arpad suggested new wording about the purpose 
of the NC label.  Arpad will send out the latest draft of the Designator Pin 
List Relaxation BIRD [AR].


Walter noted he sent out an email about port naming.  Michael stated we can 
add this to the bin list.


Arpad motioned to adjourn.  Walter seconded.  The meeting adjourned.


Next Meeting:
The next meeting will be February 23.


================================================================================
Bin List:
1. Touchstone 3
2. Pole-residue support for Touchstone
3. Clarification BIRD drafts from ATM
4. TSIRD(4)
5. ISSRD process
6. Frequency data in multiple lines
7. Port naming