================================================================================ 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 September 28, 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 September 26 meeting: Arpad Muranyi moved to approve with this change. Bob Ross seconded. Minutes were approved without objection. Review of ARs: - Michael to send out the latest IBIS 7.0 draft and checklist to the group. - Michael reported this was done and thanked Mike LaBonte for posting. Opens: - Bob commented that in the Table of Contents the capitalization of section titles is inconsistent and whether the text is bold is also inconsistent. He requested that we should review this. Michael noted the very last checklist item is to address these issues, and he agreed that the Table of Contents will need some edits. Editorial review of ver7_0_180928.docx and the task checklist: Michael stated we will add BIRD196 to the checklist once it is approved. We started with checklist item 34 which is for BIRD187.3 the Format and Usage Out Clarifications. This BIRD adds text to the "Format" section and addresses the fact that some of the text was not in complete sentences, although other sections may still have this issue. Michael noted we will also need to check the spacing of the text. Bob commented we may have other sections that have this issue. Michael agreed and stated the technical editor we used to start the Word document was very knowledgeable about this, but it has since become more of a problem. Michael stated after some of the equations at the end of a sentence do not have periods. He asked if it is okay to add them. Arpad agreed and noted that we have a period in the other sentences ending with equations. Bob commented that technical papers are not consistent in this manner. Michael noted the phrase "executable model file" was added by a different BIRD that made changes to this section. Mike asked which BIRD this was. Michael replied that this was List clarification BIRD. He asked if this is consistent with our file naming rule changes. Mike noted that he prefers to remove the word "file". Arpad agreed. Michael stated the Combination and Corner Rules section has some text clarifications and wording changes. The phrase "AMI parameter" was changed to "AMI parameter formats". We marked checklist item 34 as verified. Michael stated checklist item 35 is BIRD 188.1 which is the Rx Noise support BIRD. The Rx_Noise parameter is expanded to include the Rx_GuassianNoise option. Michael noted the underscore was missing in the draft. The AMI_Version is listed as 7.0 rather than 6.2. And, the units are now specified in the equations. Bob asked about the indentation of the definitions starting with the word "where". Michael replied this is consistent with the other sections. Michael noted we have a new parameter called Rx_UniformNoise. Mike asked about the notes following this section. Michael replied these are notes from 6.1 which relate to the previous parameter definitions. He asked if we should move these notes under the appropriate parameters. Bob was concerned about rearranging sections. Michael noted we have a bigger issue. For instance, we have an introductory paragraph about Reserved Parameters with no heading. Mike suggested to add a header and come back to this section. Michael added "Receiver Reserved Parameters" as a header. He noted we have the same issue on page 238. Michael stated in most of the IBIS specification we are very clean with definitions only in a particular section, but in this section we have introductory text in the middle of the section. Bob commented we have to be careful that the note is about the following text and not the preceding text. Michael asked about the notes on page 243 and if we want to move them. Arpad thought the first note should be moved after the Rx_Clock_Recovery_Dj. Bob asked if this should be a note or a paragraph. Michael commented that this text is saying where these parameters can be used, he thought it could at either the beginning or at the end of the section. Bob asked if the note has terms that have not been defined. Michael replied it does. Bob commented in that case the text should be at the end. Mike thought it is a trade-off between forward referencing and getting lost at the end of a section. Bob stated if we move the text to the top of the section we should state the forward reference. Mike suggested to add the word "below" and move the text to the top of the section. Michael noted that the opening paragraph is saying the same thing as the note in question. Bob asked if we can remove one of the paragraphs if they are redundant. Michael added a checklist item to resolve this issue. Michael stated there is an additional note referring to the Rx jitter parameters. He noted that the opening paragraph of this section does not have the same problem with redundant statements, so we can move this text. Michael also added the word "below" to the first sentence. Bob asked about the reference to the table and if the table covers everything in this section. Michael replied it covers everything. Mike noted a missing parenthesis on page 239. Michael asked if the Rx_Receiver_Sensitivity is part of the list of parameters. Mike replied it is. Michael stated the table is in the correct place, as it is at the end of the section. Bob asked if the table is part of a subsection. Michael asked if the table should be its own section and added a checklist item about this. Michael stated, on page 242, the text needs to become a new subsection. Mike commented that this text if for the noise parameters. We marked checklist item 35 as verified. Bob noted one issue is the heading formating and we have mixed case headings and different fonts at different levels throughout the document. We do not want subheadings as bold compared to headings above in the hierarchy. Michael agreed and noted that this is covered in the second to last item on the checklist. Michael asked when we want to hold the next meetings. He proposed to have meetings on Wednesday and Friday next week. Arpad asked if want to use the ATM time for editorial work. Michael thought we had discussed to use the ATM time to discuss the future EBD improvements proposed by Walter. Arpad noted that the ATM meeting is canceled for next week, as it was proposed for everyone to review the IBIS 7.0 draft. Michael will send out the latest draft and checklist [AR]. Mike moved to adjourn. Bob seconded. The meeting adjourned without objection. The next meeting will take place Wednesday, October 3. 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?