[Pixel]<Chipndale>documentation>ChipndaleTools21.tioga!11

ChipndaleTools21.tioga

last edited by: Christian Jacobi September 3, 1985 10:40:11 am PDT

CHIPNDALETOOLS 2.1

CHIPNDALETOOLS 2.1 — FOR INTERNAL XEROX USE ONLY

Chipndale

An interactive editor for VLSI designs

Some additional tools

Release 2.1

Ch. Jacobi, (with entries from Kim Rachmeler, Jim Gasbarro, Mark Shand, Ed McCreight, George Bier) et all (Sep 1, 1985)

A relatively incomplete documentation.

Filed on: [Indigo]<Chipndale>Documentation>ChipndaleTools21.tioga

Abstract: Chipndale, is an interactive graphic layout tool made to run in Cedar. Chipndale makes use of multiple windows, extensive parallel processing, vast amounts of memory, pop-up menus, and other assorted goodies. When complete, Chipndale will have a DRC and circuit extractor, a fast set of IO and checkplot routines, and modular device extensibility. What's more, everything in Chipndale will be completely technology independent, that is, all the features will be equally at home dealing with PC boards or CMOS chips.

This document document tells the designer about additional tools, like generating checkplots, masks, CIF output

XEROX Xerox Corporation
Palo Alto Research Center
3333 Coyote Hill Road
Palo Alto, California 94304

For Internal Xerox Use Only

0. General programs to run in Chipndale

Abort the program: <ESC><DEL> aborts most programs; all which do query for abort as they should.

The program menu: <SPACE>-<P> shows a menu of programs to run.

The rect program menu: <SHIFT>-<P>-middle shows also a menu of programs to run. The command allows you first to drag a rectangular area; This area is provided the program as a parameter.

Usually programs must be started first, only thereafter they register their commands. However some very important programs may have tiptable entries of their own.

1. Design rule checking

NOT YET CONVERTED TO CEDAR 6.0

DF File: /Cedar/ChipNDale/6.0/top/Spinifex21

Start program: nmosSpinifex

or cmosSpinifex

DRC/Extraction

(contributed by Mark Shand)

Spinifex - the ChipNDale DRC/Extraction Package

August 9, 1984

DF file: /Cedar/ChipNDale/5.2/top/Spinifex17.df

Documentation: SpinifexDoc.tioga (in DF file)

Maintainer: Shand

The Spinifex DRC/Extraction Package is ready for use by ChipNDale designs. What follows is a list of problem areas a new user may encounter, for more details see the documentation.

1) The design rules are not 100% complete, this is particularly true of rules with regard to well contacts (though Spinifex does insist that wells are connected to by one and only one node).

