Processing cadence result data from psf folder

 Dear RF Stuff,

> Is there any way, OCEAN can read the raw data in the psf folder and write into a .txt file 

 Yes. Ocean can open a set of results in a psf directory and write whatever results you want into a text file. Please refer to the ocean reference manual for the speciifc syntax. The manual may be found be doing a search for "ocean reference manual" on Cadence online support. 

Shawn

 I used the same commands used in my ocean scripts as below:-

 openResults("psf")

selectResult( 'tran )
plot(getData("/V2_OUTP_Q/PLUS"))

But it didn't work. But when I run the simulation, using OCEAN script ( i.e. load(".../../xxxx.ocn) ) it plots .

I am not able to understand why  plot(getData("/V2_OUTP_Q/PLUS")) command is NOT working in ocean terminal 

 Dear RF Stuff,

> I am not able to understand why  plot(getData("/V2_OUTP_Q/PLUS")) command is NOT working in ocean terminal  

Add the command outputs() after you have entered openResults("psf") and selectResult("tran"). This command lists the available outputs. There may be a syntax issue with the node name. A second possibility is the terminal window you are using is not a graphics compatible window. You might aso try ocnPrint().

Shawn

 Hi Swann,

When I typed  outputs, it shows:-

 ("V2_OUTP_Q:p")

But NOT as   ("/V2_OUTP_Q/PLUS").

I am NOT able to understand why it is NOT showing  ("/V2_OUTP_Q/PLUS") as when I run with ocean script.

 Dear RF Stuff,

 > I am NOT able to understand why it is NOT showing  ("/V2_OUTP_Q/PLUS") as when I run with ocean script.

Please use the node name shown when you typed outputs. There is an amaps dreictory in the /netlist directory that maps node names and when you run ADE, it is invoked so you can plot the signal name  /V2_OUTP_Q/PLUS. When you run standalone ocean, if it does not know the location of the netlist directory, it may not have access to that file. Hence, the node name to access the signal is different than the hierarchical nde name. To avoid this issue, the netlist file should be on the same directory level as the /psf directory. A possible workaround provided by Cadence is to create a soft link to the netlist directory that appears on the same level as your /psf directory. This can be done with the ocean system() command. An example is:

system("ln -s <path1>/netlist <path2>/netlist")

where <path1> is the location of your /netlist directory and <path2> is the location of your /psf directory. This will place a symbolic link of the /netlist directory adjacent your existing /psf directory.

I hope this helps.

Shawn

 Dear Shwan,

As I mentioned, in the previous posts, that I am NOT running stand alone OCEAN in the CLUSTERS ( SERVER).

I am running as  :- spectre input.scs in the terminal.

Then I am using ocean script to plot the saved node voltages/currents generated during simulation in the psf foder.

But the input.scs always gets generated in the psf folder where netlist also exists.

In the input.scs file,   ("V2_OUTP_Q:p") gets created instead of /V2_OUTP_Q/PLUS for saving current going into the source  V2_OUTP_Q.

 Is there any way, to ensure that in input.scs,  /V2_OUTP_Q/PLUS is used for saving current going into the source  V2_OUTP_Q ?

Kind Regards,

This is a question about namespaces. In OCEAN data access functions (e.g. v(), i(), getData(), pv() etc), the net name/terminal name can be specified either as a "schematic" name or a "netlist" name. If the name begins with a "/", then it refers to a "schematic" name - i.e. the hierarchical name of something within the Virtuoso database. Otherwise it refers to a name that is in the netlist - in which case it has to refer to spectre's naming rules (i.e. dot "." as the hierarchy separator, and ":" for terminal access or operating point parameter access).

When the schematic is netlisted, you end up with directories called map and amap in the netlist directory which contain the information about how schematic names are mapped to netlist names (in particular this is important if reserved words or illegal characters are used). The names you ask to save get translated via this mapping informaton into corresponding netlist names - so if you ask to save /V2_OUTP_Q/PLUS in OCEAN, it will correspond to a "save V2_OUTP_Q:p" in the netlist. Similarly post-simulation, it uses this mapping information to allow you to access signals using the schematic names (the result database itself only ever contains netlist names).

In order to do that mapping however, OCEAN needs to know where the amap directory is. The simplest way of achieving that is to ensure that you have:

someDirectory
  --> netlist
          --> amap dir
          --> map dir
          --> input.scs
  --> psf

You run the simulation from inside the netlist dir, and then use "spectre -raw ../psf input.scs"

The expectation from the OCEAN access functions is that you have netlist and psf alongside each other. There are ways around that if OCEAN runs the simulation because it can create a runObjFile in the psf dir to tell it where the netlist dir is, but if running spectre standalone that won't be created and it will then fall back to the default assumption of the structure above.

Regards,

Andrew.