next up previous contents index
Next: Skeleton Mode Up: The Convert Menu: Data Previous: The Text Editor Button:   Contents   Index


The Edit Parameters Button: Edit Conversion Parameters

This command brings up a text editing window displaying the LongName, Description, StreamIn, StreamOut, and NoDrcDatatype lines for the current layer, as they would appear in the technology file. Changing the current layer will update the listing to the parameters for the new current layer. The user can add new lines or modify existing lines as desired. The Save Tech button in the Attributes Menu can be used to write a new technology file containing the modifications.

To add a specification, select the desired keyword in the Keywords menu of the editor. The user will then be asked to enter the associated text on the prompt line.

Clicking on a line in the listing will select the line. The text for the selected line can be edited, or the line deleted, with the Edit and Delete buttons in the editor's Edit menu. The Edit menu also contains an Undo button, allowing the last operation to be undone.

The syntax for the keywords is described below. The LongName and Description fields of layers are multi-purpose and do not exclusively pertain to conversion functions. Their inclusion in this editor is due to lack of a better place for this functionality. The remaining parameters are specific to conversion, and in fact GDSII and OASIS conversion only.

LongName longname
This will set (or reset) the long name field of the current layer. If no non-space characters are found after the keyword, the statement is ignored. Leading and training white space is removed from the argument.

Description description_string
This will set the description field of the current layer. If no non-space characters are found after the keyword, the statement is ignored. Leading and training white space is removed from the description string.

StreamIn layer_list [, datatype_list]
This keyword specifies a set of layer/datatype combinations that will map to the present Xic layer when reading GDSII and OASIS files. Any number of such lines can be present. The layer_list is a space-separated list of tokens, each of which is either a GDSII layer number (``32'') or a range of numbers (``35-41''). The datatype_list is similarly constructed, and is optional. The numbers in either list can range from 0 to 255. If a datatype_list appears, it is separated from the layer_list with a comma. The line specifies that each of the datatypes listed on each of the GDSII layers listed will be converted to the present Xic layer. If the datatype list is absent, it defaults to ``0-255''. For example,
StreamIn 5 7 8 21-30, 0 20-63
specifies that datatypes 0 and 20-63 on GDSII layers 5, 7, 8, and 21-30 will be mapped to the present Xic layer as a GDSII or OASIS file is read. Note that GDSII layers cam be mapped to more than one Xic layer. In this case, the geometry will be created on each of the Xic layers mapped to.

StreamOut out_layer [out_datatype]
This line specifies a layer/datatype combination to be used when generating GDSII and OASIS files for the present Xic layer. One of these should appear for each Xic layer. The out_layer and out_datatype can be in the range 0 - 255. Note that often the end of range values are reserved in other CAD environments, and that some releases of the GDSII format support only 64 layers and datatypes. The default datatype, if not given, is 0. If there are more than one StreamOut lines given for a layer, the objects will be added to the GDSII or OASIS file on each of the GDSII layers specified. There is no default.

NoDrcDatatype datatype
If this keyword is given, then any object that has the given datatype will be ignored during DRC. On output, objects that have their DRC skip flags set will be written with this datatype, and not the default datatype given in the StreamOut line. The given datatype should appear in the input mapping for the layer.


next up previous contents index
Next: Skeleton Mode Up: The Convert Menu: Data Previous: The Text Editor Button:   Contents   Index
Stephen R. Whiteley 2006-10-23