================================================================================ IBIS EDITORIAL TASK GROUP http://www.ibis.org/editorial_wip/ Mailing list: ibis-editorial@freelists.org Archives at http://www.freelists.org/archive/ibis-editorial/ ================================================================================ Attendees from October 16, 2018 Meeting (* means attended at least using audio) ANSYS Curtis Clark Cadence Design Systems Bradley Brim Intel Corp. Michael Mirmak* Keysight Technologies Radek Biernacki* Mentor, A Siemens Business Arpad Muranyi* Micron Technology Justin Butterfield*, Randy Wolff SiSoft Walter Katz*, Mike LaBonte* Teraspeed Labs Bob Ross* Michael Mirmak convened the meeting. No patents were declared. Justin Butterfield took minutes. Review of minutes from the October 10 meeting: Mike LaBonte moved to approve. Bob Ross seconded. Minutes were approved without objection. Review of minutes from the October 9 meeting: Arpad Muranyi had noted a correction over email to change the sentence: "Arpad commented we do have some definitions for these terms in the General Rules section." to "Arpad commented we do have some definitions for such terms at the beginning of the Multi Lingual Modeling section." Mike moved to approve with this change. Bob seconded. Minutes were approved without objection. Review of ARs: - Mike to look into why the email regarding Touchstone files from Radek Biernacki was not sent out. - Michael also did not received the email. Mike reported he has not had a chance to look into this, but it could be a Freelist problem. Radek stated he will resend the email to the Editorial reflector. - Mike to post the latest IBIS 7.0 draft and checklist. - Michael noted this was done. - Arpad to research the conflict between BIRD196 and BIRD186.4. - Arpad reported this was discussed at the IBIS Open Forum meeting. Radek stated we need to add an item for this to the checklist. Mike noted this was a clarification instruction with the motion to approve BIRD196. Opens: - None. Touchstone terminology discussion: Radek noted the issue is that we do not have connections to Touchstone files but we have connections to Touchstone components. Arpad commented we have connections to circuit models. Michael stated that we do not have the phrase "connections to Touchstone files", but we now say "networks described by Touchstone files". Radek thought we could clarify by saying "n-port networks", but he agreed that this change addresses the issue. Arpad stated he does not like the term "n-port network", as all Touchstone files will have at least one port. Michael asked if there is any alternative to "n-port". Mike stated that since the term "IBIS-ISIS subcircuits" is used in this sentence, he suggested to add "n-port". Michael asked if "n-port" should be upper case or lower case. Arpad noted that "N+1" has a capital "N". Bob stated "n-port" is a different concept and suggested to use lower case. Michael made the change and asked if this issue can be closed. Radek and Arpad agreed with this change. Bob asked about the examples where the phrase "Touchstone files" appears. Michael replied that the examples are referring to the actual files. We marked checklist item 42 as verified. Editorial review of ver7_0_181016.docx and the task checklist: Michael asked about checklist items 47 and 48 which were moved to the Finalization steps. Mike replied that we did not delete these items, as we did not want to change the numbering of the subsequent items. Michael asked about checklist item 46 regarding some comments from Bob. Mike noted this is in BIRD189.7 on page 26. The issue is that the Param subparameter has a format column which only has "Value" as an entry, and we added some text stating this. Mike thought that we might need a BIRD for this change. Bob stated the issue is that it is odd to we have "Value" in the format column and value as the last column heading. Michael stated this is a clarification change. Mike added we are clarifying what we believe are the rules. Michael asked if we have any other formats other than Value. He noted we could expand on this later, and this is for future enhancements. Radek stated the question is on the future direction. He raised the issue of how would we instantiate subcircuits with the other methods such as Corners. He would rather have separate definitions of subcircuit instances. Walter Katz stated we can defer further discussions on Corner, and asked if there is anything preventing us from changing it in the future. Bob thought there is not. Radek thought either way is okay. Bob stated we could define a different name for parameter corner. Mike noted that the added sentence is obvious but unstated. Other changes such as removing the format column would require a new BIRD. Mike suggested that this would need to be done now to address IBIS 7.0. Michael noted it is easier to remove restrictions than to add them later. Bob stated we can change the structure to add columns later. Walter commented for the purposes of these meetings the wording is correct. Michael suggested to take up the discussion in ATM. Michael stated the checklist item 54 relates to BIRD196. We still have the text "a stem and an ending period". Arpad suggested to remove the text "or a stem and an ending period and no extensions (e.g, xyz.)" . Mike agreed. Radek thought we need to be more specific and asked what the BIRD states. Michael showed BIRD196. Radek agreed with removing the entire phrase. Michael changed all four instances of this phrase. We marked checklist item 54 as verified. Michael noted the checklist item 56 is on the phrase "relative path". Mike commented we do not need to check the phrase in the EBD and AMI sections. Bob commented that where file reference is used we should mention the relative path. Michael stated neglecting the EBD and AMI sections, these are covered. Mike stated we can mark this as complete. Walter agreed. We marked item 56 as verified. Michael stated checklist item 57 is regarding the Section 10.6.1 redundant text. Mike commented that we now have these paragraphs next to each other, and this is an issue. Michael commented in the second paragraph we list out all the clock recovery parameters and are more specific. He asked if there are any technical differences between the paragraphs. Walter thought we should remove the second paragraph. Arpad asked if we should combine the paragraphs. Michael was concerned that if we add any new parameters they would need to be added to the specific list in the text. Radek asked if the second paragraph covers all the parameters. Michael found that the Rx_Clock_PDF parameter description was not under this section but was with Rx_sensitivity. He asked if we want to move Rx_Clock_PDF. Radek asked if this is the correct place. Michael suggested to continue this discussion in the next meeting. Michael will send out the latest draft and checklist [AR]. Mike proposed to send out a note for a vote about including BIRD196 in IBIS 7.0. He commented there was no motion in the IBIS Open Forum, but a vote is anticipated. Bob noted that we should document the BIRD196 changes in the checklist. Michael agreed. Mike moved to adjourn. Arpad seconded. The meeting adjourned without objection. The next meeting will take place Wednesday, October 17, at 8 AM Pacific. Open Technical Questions: 1. BIRD182: POWER and GND [Pin] signal_name as [Pin Mapping] bus_label a. Is a bus_label created even if we don't have [Pin Mapping], [Bus Label], or [Die Supply Pads] through the [Pin]? b. Is a bus_label short created for legacy package models based on the second column of [Pin] when we do not have a [Pin Mapping] entry?