Difference between revisions of "Cadence Tools"

m (Botto moved page Cadence to Cadence Tools)
(5 intermediate revisions by 2 users not shown)
Line 5: Line 5:
=== Version ===
=== Version ===


*Various versions of tools, most current as of 12/15/2015
*Various versions of tools, most current as of 09/15/2017


{{AuthorizedUsers}}
{{AuthorizedUsers}}
Line 12: Line 12:
=== Modules ===
=== 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:
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, expandable below:
 
<div class="tocccolours mw-collapsible mw-collapsed">
 
==== Available Cadence Products ====
<div class="mw-collapsible-content">
* apps/cadencetools/2017/assura/415
* apps/cadencetools/2017/confrml/1620
* apps/cadencetools/2017/confrml/1710
* apps/cadencetools/2017/ctos/1420
* apps/cadencetools/2017/edi/1428
* apps/cadencetools/2017/et/1514
* apps/cadencetools/2017/ets/1319
* apps/cadencetools/2017/ext/1527
* apps/cadencetools/2017/ext/1611
* apps/cadencetools/2017/ext/1710
* apps/cadencetools/2017/ext/1711
* apps/cadencetools/2017/ic/616
* apps/cadencetools/2017/incisiv/1410
* apps/cadencetools/2017/incisive/1420
* apps/cadencetools/2017/incisive/1510
* apps/cadencetools/2017/innovus/1623
* apps/cadencetools/2017/innovus/1710
* apps/cadencetools/2017/mmsim/1510
* apps/cadencetools/2017/mvs/1710
* apps/cadencetools/2017/pvs/1517
* apps/cadencetools/2017/pvs/1524
* apps/cadencetools/2017/rc/1428
* apps/cadencetools/2017/sig/1600
* apps/cadencetools/2017/spbs/1721
* apps/cadencetools/2017/ssv/1623
* apps/cadencetools/2017/ssv/1710
* apps/cadencetools/2017/stratus/1521
* apps/cadencetools/2017/stratus/1623
* apps/cadencetools/2017/stratus/1711
</div></div>


* 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 <code>module add</code> prior to using any Cadence executables. See [[Modules]] for more information.
To run any Cadence tools on the cluster, ensure that you use <code>module add</code> prior to using any Cadence executables. See [[Modules]] for more information.


== Running on CIRCE - Interactive Job ==
{{AppRunningOnAll}}


*'''Note:''' All Cadence processing/simulation jobs should be run in an SRUN session, and NOT on the login nodes!
*'''Note:''' All Cadence processing/simulation jobs should be run in an SRUN session, and NOT on the login nodes!
Line 42: Line 58:
To run Cadence tools using the GUI, the following steps must be taken, in addition to using another command sequence.
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:<pre style="white-space:pre-wrap; width:25%; border:1px solid lightgrey; background:#000000; color:white;">[user@login0 ~]$</pre>
1. You must take note of the CIRCE/SC login node that you’re presently logged into. You should see something like:<pre style="white-space:pre-wrap; width:25%; border:1px solid lightgrey; background:#000000; color:white;">[user@login0 ~]$</pre>


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:<pre style="white-space:pre-wrap; width:35%; border:1px solid lightgrey; background:#000000; color:white;">[user@login0 ~]$ echo $DISPLAY
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:<pre style="white-space:pre-wrap; width:35%; border:1px solid lightgrey; background:#000000; color:white;">[user@login0 ~]$ echo $DISPLAY

Revision as of 20:18, 16 April 2018

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 09/15/2017

Authorized Users

  • CIRCE account holders
  • RRA account holders
  • SC account holders

Platforms

  • CIRCE cluster
  • RRA cluster
  • SC 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, expandable below:

Available Cadence Products

  • apps/cadencetools/2017/assura/415
  • apps/cadencetools/2017/confrml/1620
  • apps/cadencetools/2017/confrml/1710
  • apps/cadencetools/2017/ctos/1420
  • apps/cadencetools/2017/edi/1428
  • apps/cadencetools/2017/et/1514
  • apps/cadencetools/2017/ets/1319
  • apps/cadencetools/2017/ext/1527
  • apps/cadencetools/2017/ext/1611
  • apps/cadencetools/2017/ext/1710
  • apps/cadencetools/2017/ext/1711
  • apps/cadencetools/2017/ic/616
  • apps/cadencetools/2017/incisiv/1410
  • apps/cadencetools/2017/incisive/1420
  • apps/cadencetools/2017/incisive/1510
  • apps/cadencetools/2017/innovus/1623
  • apps/cadencetools/2017/innovus/1710
  • apps/cadencetools/2017/mmsim/1510
  • apps/cadencetools/2017/mvs/1710
  • apps/cadencetools/2017/pvs/1517
  • apps/cadencetools/2017/pvs/1524
  • apps/cadencetools/2017/rc/1428
  • apps/cadencetools/2017/sig/1600
  • apps/cadencetools/2017/spbs/1721
  • apps/cadencetools/2017/ssv/1623
  • apps/cadencetools/2017/ssv/1710
  • apps/cadencetools/2017/stratus/1521
  • apps/cadencetools/2017/stratus/1623
  • apps/cadencetools/2017/stratus/1711


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 Cadence Tools on CIRCE/SC

The Cadence Tools user guide is essential to understanding the application and making the most of it. The guide and this page should help you to get started with your simulations. Please refer to the Documentation section for a link to the guide.

  • Note on CIRCE: Make sure to run your jobs from your $WORK directory!
  • Note: Scripts are provided as examples only. Your SLURM executables, tools, and options may vary from the example below. For help on submitting jobs to the queue, see our SLURM User’s Guide.
  • 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/SC 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

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