Difference between revisions of "Cadence Tools"
(Created page with "== Description == ''From: http://www2.ece.ohio-state.edu/cadence/'': The '''Cadence''' toolset is a complete Integrated Circuit (IC) Electronic Design Automation (EDA) system...") |
(No difference)
|
Revision as of 16:46, 1 July 2016
Description
From: http://www2.ece.ohio-state.edu/cadence/: The Cadence toolset is a complete Integrated Circuit (IC) Electronic Design Automation (EDA) system used to devlop commercial analog, digital, mixed-signal and RF ICs and breadboards.
Version
- Various versions of tools, most current as of 12/15/2015
Authorized Users
CIRCE
account holdersRRA
account holdersSC
account holders
Platforms
CIRCE
clusterRRA
clusterSC
cluster
Modules
Individual tools, grouped by “release stream” and specified by version. Find the release stream and version for the desired tool/functionality on the Release Stream List attached at the bottom of this page:
- apps/cadencetools/2015/assura/41
- apps/cadencetools/2015/confrml/151
- apps/cadencetools/2015/ctos/142
- apps/cadencetools/2015/edi/142
- apps/cadencetools/2015/et/151
- apps/cadencetools/2015/ets/131
- apps/cadencetools/2015/ext/142
- apps/cadencetools/2015/ic/616
- apps/cadencetools/2015/incisiv/142
- apps/cadencetools/2015/innovus/151
- apps/cadencetools/2015/mmsim/141
- apps/cadencetools/2015/mvs/151
- apps/cadencetools/2015/pacific/61
- apps/cadencetools/2015/pvs/151
- apps/cadencetools/2015/rc/142
- apps/cadencetools/2015/sigrity/2015
- apps/cadencetools/2015/spb/166
- apps/cadencetools/2015/ssv/151
- apps/cadencetools/2015/vipp/92
To run any Cadence tools on the cluster, ensure that you use module add
prior to using any Cadence executables. See Modules for more information.
Running on CIRCE - Interactive Job
- Note: All Cadence processing/simulation jobs should be run in an SRUN session, and NOT on the login nodes!
To run Cadence tools using the GUI, the following steps must be taken, in addition to using another command sequence.
1. You must take note of the CIRCE login node that you’re presently logged into. You should see something like:
[user@login0 ~]$
2. You must take note of the current X display that you’re using so that it can be properly exported. To do this, you’ll run the command below and what you should expect to see on the shell:
[user@login0 ~]$ echo $DISPLAY login0.rc.usf.edu:7009.0
3. You now have your display variables necessary to use the Cadence GUI on a compute node within the cluster. You now need to run the command below with example resources:
[user@login0 ~]$ srun --time=02:00:00 --nodes=1 --ntasks-per-node=4 --pty /bin/bash [user@wh-520-4-1 ~]$
4. If all goes well, you should get dropped into an interactive shell on the execution host. You’ll now need to export the display variables taken from steps 1 and 2 above. You’ll run the following command:
[user@wh-520-4-1 ~]$export DISPLAY=login0:7009
5. The last step is to load the Cadence module as described below and then start your specific Cadence toolset.
Documentation
Home Page, User Guides, and Manuals
- Cadence Home Page:
More Job Information
See the following for more detailed job submission information:
Reporting Bugs
Report bugs with Cadence Tools to the IT Help Desk: rc-help@usf.edu