main menu | module menu | << previous section | next section >>

Sentaurus Process
1. Getting Started

1.1 Working With This Module
1.2 File Types
1.3 Starting Sentaurus Process

Objectives

To provide an introduction to the features of Sentaurus Process.
To identify the file types used by Sentaurus Process.
To demonstrate how to run Sentaurus Process.

1.1 Working With This Module

Sentaurus Process is a highly flexible multidimensional process modeling environment. With its modern software architecture, it constitutes a solid base for process simulation. Calibrated to a wide range of the latest experimental data using proven calibration methodology, Sentaurus Process offers unique predictive capabilities for modern silicon and nonsilicon technologies.

In this module, you are guided through a series of examples of increasing complexity. The most widely used Sentaurus Process commands are introduced in the context of these examples.

The module discusses only arguments and options that are used in the given examples. For details about commands, see the Sentaurus™ Process User Guide.

A listing of the command file of Sentaurus Process is given at the end of each section in the form of an HTML link. You are encouraged to create a local copy of the command file from the browser (choosing File > Save As) and to run it. Some examples are given as Sentaurus Workbench package files. After creating a local copy, the files can be opened with Sentaurus Workbench.

1.2 File Types

The main file types used in Sentaurus Process are:

Command file (*.cmd)
This is the main input file for Sentaurus Process. It contains all the process steps and can be edited. This file is referred to as the command file or input file.
Log file (*.log and *.out)
Sentaurus Process generates a .log file when it is run from the command line and an .out file when it is run from Sentaurus Workbench. Both files contain information about each processing step, and the models and values of physical parameters used in it. The amount of information written to the log file is controlled by the info argument, which is available in nearly all commands. The global default information level (0) can be changed with pdbSet InfoDefault <n>. Allowed values of InfoDefault are 0, 1, and 2 with higher values indicating more verbose output. Any value higher than 2 will be interpreted as 2.
TDR boundary file (*_bnd.tdr)
This file stores the boundaries of the structure without the bulk mesh or fields. It can be used as the structure file for the Sentaurus Mesh meshing engine and can be loaded into Sentaurus Visual for viewing. The name of a TDR boundary file can be specified with the tdr argument of the init command of Sentaurus Interconnect, and then the loaded boundary will be meshed.
To open a TDR file, open a terminal window and launch the TDR file viewer with the command:
svisual <file_name>.tdr
TDR grid and doping file (*_fps.tdr)
TDR files can be used to split and restart a simulation. Such restart files are saved using the struct tdr=<c> command because restarting requires interface data, parameter and command settings, mesh ordering information, as well as bulk grid and data. If either !pdb or !interfaces is specified in the struct command, the TDR file will not be suitable for restarting. The TDR file can be loaded into Sentaurus Process using the init command, but the results of the subsequent simulation steps might differ in a simulation with splits and a restart, compared to a simulation of the entire flow in one attempt.
XGRAPH file (*.plx)
This file saves the 1D distributions of the doping concentration or other fields in a specified cross section. This file can be viewed by loading into Sentaurus Visual.

1.3 Starting Sentaurus Process

To start Sentaurus Process in interactive mode, type the following on the command line:

> sprocess

Sentaurus Process displays version and host information, followed by the Sentaurus Process command prompt.


Sentaurus Process

Version W-2024.09 for linux64 - Jul 22, 2024 16:20:09
Changelist number: 9089333, Compile host: us01odc-sc5-1-pbm363

Copyright (c) 1993 - 2024 Synopsys, Inc.
This software and the associated documentation are proprietary to Synopsys,
Inc. This software may only be used in accordance with the terms and conditions
of a written license agreement with Synopsys, Inc. All other use, reproduction,
or distribution of this software is strictly prohibited.  Licensed Products
communicate with Synopsys servers for the purpose of providing software
updates, detecting software piracy and verifying that customers are using
Licensed Products in conformity with the applicable License Key for such
Licensed Products. Synopsys will use information gathered in connection with
this process to deliver software updates and pursue software pirates and
infringers.

Inclusivity & Diversity - Visit SolvNetPlus to read the "Synopsys Statement on
Inclusivity and Diversity" (Refer to article 000036315 at
https://solvnetplus.synopsys.com)

Started at: Tue Jul 23 08:35:57 2024 (MST)
User name: jasonam
Host name: us01milan-4026-005
PID: 1027153
Architecture: x86_64
Operating system: Linux rel. 4.18.0-425.3.1.el8.x86_64 ver. #1 SMP Tue Nov 8 \
  14:08:25 EST 2022

------------------------------------------------------------------------------
Checking syntax of n1_fps.cmd:
...

Commands can be now entered sequentially at the prompt.

To run Sentaurus Process in batch mode, type:

> sprocess input_fps.cmd

The command file is checked for correct syntax, and then the commands are executed in sequence until the simulation is stopped by the command exit or the end of the file is reached. Syntax-checking can be switched off with the command-line option -n: