DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 DRAFT5 ICM Issue Resolution Document (IIRD) IIRD ID#: 9 ISSUE TITLE: Clarification of S-parameter Port Assignments REQUESTOR: Michael Mirmak, Intel Corporation DATE SUBMITTED: May 21, 2007 DATE REVISED: DATE ACCEPTED BY IBIS OPEN FORUM: **************************************************************************** **************************************************************************** STATEMENT OF THE ISSUE: ICM defines links to S-parameter files. S-parameter ports do not necessarily correspond to individual physical terminals or nodes. ICM uses the term "ports" loosely and does not specify how S-parameter ports consisting of a terminal plus a reference should be handled. The text below clarifies the usage of the term "port" and defines several unambiguous referencing schemes when ICM is used with S-parameter data. **************************************************************************** STATEMENT OF THE RESOLVED SPECIFICATIONS: Proposed changes are denoted by *. Proposed changes in DRAFT 2 are denoted by **. Proposed changes in DRAFT 5 are denoted by ****. |----- SECTION THREE OLD TEXT ----- 14) Note that the text here, in many cases, assumes that the model data describes a connector. However, other types of interconnect can be modeled using the ICM format; in these cases, the words "pin" and "port" in the text below can be interpreted to refer to the locations where the interconnect is accessed for probing, measurement or analysis. |---- END OLD TEXT ---- |----- SECTION THREE NEW TEXT ----- 14) Note that the text here, in many cases, assumes that the model data describes a connector. However, other types of interconnect can be modeled * using the ICM format; in these cases, the words "pin" and "terminal" in the text below can be interpreted to refer to the locations where the interconnect is accessed for probing, measurement or analysis. |---- END NEW TEXT ---- |----- [Tree Path Description] KEYWORD OLD TEXT ----- | under "Fork, Endfork" At a fork, a path split similar in shape to the letter "T" is created. The matrix sections constituting the "T" are connected, including the first of any sections listed between the Fork and Endfork subparameters. The sections (zero or more) between the Fork and Endfork subparameters are connected together as in any other path description. If no pin map name is placed between a Fork and Endfork block, then the block constitutes a stub. However, if a pin map name is placed at the end of the Fork and Endfork block, an externally available port is created on the interconnect. |---- END OLD TEXT ---- |----- [Tree Path Description] KEYWORD NEW TEXT ----- | under "Fork, Endfork" At a fork, a path split similar in shape to the letter "T" is created. The matrix sections constituting the "T" are connected, including the first of any sections listed between the Fork and Endfork subparameters. The sections (zero or more) between the Fork and Endfork subparameters are connected together as in any other path description. If no pin map name is placed between a Fork and Endfork block, then the block constitutes a stub. However, if a pin map name is placed at the * end of the Fork and Endfork block, an externally available terminal is created on the interconnect. |---- END NEW TEXT ---- |---- [ICM S-parameter] KEYWORD OLD TEXT ---- ============================================================================== Keyword: [ICM S-parameter] Required: No, unless ICM_model_type subparameter of [Begin ICM Model] is equal to "S-parameter". Sub-Params: File_name, Port_assignment Used By: [Begin ICM Section] Description: Indicates a reference to an external S-parameter file Usage Rules: An S-parameter matrix can be used in place of an RLGC matrix. The [ICM S-parameter] keyword may appear multiple times in the file, however it may appear only once between the [Begin ICM Section]/[End ICM Section] keyword pair, and they must be placed after the [Derivation Method] keyword. File_name File_name refers to the name of an external file in "Touchstone" format containing S-parameter matrix data for this section. The Touchstone file must be located in the same directory as the ICM file which makes reference to it. Port_assignment "Port_assignment" is used to relate the ports in the S-parameter file to the node map for a particular N_Section as defined under the [Nodal Path Description] keyword. The "Port_assignment" table entries must match the node names from the corresponding [Nodal Path Description]. No more and no fewer entries in the table are allowed. Note that [ICM S-parameter] may not be used to describe data for sections in a [Tree Path Description]. There are two columns used in the Port_assignment. The first column should reference the input port name as defined in the Touchstone file that is related to the "Node Name" in the second column. The second column contains a "Node Name" as defined in the node list under the corresponding [Nodal Path Description]. ----------------------------------------------------------------------------- [ICM S-parameter] File_name sample.s4p | any name and extension allowed Port_assignment |Port Node 1 A1 2 B1 3 A2 4 B2 5 A3 6 B3 7 A4 8 B4 |---- END OLD TEXT ---- |---- [ICM S-parameter] KEYWORD NEW TEXT ---- Port_assignment "Port_assignment" is used to relate the ports in the S-parameter file to the node map for a particular N_Section as defined under the [Nodal Path Description] keyword. The "Port_assignment" table entries must match the node names from the corresponding * [Nodal Path Description]. Note that [ICM S-parameter] may not be used to describe data for sections in a [Tree Path Description]. There are two columns used in the Port_assignment. The first column should reference the input port name as defined in the Touchstone file that is related to the "Node Name" in the second column. The second column contains a "Node Name" as defined in the node list under the corresponding [Nodal Path Description]. * Note that "ports" for Touchstone(R) S-parameters are not * single physical nodes or terminals. A "port" refers to * a physical node plus its reference or return terminal. * Therefore, Port names must be duplicated to describe * assignmnent of reference terminals. The first node name in * a duplicated pair of port names is the measurement * node in the port. The second node using the same port name * is the reference port. The order of assignment is * determined starting with reference to the top of the Port_assignment list. * As a result, where N ports are declared, 2*N lines must be present * under Port_assignment, with each port listed twice. Port pairs need * not appear in ascending numerical order. * * In some cases, S-parameter ports may share reference nodes, or use a single * reference node (for example, "ground-reduced" model data). In these cases, * node names may appear multiple times under "Port_assignment." * Each node name under the ICM Section calling the S-parameter data * must appear at least once. * * Only non-zero integer numbers are permitted in the first column. All * ports implied by the accompanying S-parameter file must be represented * by numerical entries in the first column (e.g., for a five port * S-parameter file, ports 1 through 5 must appear in the first column, * with each port appearing twice). * **** TEXT BELOW DELETED * The reserved words POWER and GND may be used as the reference * node for any port. However, the exact connection between the ICM * model POWER and/or GND references and other circuit nodes in the same * netlist shall be resolved by the simulation tool processing the data. * * Previous versions of the ICM specification permitted omission of * referencing. For the purpose of parsing, ICM 1.0 and 1.1 models * that feature [ICM S-parameter] should be assumed to use a single * reference, the GND node, for all ports. However, a warning should * be issued for these ICM files. **** END OF DELETION * **** Previous versions of the ICM specification permitted omission of **** referencing. For the purpose of parsing, ICM 1.0 and 1.1 models **** that feature [ICM S-parameter] should be considered ambiguous and **** a warning should be issued for these ICM files. ** ** Additional Notes ** ** The ICM links to S-parameter data are intended to remove ambiguity ** in how S-parameter data is used in a circuit simulation context. ** As a result, ICM port assignments should be tailored to the method used to ** collect the associated S-parameter data. Under no circumstances should ** one set of S-parameter data be used with multiple ICM files that define ** different referencing schemes. ** ----------------------------------------------------------------------------- [ICM S-parameter] File_name sample1.s4p | any name and extension allowed Port_assignment |Port Node 1 A1 1 A1ref 2 A2 2 A2ref 3 A3 3 A3ref 4 A4 4 A4ref | The second Node Name for each duplicated Port name above is considered the | reference for the first node in the port. Note that the Touchstone(R) file | only contains data for four ports, but each has a unique reference. ----------------------------------------------------------------------------- [ICM S-parameter] File_name sample1.s4p | any name and extension allowed Port_assignment |Port Node 1 D1 1 dieref 2 D2 2 dieref 3 P3 3 pinref 4 P4 4 pinref | In this example, a four-port network is represented using two shared | reference nodes. No electrical relationship outside the S-parameter | data is assumed between the nodes "pinref" and "dieref". ----------------------------------------------------------------------------- [ICM S-parameter] File_name sample2.s4p | any name and extension allowed Port_assignment |Port Node 1 A1 1 PortRef 2 B1 2 PortRef 3 A2 3 PortRef 4 B2 4 PortRef | Here, the S-parameter ports share the same physical reference node, called | "PortRef." The Touchstone(R) file includes data for 4 ports total. |---- END NEW TEXT ---- ***************************************************************************** In addition, all examples using the word "Port" should be changed to use **** the word "Terminal" with appropriate capitalization for consistency. **** The specific instances are listed below |---- Section 3 OLD TEXT ---- 14) Note that the text here, in many cases, assumes that the model data describes a connector. However, other types of interconnect can be modeled using the ICM format; in these cases, the words "pin" and "port" in the text below can be interpreted to refer to the locations where the interconnect is accessed for probing, measurement or analysis. |---- END OLD TEXT ---- |---- Section 3 NEW TEXT ---- 14) Note that the text here, in many cases, assumes that the model data describes a connector. However, other types of interconnect can be modeled **** using the ICM format; in these cases, the words "pin" and "terminal" in the text below can be interpreted to refer to the locations where the interconnect is accessed for probing, measurement or analysis. |---- END NEW TEXT ---- |---- Section 6 "Fork, Endfork" OLD TEXT ---- At a fork, a path split similar in shape to the letter "T" is created. The matrix sections constituting the "T" are connected, including the first of any sections listed between the Fork and Endfork subparameters. The sections (zero or more) between the Fork and Endfork subparameters are connected together as in any other path description. If no pin map name is placed between a Fork and Endfork block, then the block constitutes a stub. However, if a pin map name is placed at the end of the Fork and Endfork block, an externally available port is created on the interconnect. |---- END OLD TEXT ---- |---- Section 6 "Fork, Endfork" NEW TEXT ---- At a fork, a path split similar in shape to the letter "T" is created. The matrix sections constituting the "T" are connected, including the first of any sections listed between the Fork and Endfork subparameters. The sections (zero or more) between the Fork and Endfork subparameters are connected together as in any other path description. If no pin map name is placed between a Fork and Endfork block, then the block constitutes a stub. However, if a pin map name is placed at the **** end of the Fork and Endfork block, an externally available terminal is created on the interconnect. |---- END NEW TEXT ---- |---- Section 6 "[Tree Path Description]" OLD TEXT ---- ----------------------------------------------------------------------------- "ICM Model" Examples ----------------------------------------------------------------------------- Example 1: A simple single line model with one section SectA Port1 >--------< Port2 [Begin ICM Model] MyModelExample1 ICM_model_type SLM_general SGR 3:1 Ref_impedance=50 [Tree Path Description] Model_pinmap Example1_pinmap Side A | The Model_pinmap name is reused, so Side and a unique | side name is required Section Mult=1 Diagonal_matrix1 Model_pinmap Example1_pinmap Side B | The Model_pinmap name is reused, so Side and a unique | side name is required . . . [End ICM Model] ----------------------------------------------------------------------------- Example 2: 2 ports per conductor, 5 sections straight through SectA SectB SectC SectD SectE Port1 >--------< >--------< >-------< >--------< >----------< Port2 [Begin ICM Model] MyModelExample2 ICM_model_type SLM_quiescent [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 SectA Section Mult=1 SectB Section Mult=1 SectC Section Mult=1 SectD Section Mult=1 SectE Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- Example 3: 2 ports per conductor, 2 series sections with one stub SectionA SectionB Port1 >------------< >--------------< Port2 | StubSection1 [Begin ICM Model] MyModelExample3 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 SectionA Fork Section Mult=1 StubSection1 Endfork Section Mult=1 SectionB Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- Example 4: 2 ports per conductor with 2 stub sections; one stub matrix is re-used, and another stub is repeated A B C Port1 >----------< >-----------< >-----------< Port2 |stub1 |stub4 |stub2 |stub4 |stub1 [Begin ICM Model] MyModelExample4 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 stub1 Section Mult=1 stub2 Section Mult=1 stub1 Endfork Section Mult=1 B Fork Section Mult=2 stub4 Endfork Section Mult=1 C Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- Example 5: 2 ports per conductor, 3 stubs A B C D Port1 >------< >------< >------< >-------< Port2 |Stub1 |Stub2 |Stub1 |Stub3 |Stub4 [Begin ICM Model] MyModel4 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 Stub1 Endfork Section Mult=1 B Fork Section Mult=1 Stub2 Section Mult=1 Stub3 Section Mult=1 Stub4 Endfork Section Mult=1 C Fork Section Mult=1 Stub1 Endfork Section Mult=1 D Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- Example 6: 3 ports per conductor, 2 stubs A B C D Port1 >------< >------< >------< >-------< Port 2 |Stub1 |Stub2 |Stub1 |Stub3 |Stub4 |Port3 [Begin ICM Model] MyModelExample6 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 Stub1 Endfork Section Mult=1 B Fork Section Mult=1 Stub2 Section Mult=1 Stub3 Section Mult=1 Stub4 Model_pinmap MyModelPinMapC Endfork Section Mult=1 C Fork Section Mult=1 Stub1 Endfork Section Mult=1 D Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- Example 7: 3 ports per conductor, 5 sections straight through SectionA SectionB SectionC SectionD SectionE Port1 >----------< >----------< >---------< >----------<|>------------< Port2 | SectionF |>------------< Port3 [Begin ICM Model] MyModelExample7 ICM_model_type SLM_quiescent [Tree Path Description] Model_pinmap = MyModelPinMapA Section Mult=1 SectionA Section Mult=1 SectionB Section Mult=1 SectionC Section Mult=1 SectionD Fork Section Mult=1 SectionF Model_pinmap MyModelPinMapB Endfork Section Mult=1 SectionE Model_pinmap MyModelPinMapC . . . [End ICM Model] |---- END OLD TEXT ----| |---- Section 6 "[Tree Path Description]" NEW TEXT ---- ----------------------------------------------------------------------------- "ICM Model" Examples ----------------------------------------------------------------------------- Example 1: A simple single line model with one section SectA **** Terminal1 >--------< Terminal2 [Begin ICM Model] MyModelExample1 ICM_model_type SLM_general SGR 3:1 Ref_impedance=50 [Tree Path Description] Model_pinmap Example1_pinmap Side A | The Model_pinmap name is reused, so Side and a unique | side name is required Section Mult=1 Diagonal_matrix1 Model_pinmap Example1_pinmap Side B | The Model_pinmap name is reused, so Side and a unique | side name is required . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 2: 2 terminals per conductor, 5 sections straight through SectA SectB SectC SectD SectE **** Terminal1 >--------< >--------< >-------< >--------< >----------< Terminal2 [Begin ICM Model] MyModelExample2 ICM_model_type SLM_quiescent [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 SectA Section Mult=1 SectB Section Mult=1 SectC Section Mult=1 SectD Section Mult=1 SectE Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 3: 2 terminals per conductor, 2 series sections with one stub SectionA SectionB **** Terminal1 >------------< >--------------< Terminal2 | StubSection1 [Begin ICM Model] MyModelExample3 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 SectionA Fork Section Mult=1 StubSection1 Endfork Section Mult=1 SectionB Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 4: 2 terminals per conductor with 2 stub sections; one stub matrix is re-used, and another stub is repeated A B C **** Terminal1 >----------< >-----------< >-----------< Terminal2 |stub1 |stub4 |stub2 |stub4 |stub1 [Begin ICM Model] MyModelExample4 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 stub1 Section Mult=1 stub2 Section Mult=1 stub1 Endfork Section Mult=1 B Fork Section Mult=2 stub4 Endfork Section Mult=1 C Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 5: 2 terminals per conductor, 3 stubs A B C D **** Terminal1 >------< >------< >------< >-------< Terminal2 |Stub1 |Stub2 |Stub1 |Stub3 |Stub4 [Begin ICM Model] MyModel4 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 Stub1 Endfork Section Mult=1 B Fork Section Mult=1 Stub2 Section Mult=1 Stub3 Section Mult=1 Stub4 Endfork Section Mult=1 C Fork Section Mult=1 Stub1 Endfork Section Mult=1 D Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 6: 3 terminals per conductor, 2 stubs A B C D **** Terminal1 >------< >------< >------< >-------< Terminal2 |Stub1 |Stub2 |Stub1 |Stub3 |Stub4 **** |Terminal3 [Begin ICM Model] MyModelExample6 ICM_model_type MLM [Tree Path Description] Model_pinmap MyModelPinMapA Section Mult=1 A Fork Section Mult=1 Stub1 Endfork Section Mult=1 B Fork Section Mult=1 Stub2 Section Mult=1 Stub3 Section Mult=1 Stub4 Model_pinmap MyModelPinMapC Endfork Section Mult=1 C Fork Section Mult=1 Stub1 Endfork Section Mult=1 D Model_pinmap MyModelPinMapB . . . [End ICM Model] ----------------------------------------------------------------------------- **** Example 7: 3 terminals per conductor, 5 sections straight through SectionA SectionB SectionC SectionD SectionE **** Terminal1 >----------< >----------< >---------< >----------<|>------------< Terminal2 | SectionF **** |>------------< Terminal3 [Begin ICM Model] MyModelExample7 ICM_model_type SLM_quiescent [Tree Path Description] Model_pinmap = MyModelPinMapA Section Mult=1 SectionA Section Mult=1 SectionB Section Mult=1 SectionC Section Mult=1 SectionD Fork Section Mult=1 SectionF Model_pinmap MyModelPinMapB Endfork Section Mult=1 SectionE Model_pinmap MyModelPinMapC . . . [End ICM Model] |---- END NEW TEXT ----| |---- Section 6 "[Nodal Path Description]" OLD TEXT ----| ----------------------------------------------------------------------------- Example 5: 2 ports per pin, 5 sections straight through. Note that this interconnect could have been also described by the [Tree Path Description] keyword due to its regularity and the one to one mapping. SectA SectB SectC SectD SectE Port_A >-------< >-------< >-------< >-------< >-------< Port_B [Begin ICM Model] MyModelExample5 ICM_model_type SLM_quiescent [Nodal Path Description] Model_nodemap Port_A N_section (A1 A2 A3 A4 11 12 13 14) Len=1.0 SectA N_section (11 12 13 14 21 22 23 24) Len=1.0 SectB N_section (21 22 23 24 31 32 33 34) Len=1.0 SectC N_section (31 32 33 34 41 42 43 44) Len=1.0 SectD N_section (41 42 43 44 B1 B2 B3 B4) Len=1.0 SectE Model_nodemap Port_B [End ICM Model] ----------------------------------------------------------------------------- Example 6: 2 ports per pin, 2 series sections with one stub that taps into line_2 and line_4. SectionA SectionB Port_A1 >----------<----->----------< Port_B1 Port_A2 >----------<---o->----------< Port_B2 Port_A3 >----------<---+->----------< Port_B3 Port_A4 >----------<-o-+->----------< Port_B4 Port_A5 >----------<-+-+->----------< Port_B5 | | | | StubSection1 [Begin ICM Model] MyModelExample6 ICM_model_type MLM [Nodal Path Description] Model_nodemap Port_A N_section (A1 A2 A3 A4 A5 11 12 13 14 15) Len=1.0 SectionA N_section ( 12 14 x2 x4 ) Len=1.0 StubSection1 N_section (11 12 13 14 15 B1 B2 B3 B4 B5) Len=1.0 SectionB Model_nodemap Port_B [End ICM Model] ----------------------------------------------------------------------------- Example 7: 2 ports per pin, 2 stub sections, one stub matrix is re-used, and another stub is repeated. A B C Port_A >---------< >---------< >---------< Port_B |stub1 |stub4 |stub2 |stub4 |stub1 |Port_C [Begin ICM Model] MyModelExample7 ICM_model_type MLM [Nodal Path Description] Model_nodemap Port_A N_section (A1 A2 A3 A4 A5 11 12 13 14 15) Len=1.0 A N_section (11 12 13 14 15 s1 s2 s3 s4 s5) Len=1.0 stub1 N_section (s1 s2 s3 s4 s5 t1 t2 t3 t4 t5) Len=1.0 stub2 N_section (t1 t2 t3 t4 t5 C1 C2 C3 C4 C5) Len=1.0 stub1 Model_nodemap Port_C N_section (11 12 13 14 15 21 22 23 24 25) Len=1.0 B N_section (21 22 23 24 25 x1 x2 x3 x4 x5) Mult=2 stub4 N_section (21 22 23 24 25 B1 B2 B3 B4 B5) Len=1.0 C Model_nodemap Port_B [End ICM Model] |---- END OLD TEXT ----| |---- Section 6 "[Nodal Path Description]" NEW TEXT ----| ----------------------------------------------------------------------------- Example 5: **** 2 terminals per pin, 5 sections straight through. Note that this interconnect could have been also described by the [Tree Path Description] keyword due to its regularity and the one to one mapping. SectA SectB SectC SectD SectE **** Terminal_A >-------< >-------< >-------< >-------< >-------< Terminal_B [Begin ICM Model] MyModelExample5 ICM_model_type SLM_quiescent [Nodal Path Description] **** Model_nodemap Terminal_A N_section (A1 A2 A3 A4 11 12 13 14) Len=1.0 SectA N_section (11 12 13 14 21 22 23 24) Len=1.0 SectB N_section (21 22 23 24 31 32 33 34) Len=1.0 SectC N_section (31 32 33 34 41 42 43 44) Len=1.0 SectD N_section (41 42 43 44 B1 B2 B3 B4) Len=1.0 SectE **** Model_nodemap Terminal_B [End ICM Model] ----------------------------------------------------------------------------- Example 6: **** 2 terminals per pin, 2 series sections with one stub that taps into line_2 and line_4. SectionA SectionB **** Terminal_A1 >----------<----->----------< Terminal_B1 **** Terminal_A2 >----------<---o->----------< Terminal_B2 **** Terminal_A3 >----------<---+->----------< Terminal_B3 **** Terminal_A4 >----------<-o-+->----------< Terminal_B4 **** Terminal_A5 >----------<-+-+->----------< Terminal_B5 | | | | StubSection1 [Begin ICM Model] MyModelExample6 ICM_model_type MLM [Nodal Path Description] **** Model_nodemap Terminal_A N_section (A1 A2 A3 A4 A5 11 12 13 14 15) Len=1.0 SectionA N_section ( 12 14 x2 x4 ) Len=1.0 StubSection1 N_section (11 12 13 14 15 B1 B2 B3 B4 B5) Len=1.0 SectionB Model_nodemap Terminal_B [End ICM Model] ----------------------------------------------------------------------------- Example 7: **** 2 terminals per pin, 2 stub sections, one stub matrix is re-used, and another stub is repeated. A B C **** Terminal_A >---------< >---------< >---------< Terminal_B |stub1 |stub4 |stub2 |stub4 |stub1 **** |Terminal_C [Begin ICM Model] MyModelExample7 ICM_model_type MLM [Nodal Path Description] **** Model_nodemap Terminal_A N_section (A1 A2 A3 A4 A5 11 12 13 14 15) Len=1.0 A N_section (11 12 13 14 15 s1 s2 s3 s4 s5) Len=1.0 stub1 N_section (s1 s2 s3 s4 s5 t1 t2 t3 t4 t5) Len=1.0 stub2 N_section (t1 t2 t3 t4 t5 C1 C2 C3 C4 C5) Len=1.0 stub1 **** Model_nodemap Terminal_C N_section (11 12 13 14 15 21 22 23 24 25) Len=1.0 B N_section (21 22 23 24 25 x1 x2 x3 x4 x5) Mult=2 stub4 N_section (21 22 23 24 25 B1 B2 B3 B4 B5) Len=1.0 C **** Model_nodemap Terminal_B [End ICM Model] |---- END NEW TEXT ----| |---- Section 6 "[ICM Node Map]" OLD TEXT ----| ----------------------------------------------------------------------------- Example 5: [ICM Node Map] Port_A | pin node name PORT_A1 A1 POS_0 PORT_A2 A2 NEG_0 PORT_A3 A3 POS_1 PORT_A4 A4 NEG_1 [ICM Node Map] Port_B | pin node name PORT_B1 B1 POS_0 PORT_B2 B2 NEG_0 PORT_B3 B3 POS_1 PORT_B4 B4 NEG_1 ----------------------------------------------------------------------------- Example 6: [ICM Node Map] Port_A | pin node name PORT_A1 A1 POS_0_A PORT_A2 A2 NEG_0_A PORT_A3 A3 POS_1_A PORT_A4 A4 NEG_1_A PORT_A5 A5 REF [ICM Node Map] Port_B | pin node name PORT_B1 B1 POS_0_B PORT_B2 B2 NEG_0_B PORT_B3 B3 POS_1_B PORT_B4 B4 NEG_1_B PORT_B5 B5 REF ----------------------------------------------------------------------------- Example 7: [ICM Node Map] Port_A | pin node name PORT_A1 A1 POS_0_A PORT_A2 A2 NEG_0_A PORT_A3 A3 POS_1_A PORT_A4 A4 NEG_1_A PORT_A5 A5 REF [ICM Node Map] Port_B | pin node name PORT_B1 B1 POS_0_B PORT_B2 B2 NEG_0_B PORT_B3 B3 POS_1_B PORT_B4 B4 NEG_1_B PORT_B5 B5 REF [ICM Node Map] Port_C | pin node name PORT_C1 C1 POS_0_C PORT_C2 C2 NEG_0_C PORT_C3 C3 POS_1_C PORT_C4 C4 NEG_1_C PORT_C5 C5 REF |---- END OLD TEXT ----| |---- Section 6 "[ICM Node Map]" NEW TEXT ----| ----------------------------------------------------------------------------- Example 5: **** [ICM Node Map] Terminal_A | pin node name **** TERMINAL_A1 A1 POS_0 **** TERMINAL_A2 A2 NEG_0 **** TERMINAL_A3 A3 POS_1 **** TERMINAL_A4 A4 NEG_1 **** [ICM Node Map] Terminal_B | pin node name **** TERMINAL_B1 B1 POS_0 **** TERMINAL_B2 B2 NEG_0 **** TERMINAL_B3 B3 POS_1 **** TERMINAL_B4 B4 NEG_1 ----------------------------------------------------------------------------- Example 6: **** [ICM Node Map] Terminal_A | pin node name **** TERMINAL_A1 A1 POS_0_A **** TERMINAL_A2 A2 NEG_0_A **** TERMINAL_A3 A3 POS_1_A **** TERMINAL_A4 A4 NEG_1_A **** TERMINAL_A5 A5 REF **** [ICM Node Map] Terminal_B | pin node name **** TERMINAL_B1 B1 POS_0_B **** TERMINAL_B2 B2 NEG_0_B **** TERMINAL_B3 B3 POS_1_B **** TERMINAL_B4 B4 NEG_1_B **** TERMINAL_B5 B5 REF ----------------------------------------------------------------------------- Example 7: **** [ICM Node Map] Terminal_A | pin node name **** TERMINAL_A1 A1 POS_0_A **** TERMINAL_A2 A2 NEG_0_A **** TERMINAL_A3 A3 POS_1_A **** TERMINAL_A4 A4 NEG_1_A **** TERMINAL_A5 A5 REF **** [ICM Node Map] Terminal_B | pin node name **** TERMINAL_B1 B1 POS_0_B **** TERMINAL_B2 B2 NEG_0_B **** TERMINAL_B3 B3 POS_1_B **** TERMINAL_B4 B4 NEG_1_B **** TERMINAL_B5 B5 REF **** [ICM Node Map] Terminal_C | pin node name **** TERMINAL_C1 C1 POS_0_C **** TERMINAL_C2 C2 NEG_0_C **** TERMINAL_C3 C3 POS_1_C **** TERMINAL_C4 C4 NEG_1_C **** TERMINAL_C5 C5 REF |---- END NEW TEXT ----| **************************************************************************** ANALYSIS PATH/DATA THAT LED TO SPECIFICATION: The port issue addressed by these changes was first identified by Sam Chitwood of Sigrity. Significant analysis was performed by Bob Ross of Teraspeed Consulting Group. Clarification of port references courtesy of John Moore of Agilent. Draft 5 adds explicit changes to each instance of the word "port" erroneously used, as suggested by Bob Ross. **************************************************************************** ANY OTHER BACKGROUND INFORMATION: ****************************************************************************