Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 7155
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setup Script to Run Spectre from Command Line

sgcad

Hi

In the environment I'm currently working, I'm using a setup script as below to start the graphical version of Virtuoso.

module load ic/618/06.18.290
module load assura/41/618/04.16.111
module load spectre/231/23.10.063
module load mmsim/151/15.10.627
module load pvs/191/19.15.000

setenv IC_INST_DIR  /apps/IC618/FCS
setenv MY_TECH     /process/hosted/MYTECH/MYTECH_618_rev0.12.0
setenv PROJECT     /projects/mypath
setenv CDS_Netlisting_Mode Analog

virtuoso &

Now I'd like to create a similar script that allows me to run Spectre from a command line (xterm), without any graphical features whatsoever. The intention behind this is that I can run long simulations completely independent from the graphical Virtuoso. So if Virtuoso crashes or I have to restart it, the long simulations are not affected.

How do I need to change the above script to achieve that? I presume I can remove the lines for Assura and PVS, as for just running Spectre those modules should not be needed. But then I don't know what to do next; just removing the last line ("viruoso &") does not give access to Spectre in the command line, neither does using "virtuoso -nograph &".

Any input is appreciated, thanks very much.

  • The script is simply setting up the tools (using "module") and launching Virtuoso as the final step. But as you see; Spectre is included in this setup. So will be available from the command line. You can choose to remove access to the other tools if you wish but there is no need. In fact if you remove the launching of Virtuoso then you have access to the installed modules and can launch whichever you require. This could be 'spectre' (with optons), 'virtuoso', 'assura' etc.

  • in reply to RobMan

    Thanks very much for your reply. The behavior you describe is exactly what I'd have expected, but not what I've seen. After running the script without "viruoso &", none of the tools were available in the terminal.

    But your post triggered the right thought--it was an issue related to a nested script structure. The script I've posted above was actually launched from another script, which basically resulted in the scripts closing the environment immediately after the modules were loaded and the environment variables set. Removing the actually unnecessary nesting of scripts solved the issue.

    Thanks again!

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.