Sentaurus

From FarmShare

(Difference between revisions)
Jump to: navigation, search
(Created page with "This page documents the instructions for getting sentaurus software to run. You need several environment variables: STDB, STROOT, License servers set. Create a directory "STDB"...")
Line 1: Line 1:
This page documents the instructions for getting sentaurus software to run.
This page documents the instructions for getting sentaurus software to run.
-
You need several environment variables: STDB, STROOT, License servers set.
+
You need several environment variables to be set: STDB, STROOT, License servers set.
Create a directory "STDB" (this can be of another name as long as it
Create a directory "STDB" (this can be of another name as long as it
Line 9: Line 9:
stored. And STROOT is where the software is installed.
stored. And STROOT is where the software is installed.
-
Then run 'module load sentaurus'.  That will configure your environment correctly.  You can try 'module show sentaurus' to see what it's doing.
+
Then run:
 +
  module load sentaurus
 +
That will configure your environment correctly.  You can try 'module show sentaurus' to see what it's doing. We set your STDB directory to $HOME/work/Sentaurus
Alternatively, you can set those variables yourself, here is csh example:
Alternatively, you can set those variables yourself, here is csh example:

Revision as of 13:40, 9 October 2014

This page documents the instructions for getting sentaurus software to run.

You need several environment variables to be set: STDB, STROOT, License servers set.

Create a directory "STDB" (this can be of another name as long as it matches what is in the environment variable STDB)

STDB is the local storage where the simulation scripts and results are stored. And STROOT is where the software is installed.

Then run:

 module load sentaurus

That will configure your environment correctly. You can try 'module show sentaurus' to see what it's doing. We set your STDB directory to $HOME/work/Sentaurus

Alternatively, you can set those variables yourself, here is csh example:

 setenv STDB /afs/ir.stanford.edu/users/path/to/your/homedir/STDB  
 setenv STROOT /afs/ir/class/ee/synopsys/sentaurus/I-2013.12-SP2/
 setenv LM_LICENSE_FILE 27000@cadlic0.stanford.edu
 setenv SNPSLMD_LICENSE_FILE 27000@cadlic0.stanford.edu
 set path=(/afs/ir/class/ee/synopsys/sentaurus/I-2013.12-SP2/bin $path)

The sentaurus workbench can be started using the "swb" command.

You should see a set of examples in "GettingStarted" tab on the left hand side of the menu. I recommend using "SmallMOS_2D3D" under "sprocess" examples since it contains all the components that needs to be tested.

A right click menu can be used to copy this project and similarly pasted into your working STDB directory.

run the project by clicking on the running man icon on the top interface (towards upper right area of the window.)

Once the software finishes running the nodes that ran should turn yellow. except for inspect (another graphical interface tool that fails) which will turn red (for failed run).

check svisual running by clicking on the eye icon while a node is selected (the one that is now yellow) to call up svisual. Currently this fails.

Personal tools
Toolbox
LANGUAGES