Tips & Tricks
Set # of sig figs on schematic annotation
Sometimes the number of significant figures on schematic annotations (node voltages, for example) is very high and it becomes difficult to read. To fix this, type the following into the icfb window:
envSetVal("auCore.misc" "labelDigits" 'int 5)
Change the number 5 to your desired number of sig figs. To make this change permanent, add the line to your ~/.cdsenv file.
Disable "What's New" Window
Make Nautilus (file manager) behave like a browser
Nautilus is the default file manager on the lab computers. You have likely noticed that, with the default settings, it spawns a new windows each time you open a folder. If you find this annoying, you can change its behavior with the following steps:
- Open the preferences dialogue (Edit->Preferences)
- Click on the behavior tab
- Tick the always open in browser windows option
Save operating point information over a DC sweep
You may notice that DC operating point information (gm, gds, etc.) does not get saved over a DC sweep. One way to work around this is to replicate the sweep using the parametric sweep tool. In some cases, however, this may constrain your simulation setup. If you simply want the op information to be saved for every point in a sweep, follow these directions:
- Make a new text file (saveop.scs, for example) in a directory to which you have read-write access.
- Add the following line to the file, replacing
N0with the name of the device whos operating point you wish to save:
- Save the file. Return to your ADE window, navigate to Setup->Model Libraries; now the file you just made to the list.
- Run your simulation and find the saved data in the Results Browser (under the Tools menu in the ADE). You can also access the data with equations (i.e.
getData("M0:vdsat" ?result 'dc)).
- You can, of course, have multiple lines in the file for multiple devices. For large simulations, consider saving disk space by modifying the file to save only the parameters of interest (i.e,
N0:gm). More information about the save command can be found in the spectre documentation or by running
spectre -h saveat the terminal.