Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 19974
  • 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

Processing cadence result data from psf folder

RFStuff

 Dear All,

 There is a Spectre & MATLAB interface for plotting psf data. But this somehow not working in my case with latest MATALB2014.

So I use Ocean Script for saving simulation data in text file in two column format. This then being used some other plotting tools like MATLAB. But when we run Spectre in our central server, we can't run OCEAN but only spectre ( i.e. spectre input.scs).

The raw data files are created in a folder called psf. I can copy this folder to my local macine.

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

Kind Regards,

Parents

  •  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

     

Reply

  •  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

     

Children
No Data

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.