2) There is no support for `wspec' files as yet (this is coming soon).

3) The .thy files produced require some hand editing, I hope to reduce or eliminate this.

4) Aliases for signal names are not handled fully, currently one name is chosen and a comment is insert in the .thy file indicating the choices which were available to Spinifex.

5) Strays are fairly accurate but there could be bugs in this computation (if there are it is only a few percent error).

6) Spinifex could be both faster and less greedy for VM.

Spinifex/HighlightNode - highlighting electrically connected regions.

August 9, 1984

Spinifex has the ability to interactively highlight electrical nodes the command is invoked by MiddleDown WHILE Slash. If material on the current layer is found at the point indicated and it is part of a cell which has been previously extracted then all regions electrically connected to that region have boxes on the ChipNDale highlightShade level laid over them. Be warned that shading does not extend to material in cells which have not been analyzed or above the current pushed in level.

ShowErrors

July 26, 1984

DF file: /Cedar/ChipNDale/5.2/top/ShowErrors.df

Documentation: ShowErrorsDoc.tioga (in DF file)

Maintainer: Shand

ShowErrors implements a simple command to zoom a ChipNDale viewer to a rectangle on the highLightError layer. (How these rectangles get on the highLightError layer is another matter altogether, Spinifex—my layout analysis package and PTiler—Bob Mayo's module generating system are two ChipNDale clients that display errors as rectangles on the highLightError layer.)

ShowErrors is invoked by the Slash Shift command.

ShowErrors searches the cell you are currently pushed for unselected rectangles on the highLightError layer. If no rectangles are found on the highLightError layer the message No errors to show is printed, if all rectangles on the highLightError layer are selected the message All errors are already selected is printed, otherwise the viewer is panned and scaled to show the neighborhood around the first unselected rectangle found on the highLightError layer, this rectangle is selected and an informative message about the error is printed.

To use ShowErrors, bringover the public parts of the DF file listed above and type ShowErrors to the CommandTool.

2. Generating CIF files

Flat CIF

Warning: Special program!
Use hierarchical CIF if you don't have a special reason to use flat CIF.

DF File: /Cedar/ChipNDale/6.0/top/CDFlatCif21.DF

Start program: CDCMosFlatCIF

CDNMosFlatCIF

Execute: use program menu

Flat CIF creates a CIF output without any hierarchy whatsoever. See the Program menu; the Flatcif module must be run before issuing the command. The load file sets up the CIF layer names and bloats; It is a pity, but not Chipndale's problem, that reasonable designs will end up with millions of rectangles, more than most available CIF input packages can handle.

Flat CIF generates CIF output of the whole design, not only the selection.

Do check manually if the right CIF layer names and bloats are used.

Hierarchical CIF

DF File: /Cedar/ChipNDale/6.0/top/CDCifGen21.DF

Start program: CDCMosCIF

Execute: use program menu

CIF output of the whole design is generated, not only of the selection.

Do check manually if the right CIF layer names and bloats are used.

3. Plotting on the Color Versatec

DF File: /Cedar/ChipNDale/6.0/top/CDColorPDPlot21.df

Start program: VersatecNMos

VersatecCMos

VersatecChipnsil

VersatecChipnsilBW

LilacCMos

Execute: Use the hard copy menu.

Anomaly: start the program before each plot, to make sure stipples are loaded.

Plot any portion of the design you wish by selecting an area using a mouse button with 'H' held down. Terminal will request the number of vertical strips of paper you want the plot printed on; each strip will be made into a PD file named "plot(i).pd" where i is 0..(#strips -1). The plot will be made as wide as the given number of strips will allow, at 40 inches per strip. As the PD file is being generated, a '.' will be printed for every horizontal band as it is completed. An arrow will travel down the screen indicating the current band under consideration; the phrase "finished plot(s)" indicates that all strips have been done. Now you have a PD file resident on your local disk which must be transferred to the Versatec.

Sending PD files to the Color Versatec

There is a new Peach interface which allows you to chat directly to the Versatec's server. Plot requests are automatically spooled and serviced in serial order.

The new Peach package requires that your Dorado be running the latest version of STPServer. Bringover /Indigo/CedarChest6.0/top/stpserver.df into ///Commands/; start it up by saying "STPServer" to the CommandTool. To start sending the PD file, give the command:

% chat sleepy

to connect to the Chat interface with Sleepy, the Dicentra serving the color Versatec. The command to send the file is

>> Print <filename> <#copies> <title>

where the filename is [name of Dorado]<Cedar>subdirectory>filename.pd. For example, if you had created a vanilla IC plot on Seahorse, wanted only one copy, and wanted your username as a title on the plot, you would give the command

>> Print [SeaHorse]<Cedar>temp>plot0.pd 1 Smith.pa

Your print request would now queued and would be handled on a first-come first-served basis. The official documentation for the new Peach software can be found under

/Indigo/peach/documentation/peachdoc.tioga.

It's recommended reading.

Completed plots are cut off each night and left for pick-up on a table in the Purple Lab. Users are strongly discouraged from cutting off their own plots. (It is fairly difficult to install the paper properly such that the next user gets good registration on his/her plot.)

You can easily change the colors assigned to layers by editing the load files VersatecCMOS.load and VersatecCMOS.load.

4. Plotting on the Black&White Versatec

DF File: /Cedar/ChipNDale/6.0/top/CDVPlot21.DF

Start program: run vplot

Commands: Use the hard copy menu.

DOES NOT YET RUN WITH CEDAR 6.0

I DO NOT KNOW HOW TO DEAL WITH STIPPLES...

Manipulate the design in the viewer so that you can see the entire amount of information you want to print. Hold down H , and with the left button down, draw a rectangle containing that part of the design that you want to come out on paper. When you release the button, Terminal will ask you to select the number of strips you want the design to be printed on (for all you VLSI wallpaper fans). A new viewer will appear, showing the middle of the horizontal stripe currently under consideration. An arrow pointing to the design will show you how far the transfer has progressed. After the transfer is complete, the connection to the Alto will be closed and the Trident file "plot.bits" will be printed on the Versatec. This routine should not break even on large and complex designs.

5. Press files

DF File: /Cedar/ChipNDale/6.0/Top/CDPressPlot21.DF

Start program: CDPress

Commands: Use the hard copy menu.
(Draw a rectangle with the mouse, holding H down)

Only black and white! No stipples. Useful for ChipNSil.

Use press printer (Rock'roll or Stinger) does not work on spruce or ShowPress. Sorry, the program is quite slow and right now fails in plotting most fonts...

Press files should be discarded in favor of Interpress files anyway.

6. Interpress files

DF File: /Cedar/ChipNDale/6.0/Top/CDInterpressPlot21.DF

Start program: CDInterpress

Commands: Use the hard copy menu.
(Draw a rectangle with the mouse, holding H down)

Only black and white! No stipples. Useful for ChipNSil.

Interactive options for single page, multi pages, or stripes (versatec plotter)

Interactive options for plotting a particular rectangle or the whole design.

Interactive options for a font substitution file. Default substitution file is the file CDSubstituteFonts.SubstituteFonts.

7. Recognizing primitive objects

DF File: /Cedar/ChipNDale/6.0/top/CDRecognizer21.df

Start program: CMosRecognizer

NMosRecognizer

Execute: Use the Program menu

Recognizer will replace drawn transistors and contacts with the corresponding ChipNDale primitive. It is particularly useful for ReadCif designs since ReadCif does not know about ChipNDale transistors etc. From the program menu two choices for invocation of the command exist: "Recognize All" will traverse the hiearchy of the design finding transistors throughout the whole design and "Recognize Top" which will only search the top level of the design.

7.b. Removing Overlapping Wires

DF File: /Cedar/ChipNDale/6.0/top/CDOverlapRemover21.df

Start program: CMosCifOverlap

Execute: Use the Program menu

CMosCifOverlap finds all wires of type ndif that lie completely on top of wires of type pdif and removes the ndif wire from the design. Its most probable use is after reading in a design using XeroxCmosCif. Currently when reading in a design using XeroxCmosCif, all rects of type pdif in CIF are given a ChipNDale representation of both an ndif and pdif wire. CMosCifOverlap can be used to remove the ndif.

OverlapRemover is a general tool that takes two layers, a keepLayer and a throwAwayLayer, and whenever a wire of type throwAwayLayer is found that lies completely on keepLayer, then the throwAwaLayer wire is thrown away. An example of how to register the layers can be found in /Cedar/ChipNDale/6.0/CDOverlapRemover21/CMosCifOverlapImpl.mesa

8. Generating Labels

DF File: /Cedar/ChipNDale/6.0/top/CDLabel21.DF

Start program: CDLabels

Commands: Use the rect-program-menu.

Command asks for a font name, a scaling factor and a text. (use a .strike font)

A cell for the label is created included into the design. It uses the current layer for the material of the cell.

The program tries to re-use characters made before; It uses their cell name; renaming of characters should therefore be done carefully or not at all.

It might be a good idea to make a special file containing the labels and importing them. Labels consist of surprisingly many rectangles, which do not always need be read or written.

To reduce the count of rectangles it is good to use a small font and a big scale factor.

9. Counting features

DF File: /Cedar/ChipNDale/6.0/top/CDCounting21.df

Counting all the (flat) rectangles of a design

Start program: run CDCountCommands

Command: Use program menu.

Counting static features of all designs

This is more of a debug tool than real user stuff.

Start program: run SweepCollectableStorageImpl CDCount

Commands: CDCount (to the command-tool)

Command will analyze all of the virtual memory and write how many Applications, Objects, Cells and Designs are stored totally.

10. Reading CIF Files

DF File: /Cedar/ChipNDale/6.0/top/ReadCif21.df

Start program: XeroxNmosCif, XeroxCmosCif, MosisCmosCif, StanfordCmosCif, etc.

Commands: ReadCif <filename>(.cif)

Maintainer: Jim <Gasbarro.pa>

ReadCif is a package for reading cif format files. It implements all of the cif primitives defined in Mead and Conway including arbitrary (i.e. non-rectilinear) polygons, wires, flashes, etc. Reading cif files can be complex for several reasons: 1) there is no standard definition for cif layer names and 2) cif files usually represent the mask image rather than the drawn image. ReadCif attempts to deal with these problems by allowing the user to specify in a command file the cif name to associate with a Chipndale layer and a compensation to apply when drawing the object.

Running ReadCif

ReadCif currently knows about the following technologies: XeroxCmosCif, XeroxNmosCif, MosisCmosCif, StanfordCmosCif, and ChipwichNmosCif. These names are command files which can be run from the Commander to register a particular technology with Chipndale. These command files register a new command "ReadCif" which is then used to read a cif file. ReadCif defaults the .cif extension if it is not supplied. Examples:

% XeroxCmosCif

% ReadCif Frog.cif

% ReadCif Cow

% StanfordCmosCif

% ReadCif Pig

...etc.

Making a new command file

The best way to make a new technology command file is to start with an existing one. ReadCif19.df contains several. Pick the one which is closest to you application.

The first line of the command file insures that the Chipndale technology you expect to use is loaded. Currently this can either be CDCmos or CDNmos. ReadCif has to register a Chipndale technology type when it creates a new design. It selects the technology type based upon the first character of the first layer command in the cif file. For example if the fist layer command is:

L ND;

ReadCif will create the design using Chipndale Nmos technology. Similarly, for the cif command:

L CNW;

ReadCif will create a design using Chipndale Cmos technology.

A layer is registered with Chipndale by issuing an interpreter command of the form:

← %CDProperties.PutPropOnLevel[onto: %CMos.met2, prop: $CDxCIFName, val: "CM2"]

This associates the cif layer name CM2 with Chipndale layer %CMos.met2 which is really just second layer metal. A more complicated registration would be:

← %CDProperties.PutPropOnLevel[onto: %CMos.nwel, prop: $CDxCIFName, val: NEW[%CIFIntPhase2.CIFDestRec ← [cifDest: "CNW", deltaRadius: -4000 -- nm --]]]

This associates cif layer name CNW with Chipndale layer %CMos.nwel and in addition causes ReadCif to bloat the geometry by 4 microns (the sign of the transformation indicates the change in size when the cif file was generated, this is for compatibility with BrandyCIFter). Mask compensation is done in a simple-minded manner; rectangles that were touching before compensation may end up disjoint, so be careful when using compensation.

If a layer command is specified in the cif file, but no such layer is registered with ReadCif then a warning message is printed on the terminal and all future objects on that layer are discarded. This allows extra layers (such as implant masks associated with diffusions) to be thrown away intentionally.

It is strongly recommended that each command file register some cif layer name with every Chipndale layer. This prevents interference from previously run command files. To find out the valid Chipndale layers for a particular technology, look in the file:

/Indigo/Chipndale/©©/CD@©/<technology>.mesa
e.g. /Indigo/Chipndale/6.0/CDCmos21/Cmos.mesa.

8. Read and write of Chipmonk files

DF File: /Cedar/ChipNDale/6.0/top/cdcmos21.DF

/Cedar/ChipNDale/6.0/top/cdnmos21.DF

Start program: CDReadCmCmos or CDReadCmNmos have load files to run the programs

Commands:
CDReadCmCmos for input
CDReadCmNmos for input
Use the IO menu for entry chipmonk output.

CDReadCMNMOS, CDReadCMCMOS {optional filename}

If the filename is not specified, ChipNDale will query for one.

(The crazy names stand for

ChipnDaleReadChipMonkNMOS and

ChipnDaleReadChipMonkCMOS)

Commands: CDReadCmCmos for input
CDReadCmNmos for input
Use the IO menu for entry Chipmonk output.

When reading Chipmonk files, it is important to know the technology associated with that design so that you use the correct form of the read command. The Chipmonk files do not contain the ChipNDale technology.

The IO pop-up menu allows to create backwards compatible chipmonk output. (.chip file). This command is restricted to CMOS and NMOS IC designs. Try to avoid switching between the Chipmonk and ChipNDale worlds frequently; on every transfer you may loose some information. Not all ChipNDale features can be written onto Chipmonk compatible files. Not all Chipmonk representation of objects can be represented in ChipNDale, mainly those which can not be fabricated safely are excluded.

The commands to read and write Chipmonk files are in seperate configs and loaded on demand only.

9. Chipmonk compatible colors

A program exists which enables ChipNDale to read the color map description and the color pattern description files of Chipmonk. These commands are active only while a 4-bit per pixel device is used for display. (The general ChipNDale command CDColor allows you setting of 4 bit per pixel mode.)

DF File: /Cedar/ChipNDale/6.0/top/cdcmos21.DF
/Cedar/ChipNDale/6.0/top/cdnmos21.DF

Start program: run ChipmonkColors

Commands:

CDColorMap {optional filename} {optional number}

This command allows to set up Chipmonk compatible colors. Ask for a colormap number and sets up the colormap. n>0 is an entry from a colormap file. A filename allows to read another colormap file. If no parameter appears on the commandline, chipndale will query you for a number.

CDPatterns {optional filename} {optional number}

This command allows to set up Chipmonk compatible colors. Ask for a pattern number, changes NMOS and CMOS to use this number to represent color patterns. 1 means Chipmonk's default patterns, n>1 is the entry on a pattern file. A filename allows to read another color pattern file. If no parameter appears on the commandline, ChipNDale will query you for a number.

It also implements some entries in the <SPACE>-B pop up menu

User profile entries

--The following color map and pattern entries are interpreted by the ChipmonkColors program.

ChipNDale.ChipmonkColorMaps: " ... default.CDColorMaps"

-- better use a full path name

ChipNDale.ChipmonkColorMapNum: -1

-- in four bits per pixel mode only

-- <0 use default colormap

-- 0 use default colormap, but read in the colormap file

-- >0 use a colormap from the ChipmonkColorMaps file as in profile

-- better use a full path name

ChipNDale.ChipmonkColorPatterns: " ... default.CDColorPatterns"

-- NMOS and CMOS only

-- better use a full path name

ChipNDale.ChipmonkColorPatternNum: 0

-- currently cmos only

-- <0 use entry from ChipmonkColorPatterns file

-- with positionkey = ABS[ChipmonkColorPatternNum]

-- (to get positionkey -0 use 1)

-- 0 use default colorpatterns

-- 1 use chipmonks default colorpatterns

-- >1 use entry from ChipmonkColorPatterns file

10. Generating Program Text

DF File: /Cedar/ChipNDale/6.0/Top/CDMakeProc21.DF

Start program: CDMakeProc

Commands: Use the program menu and select "make text"

The command generates a file (and a viewer) with a program text. This program will generate the selected object... Of course you have to compile and run the program first.

There is no guarantee that the generated program will run with any other ChipNDale version than the one used to generate it. It might be more work to transfer source text to a newer ChipNDale version, than to transfer the .dale file.

Not all ChipNDale features are handled for the program; Give it a try, look if the command generates a program powerful enough, or, if not, you have bad luck.

I do not intend to do any AI to get an optimal program...

11. Generating MEBES files

DF File: /Cedar/ChipNDale/6.0/Top/CDMEBES21.DF

Start program: CDMEBESForMPC55.load or similar (see below)

Commands: Use the program menu and select "MEBES mask generation"

By: Ed <McCreight.pa>

This utility does two things. The first is to generate a set of MEBES Mode I/II pattern files from which the mask tooling for a design can be generated by a mask house. Along with these pattern files the utility generates an "archive tape header" file that must be written as the first file on a magnetic tape containing the pattern files. All of these files are put into a subdirectory specified by the $CDMEBESMaskSetName property of the design, and the entire subdirectory should be written by the TapeTool onto a tape. The important TapeTool parameters are 1600 bpi and 2048-character blocks.

The other function of this utility is to measure various mask areas, perimiters, lengths of minimum-width coverage and space, etc. These numbers, together with yield measurements of process monitor test structures, can be used by a foundry to predict fabrication yield.

Now for the parameters. The first is the variable CDMEBES.stripesPerClump, which controls a space-time tradeoff inside the package. It should be set to the largest positive integer value that does not induce thrashing. The default value is 10, which is fine for simple designs, but for the most complex designs it may have to be set as low as 2. One day I might automate this setting...

Another group of numeric parameters, measured in nanometers, are registered as properties of the technology. The values of these parameters are REF INT's, or more suggestive, REF CDMEBES.Nm. The first parameter, $CDMEBESNmPerLambda, gives the multiplicative scale factor that relates CD.lambda to nanometers on the mask. The second, $CDMEBESNmPerEBESPixel, gives the nominal MEBES pixel size in nanometers. As of this writing there are only two useful values for this second parameter: 500 and 250. This parameter must be uniform over an entire wafer, and we are using the value 500 for technologies with two-micron minimum feature sizes (it's considerably less expensive than 250). Notice that the MEBES pixel size constrains the reasonable choice of NmPerLambda: all positions and feature sizes must resolve to integral pixels.

The next two numeric parameters, $CDMEBESXNmPerDie and $CDMEBESYNmPerDie, describe the final die size, including a half-scribe-line perimeter if appropriate. CDMEBES will center the design within this die. It's not smart enough to try rotating the design if it won't fit; you have to do that yourself. The next parameter, $CDMEBESActiveToScribeCenter, describes the minimum spacing from any design-generated mask feature to the edge of the die (meaning the outer edge of the half-scribe-line). The final parameter, $CDMEBESNmMaxBloat, is at least as large as the maximum diameter by which any ChipNDale layer in this technology enlarges to produce a mask feature.

The next parameter is the seven-character ROPE mask set name. It should be registered as the $CDMEBESMaskSetName property of the design, but there is also a default name registered as the same property of the atom $MEBESMask. A typical mask set name would be "MPC55AW", meaning Xerox MPC series, run 55, wafer A, die W.

The final parameter specifies the set of masks to be generated. It is registered as the $CDMEBESMaskSetSpec property of the technology, and its value is a LIST OF REF ANY. Each element of this list must be either a CDMEBES.MaskSpec or a CDMEBES.CoverSpec.

If a mask m is specified as a CDMEBES.MaskSpec ( = REF CDMEBES.MaskSpecRec[ name: ROPE -- a two character decimal number -- , cover: CDMEBES.CoverSpec ] ), real pattern files sufficient to cover the die will be generated, and their names will like ///MPC55AW/MPC55AW10.AA, ///MPC55AW/MPC55AW10.AB, ///MPC55AW/MPC55AW10.AC, ..., ///MPC55AW/MPC55AW10.BA, ///MPC55AW/MPC55AW10.BB, ..., where MPC55AW is the mask set name of the design, and "10" is the two-character ROPE m.name of the mask layer being generated. Usually one pattern file is sufficient to cover a die, but for large dice a regular array of pattern files (whose row and column are indicated in the filename suffix) is generated. In the latter case, that is, if a mask is specified as a CDMEBES.CoverSpec, then no pattern files are generated.

If a mask is simply specified as a CDMEBES.CoverSpec, it is computed and then discarded. This behavior is useful mainly if CoverSpec is an analysis function like $MeasureRuns.

A CDMEBES.CoverSpec is one of the following:

Boolean combinations

LIST[$NOT, CDMEBES.CoverSpec]

LIST[$AND, CDMEBES.CoverSpec, CDMEBES.CoverSpec, ...]

LIST[$OR, CDMEBES.CoverSpec, CDMEBES.CoverSpec, ...]

LIST[$ANDNOT, CDMEBES.CoverSpec, CDMEBES.CoverSpec]

Complex functional combinations

CDMEBES.Enlarge

= REF CDMEBES.EnlargeRec[basis: CDMEBES.CoverSpec, deltaDiameter: CDMEBES.Nm ← 0]

LIST[$RestrictNImplant, maxGrowth: REF CDMEBES.Nm, ndif: CDMEBES.CoverSpec, pdif: CDMEBES.CoverSpec]

... others as needed

Complex analysis specifications

LIST[$MeasureRuns, maxCoverInterest: REF CDMEBES.MEBESPixels, minCoverFeature: REF CDMEBES.MEBESPixels, maxSpaceInterest: REF CDMEBES.MEBESPixels, minSpaceFeature: REF CDMEBES.MEBESPixels, geom: CDMEBES.CoverSpec ]

.. this computes geom and then measures its area and perimeter. It also produces a table of lengths for various feature widths (in MEBES pixels up to maxInterest), and complains about features smaller than minFeature, separately for areas covered by geom and spaces in between.

Basic

CDMEBES.CDLayer

= REF CDMEBES.CDLayerRec[source: CD.Layer, deltaDiameter: CDMEBES.Nm ← 0]

CDMEBES.Scribe

= REF CDMEBES.ScribeRec[dieEdgeToLineCenter, lineWidth: CDMEBES.Nm ← 0]

For further examples of parameters, see the files CDMEBESForMPC55.load and CDMebesAnalyze.load.