Differenze
Queste sono le differenze tra la revisione selezionata e la versione attuale della pagina.
| Entrambe le parti precedenti la revisione Revisione precedente Prossima revisione | Revisione precedente | ||
|
vlsi:personalpages:cenna:tcad [16/10/2015 18:00] cenna |
vlsi:personalpages:cenna:tcad [13/11/2015 09:42] (versione attuale) cenna |
||
|---|---|---|---|
| Linea 1: | Linea 1: | ||
| - | Synopsys Sentaurus TCAD\\ | + | [ __[[vlsi:personalpages:cenna:TCAD:Sprocess|Sprocess]]__ ] |
| + | [ __[[vlsi:personalpages:cenna:TCAD:StructureEditor|StructureEditor]]__ ] | ||
| + | [ __[[vlsi:personalpages:cenna:TCAD:Sdevice|Sdevice]]__ ] | ||
| + | [ __[[vlsi:personalpages:cenna:TCAD:Other TCADs|Other TCADs]]__ ] | ||
| + | |||
| + | |||
| + | ==== Synopsys Sentaurus TCAD ==== | ||
| connect to the virtual machine\\ | connect to the virtual machine\\ | ||
| Linea 7: | Linea 14: | ||
| </code> | </code> | ||
| The first time you start Sentaurus, you have to set the STDB environment variable.\\ | The first time you start Sentaurus, you have to set the STDB environment variable.\\ | ||
| - | 1. create a folder called DB inside your space on /data disk | + | |
| + | 1. CAD admin usually creates a DB folder for each user inside /data. If not, create a folder called DB inside your space on /data disk\\ | ||
| + | **DON'T** put your DB folder inside /home, or the simulations will saturate the disk in a short time and TCAD will crash. | ||
| <code> | <code> | ||
| sudo mkdir /data/users/<your_name>/DB | sudo mkdir /data/users/<your_name>/DB | ||
| </code> | </code> | ||
| - | 2. edit your .cshrc file by typing | + | 2. edit your .cshrc file by typing (NOTE: by default, administrator sets cshell as default shell for users) |
| <code> | <code> | ||
| sentenv STDB = /data/users/<your_name>/DB | sentenv STDB = /data/users/<your_name>/DB | ||
| Linea 26: | Linea 36: | ||
| !!!selinux disabled to let xauth work properly (configuration file edited) | !!!selinux disabled to let xauth work properly (configuration file edited) | ||
| + | **Issues**\\ | ||
| + | - Simulation with correct syntax fails (red node color): | ||
| + | * saturated disk space | ||
| + | * you changed the command file between one node and the other | ||
| + | |||
| + | |||
| + | ------ | ||
| + | **Request an account/report a problem** | ||
| + | |||
| + | mail me [[cenna@NOSPAMto.infn.it]] | ||
| + | |||
| + | for hardware problems with the server, contact Centro di Calcolo | ||
| + | |||
| + | ------ | ||
| + | **Running simulations/ CPU usage** | ||
| + | |||
| + | When you run a simulation, you can specify the number of threads/cores which will be used. Our machine has 16 cores: usually, the programs accepts a number of threads <16.\\ | ||
| + | Please don't use the "priority run" option, this will not speed up that much the simulation but will consume a lot of computing resources. | ||
| + | ------ | ||
| + | **Where to learn Sentaurus** | ||
| + | |||
| + | Europractice courses: [[http://www.europractice.stfc.ac.uk/training/]]\\ | ||
| + | Basic tutorial by Synopsys: click on the "T" icon on Sentaurus Workbench | ||
| Linea 31: | Linea 64: | ||
| - | ===== Example: gaussian doping profile definition ===== | ||
| - | 1. create a window for your doping concentration, here I used the "Line" option (other possibilities are rectangle, polygon..)\\ | ||
| - | syntax "window name" "window type" (window start coordinate) (window end coordinate) | ||
| - | <code> | ||
| - | (sdedr:define-refeval-window "Ndeep_wind1" "Line" (position xndeep0 @L@ 0.0) (position xndeep1 @L@ 0.0) )</code> | ||
| - | 2. define the doping profile placement and the direction | ||
| - | <code> | ||
| - | (sdedr:define-analytical-profile-placement "AnalyticalProfilePlacement_Ndeep1" "AnalyticalProfileDefinition_Ndeep1" "Ndeep_wind1" "Negative" "NoReplace" "Eval")</code> | ||
| - | 3. set the type of dopant, peak position and value, value at junction (the doping concentration of the bulk) and junction depth (where your doping joins the bulk). NOTE!!!: peak position is relative to your profile, it is NOT the coordinate of peak in the whole device. | ||
| - | <code> | ||
| - | (sdedr:define-gaussian-profile "AnalyticalProfileDefinition_Ndeep1" "ArsenicActiveConcentration" "PeakPos" 1 "PeakVal" 5e+17 "ValueAtDepth" 2.5e+12 "Depth" 2 "Gauss" "Factor" 0.8) | ||
| - | </code> | ||