Thanks Curtis for remembering that suggestion. I can actually several ways of
wording it, but the way we have it is technically incorrect according to our
definition of vocabulary, because the file name is defined as stem + extension.
So we could say, as you suggested:
“The file name stem and extension shall use characters from”,
but we could also say:
“The file name (stem and extension) shall use characters from”
There may be other options too…
Thanks,
Arpad
===================================================================
From: Curtis Clark [mailto:curtis.clark@xxxxxxxxx]
Sent: Tuesday, September 18, 2018 4:08 PM
To: Walter Katz <wkatz@xxxxxxxxxx>
Cc: Muranyi, Arpad <Arpad_Muranyi@xxxxxxxxxx>; IBIS-ATM
<ibis-macro@xxxxxxxxxxxxx>
Subject: Re: [ibis-macro] Changes for 7.0 relating to file_name, stem,
extension and character set.
Hi Everyone,
Arpad also proposed an additional change highlighted below in blue:
3. File names shall have a stem of no more than sixty (60) characters
followed by a period (“.”), followed by a file name extension. The file name
stem and extension shall use characters from the set (space, “ ”, 0x20 is not
included), (Note that “.” is not allowed in extension):
Thanks,
Curtis
On Tue, Sep 18, 2018 at 3:58 PM, Walter Katz
<wkatz@xxxxxxxxxx<mailto:wkatz@xxxxxxxxxx>> wrote:
All,
Regarding:
6) IBIS v7.0 Section 3.2 issues (Editorial)
- Item #3 allows a period (.) to be part of the “stem” as well
as the extension of a file name. However, section 3.1 defines
extension as “The portion of a file name after the last period,
if any.”. These contradictory definitions need to be corrected.
- discussion
These are not contradictory.
* stem: The portion of a file name before the last period, or the full file
name if no period.
* extension: The portion of a file name after the last period, if any.
* file name: The name of a file without its location.
* path: A sequence of root directory (optional), directory elements and
file name that identify the location of a file. A path may be absolute or
relative.
*
Consider a file name can be xyz.def.jkl
* The extension is the portion of a file name after the last period
* The extension for this file name is “jkl”
* The stem is “xyz.def”
Item 3 in section 3.2:
3. File names shall have a stem of no more than sixty (60) characters
followed by a period (“.”), followed by a file name extension. The file name
and extension shall use characters from the set (space, “ ”, 0x20 is not
included):
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ‘ ` .
The character sequence “./” is not permitted in any reference to an IBIS file
or to any other file format, effectively restricting the naming of files to
those in the same directory as the referring file or a subdirectory of that
directory. Absolute paths - those beginning with a root name or root directory
- are not permitted in a reference to any file.
Arpad is concerned that “extension shall use characters from the set” which
includes “.”. But since extension is after the last “.”, then it cannot contain
a “.”. Do we really need to change this to say the following?
3. File names shall have a stem of no more than sixty (60) characters
followed by a period (“.”), followed by a file name extension. The file name
and extension shall use characters from the set (space, “ ”, 0x20 is not
included), (Note that “.” is not allowed in extension):
a b c d e f g h i j k l m n o p q r s t u v w x y z
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
0 1 2 3 4 5 6 7 8 9 _ ^ $ ~ ! # % & - { } ) ( @ ‘ ` .
The character sequence “./” is not permitted in any reference to an IBIS file
or to any other file format, effectively restricting the naming of files to
those in the same directory as the referring file or a subdirectory of that
directory. Absolute paths - those beginning with a root name or root directory
- are not permitted in a reference to any file.
File name should not begin with a “.”.
File name should not end with a “.”.
I do recommend that we make the following change:
The character sequences “./” and “..” are not permitted in any reference to an
IBIS file or to any other file format, effectively restricting the naming of
files to those in the same directory as the referring file or a subdirectory of
that directory. Absolute paths - those beginning with a root name or root
directory - are not permitted in a reference to any file.
* stem: The portion of a file name before the last period, or the full file
name if no period. The stem should contain at least one character.
Page 112: In addition, file names using only a stem (e.g., xyz) or a stem and
an ending period and no extension (e.g., xyz.) are permitted.
Page 132: In addition, file names using only a stem (e.g., xyz) or a stem and
an ending period and no extension (e.g., xyz.) are permitted.
6.1 says in three places
In addition, files with no extensions (e.g, xyz) or with just a dot (e.g.,
xyz.) are permitted.
Page 100, 101, 122
Walter
Walter Katz
wkatz@xxxxxxxxxx<mailto:wkatz@xxxxxxxxxx>
Office 978.461-0449 x 133
Mobile 720.417-3762
From: ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>
<ibis-macro-bounce@xxxxxxxxxxxxx<mailto:ibis-macro-bounce@xxxxxxxxxxxxx>> On
Behalf Of Muranyi, Arpad
Sent: Tuesday, September 18, 2018 1:34 PM
To: ibis-macro@xxxxxxxxxxxxx<mailto:ibis-macro@xxxxxxxxxxxxx>
Subject: [ibis-macro] IBIS-ATM teleconference - Agenda for September 18, 2018
Time: Tuesday, September 18, 2018 at Noon US Pacific Time
=====
WebEx:
======
https://sisoft.webex.com/sisoft/j.php?MTID=m1775c35b7d9a55735fbb2c67876222ba
Meeting Number: 735 161 627
Meeting Password: IBIS
Audio:
======
Voice dial-in: (800) 637-5822
International: +1 (647) 723-3937 <--- (For Canada)
0114501530 <--- (For Sweden)
0201400572 <--- (For Sweden Toll Free)
069509594672 <--- (For Germany)
08001014542 <--- (For Germany Toll free)
Access Code: 685-0440
Mentor Global Crossing Teleconference commands for audio:
http://www.globalcrossing.com/customer/collaboration/cust_ready_access_tips.aspx
---------------------------------------------------------------------
---------------------------------------------------------------------
Agenda
======
1) Opens
2) Roll call
3) Review of ARs:
Randy: Investigate if/why/how a clock waveform input might be used
- in progress
Michael M.: Investigate if/why/how a clock waveform input might be used
- in progress
Any other AR-s?
4) Call for any IBIS related patent disclosures
5) Approval of minutes
6) IBIS v7.0 Section 3.2 issues (Editorial)
- Item #3 allows a period (.) to be part of the “stem” as well
as the extension of a file name. However, section 3.1 defines
extension as “The portion of a file name after the last period,
if any.”. These contradictory definitions need to be corrected.
- discussion
7) IBIS-AMI improvements (All)
- Walter’s Summary of DDR5 Issues email
- discussion
9) Complex C_comp modeling (Randy)
- discussion?
10) Motion to adjourn?
Topic bin list:
===============
- Removing the single-ended input threshold requirements for
differential buffers
- Removing the single-ended characterization load requirements for
differential buffers
- Guidance for power-aware vs. AMI models – do we have rules for
how a power-aware (and therefore potentially non-LTI) buffer
analog data set should be used with IBIS-AMI algorithmic data?
- Fix all the referencing problems in the current specification
(after Randy’s C_comp proposal and BIRD189 are done)
- IBIS-AMI Post Simulation Processing (FEC) (Mike L.)
Tabled topics:
==============
11) New BIRDs from Editorial Task Group? (Bob/Radek)
a) Specify buffer reference terminals for pins ([Pin Reference])
b) Simulation (aka DIA) vs. DUT (depends on #a)
c) C_comp and package reference in simulation clarifications
(depends on #a)
d) Make changes to the [Receiver Threshold], once a) and b) are
resolved
12) 166.4 Resolving problems with Redriver Init Flow (Walter)
13) BIRD190 (Ambrish)
14) Fangyi’s Redriver flow BIRD draft (Fangyi)
- add equations
- consider rewriting the AMI "front end" in the spec (flows)
(when this proposal is added to the spec)
15) How to handle missing min/max data? (Arpad)
- what should be the governing rule for synchronizing
typ/min/max data?
Pending BIRDs awaiting discussion:
==================================
166.4 Resolving problems with Redriver Init Flow
181.1 I/V Table Clarifications
190 Clarification for Redriver Flow
195.1 Enabling [Rgnd] and [Rpower] Keywords for Algorithmic Input Models
TBD New proposal for Redriver Flow (may replace BIRD166)
TBD C_comp modeling with IBIS-ISS
Thanks,
Arpad
=====================================================================
