8.3.1 Input Files needed by VLSICAP



next up previous contents
Next: 8.3.2 The PIF Geometry Up: 8.3 Data Level Integration Previous: 8.3 Data Level Integration

8.3.1 Input Files needed by VLSICAP

The original program system VLSICAP needs three kinds of data on input:

Since PIF can hold the complete physical problem description including the geometry, materials, and doping profiles, both the input data and doping data files are replaced with a single input PIF binary file. The input deck, however, has to be kept for the specification of non-physical information, like the master file name <MFN> and which quantities should be written to the PBF once the run is completed. The following sections describe how the various required inputs for MESHCP are stored on PIF.



Martin Stiftinger
Tue Nov 29 19:41:50 MET 1994