Design Conversion Tool Sergey Yevstigneev, Boris Ryakhovsky ...

used when further execution of the tool is useless, e.g. when no space on disk isleft for required intermediate files creation.Information about objects currently processed and number of issues found islogged to the log file and CIW.After Scan stage completes, the form with gathered data (Scan Data form)appears. Unless any data found – a message about it appears and tool finisheswork. The Scan Data form contains two listboxes, "Available data:" - with founddata and "Chosen data:" - with data (issues) which you chose to be fixed. Eachline in listbox represents one issue, found while scanning. It contains instancemaster, name, address (library, cell, view), id of issue, issue description.Auxiliary buttons “All”, “None”, “Choose”/”Unchoose”, “Chooseall”/”Unchoose all” allow handy selection of the issues. “Information” buttondisplays expanded generated by plug-in information about each issue cause.Cyclic field “Sort by” allow to sort issues by any field. "Check schematics"button allows to use standard Cadence “Check&Save” functionality before eachschematic view closing with printing results to log and CIW.Unless Action stage desired, the original list of found issues can be saved bypressing "Save scan data" button for future use. File name is set by file managerdialog. To avoid repeated database scanning for someone reason, e.g. whenaction stage failed due to write-protected database, previously saved data can beloaded in main form by “Load scan data” button, thus replacing Scan stage.After pressing “OK” button fixing of all chosen issues begins. Process isreported to CIW and log file. Issues which require no action are skipped.Disregarding absence of any stage, at the end of work the tool performs deinitializationof plug-ins to clean up environment.Plug-insActual design database problem resolving is provided by specially preparedSKILL utility or utilities set. They could be involved in the database conversionprocess if several pre-defined rules are supported. The utilities could bereasonably named as plug-ins for Design Conversion tool. The followingconditions should be satisfied to successfully register and execute a plug-in byDesign Converter:plug-in configuration file should be named with “.il” extension and locatedaccording to known TDK sub-directory or DESIGNCONVERSION_PATHSKILL variable in case of generic mode;all SKILL procedures which are used by plug-in should be defined before theplug-in registration.correct set of keywords and their values should be available in the plug-inconfiguration, this information should be followed by the next template:; $keyword: value $Plug-in configuration could be done either as separate file or usually could bemerged with correspondent SKILL procedures. Below is a list of valid plug-inattributes which allows migration procedure registering and defines how itshould be executed. Each keyword should be selected in the configuration, nonesymbol should be done for optional fields at least.ToolName: plug-in symbolic name. It is identification name which is used byDesign Converter for processing and log information keeping.Prompt: user friendly plug-in name. It’s used in Design Converter GUI andcould be referenced in related documentation.