================================================================================ IBIS EDITORIAL TASK GROUP http://www.ibis.org/editorial_wip/ Mailing list: ibis-editorial@freelists.org Archives at http://www.freelists.org/archive/ibis-interconn/ ================================================================================ Attendees from September 26, 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 19 meeting: Arpad Muranyi moved to approve with this change. Mike LaBonte seconded. Minutes were approved without objection. Review of ARs: - Arpad to write a BIRD to prevent file names ending with a period. - Arpad reported this was done. Michael noted this was discussed in ATM, and the BIRD has been submitted to the IBIS Open Forum. - Michael to send out the latest IBIS 7.0 draft and checklist to the group. - Michael reported this was done. Opens: - None. Editorial review of ver7_0_180926.docx and the task checklist: Michael reviewed that we need to finish BIRD186.4 regarding the File Naming Rules. We had went through all of the text changes for the Converter_Parameters section not taking into account BIRD196, but we stopped short of the changes to the examples. Arpad asked if we are going to implement the changes from BIRD196 now or wait until it is approved. Michael replied he prefers to wait until the BIRD is approved in case there are any last minute changes. Michael noted the Converter_Parameters changes are done, although the current draft does not consider the BIRD196 changes. He noted the examples changed file_name to file_reference for the column headings. The name "MyVhigh" was also changed to lower case. Michael stated, in the Package Modeling section, there was a small change to package_file_name which is now ".pkg". The Usage Rules for .Pkg File section has the same change, but the ".pkg" in this case has a trailing period. Arpad suggested to delete the period. Michael stated the EBD section also changed filename to "". The .ebd also has the period removed when referring to the extension. Arpad suggested to add quotes around "ebd". Michael asked if we should do a global check for the extensions and add the quotes. Arpad thought we should. Michael added a new checklist item for this task. Michael noted the Reference Designator section was changed. Arpad asked about the phrase "file reference name". Michael thought this was okay. Bob Ross stated the file reference is a file name with a relative path, but it is not a full path. Michael noted the way this text is written the parser and EDA tool would have to search down all subdirectory paths to find the file. Arpad asked about removing the word "name" and calling it "file reference". In this case, we do not exclude the path. He noted we may have cases where a file with the same name exists in different subdirectories. Michael noted the phrase "file reference" is defined to include the path. He asked if we want to say the file name or file reference and if we want to change the text in the Reference Designator Map section. If we say file reference, we are allowing paths in the second column of the [Reference Designator Map]. Arpad asked if there is a character limit on that column. Bob replied there is not. Michael asked if we want to specify the exact path or let the parser find it in subdirectories. Bob thought we want to specify the exact path. Arpad asked how this is worded in other places in the specification. Michael replied that the .ami file has a similar issue in the [Algorithmic Model] keyword section. He changed relative "paths" to relative "path" in the [Algorithmic Model] section. Bob commented that we have the the same problem for DLLs. Mike reiterated Arpad's earlier point that we could have files with the same name in different paths. Michael, in the [Reference Designator Map] section, changed "file reference name" to "file reference", and changed can exist to shall exist. Mike suggested to align the component_name column names and to add a path to one of the example file references. Bob commented that this is a strange place to introduce the example. He suggested to add examples to the base IBIS sections. Mike commented he did a search on backslash, and we do have a rule that backslashes would be converted to forward slashes as required by the operating system except for DLLs. Arpad asked if we need a "./" before the file names in the [Reference Designator Map] examples. Bob replied this is prevented by the rules. Michael stated the executable section is also changed, and AMI_Executable is now the official name. He noted that we now say file reference. The word "path" is now singular per our earlier change. Mike commented that "ami" should be in quotes. Michael noted that AMI parameter definition file name is now root name. We verified the changes in the Supporting_File section. There are also some minor changes under DLL_ID. Michael asked about the word "name" and if it should be "file name". Arpad thought it is okay to leave it as "name". Bob agreed. Michael noted the last change from BIRD186.4 is to change the 120 line length restriction to 1024 characters. Originally, this was in four places in IBIS 6.1, but we have an additional place in IBIS 7.0. We marked check list item 33 as verified. Mike noted there is only one place we need to add quotes for the extension was one case for "ims". Michael stated this was a good a find. He marked this checklist item as verified. Michael will send out the latest draft and checklist [AR]. Mike moved to adjourn. Arpad seconded. The meeting adjourned without objection. The next meeting will take place Friday, September 28. 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?