Monte Carlo simulation in Ocean XL for a text-only netlist

Soner,

      I would recommend either 1.)running OCEAN using the bsub command or 2.) opening OCEAN interactively in the same directory you run cadence from (i.e., where your environment variables, etc., are set, or where your .cdsenv, .cdsinit, etc.. files are). This would look like:

1. bsub -q [queue where you want the sim to run] "ocean <[path to ocean script from present dir/oceanscriptname.ocn]> [path to ocean script frompresent dir/oceanoutputlogfilename.log] "

for example, this may look like:

bsub -q medium "ocean <ocean/amp.ocn> ocean/ampoutput.log"

since I have my scripts in a folder called ocean and I am running it from the folder I would normally run cadence in. You don't have to send it to a queue if you don't want to or know what this means. If you just want to submit it locally, you can omit -q [queue name] above.

2. Open ocean in the same directory as you would cadence by typing ocean at the command line. Then when ocean loads, type:

load("[path to ocean script from present directory/oceansctiptname.ocn")

and the sim should go, You may have been having trouble because your .cdsenv files and things like that couldn't be found. For example, since my scripts are located at /home/john/cadence/ocean and my cadence directory is cadence, I can simply type

load("ocean/amp.ocn")

since cadence is running from the /home/john/cadence folder.

If you are still having trouble, start from the ground up by trying to run a test script in your cadence CIW. I've found that this helps. At least try having ocean put its output into a log file.

Best,

John

Soner,

      I would recommend either 1.)running OCEAN using the bsub command or 2.) opening OCEAN interactively in the same directory you run cadence from (i.e., where your environment variables, etc., are set, or where your .cdsenv, .cdsinit, etc.. files are). This would look like:

1. bsub -q [queue where you want the sim to run] "ocean <[path to ocean script from present dir/oceanscriptname.ocn]> [path to ocean script frompresent dir/oceanoutputlogfilename.log] "

for example, this may look like:

bsub -q medium "ocean <ocean/amp.ocn> ocean/ampoutput.log"

since I have my scripts in a folder called ocean and I am running it from the folder I would normally run cadence in. You don't have to send it to a queue if you don't want to or know what this means. If you just want to submit it locally, you can omit -q [queue name] above.

2. Open ocean in the same directory as you would cadence by typing ocean at the command line. Then when ocean loads, type:

load("[path to ocean script from present directory/oceansctiptname.ocn")

and the sim should go, You may have been having trouble because your .cdsenv files and things like that couldn't be found. For example, since my scripts are located at /home/john/cadence/ocean and my cadence directory is cadence, I can simply type

load("ocean/amp.ocn")

since cadence is running from the /home/john/cadence folder.

If you are still having trouble, start from the ground up by trying to run a test script in your cadence CIW. I've found that this helps. At least try having ocean put its output into a log file.

Best,

John