Stats

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

Command openResults problem

loon

Hi all,

       After I run a simulation, I can use command openResults to open it

simulation_directory = "/projects/......./schematic/psf"
openResults( simulation_directory)

selectResult( 'tran )
outputs()

      I get the following results

     ("/D<0>" "/D<1>" "/D<2>" "/D<3>" "/D<4>")

      And I can process the data.

      The problem is that I copy the whole simulation data files to a new directory, and load the simulation data

from new directory, After entering the following command, get the following results.

     ("D\\<0\\>" "D\\<1\\>" "D\\<2\\>" "D\\<3\\>" "D\\<4\\>")

     I can not use getData command to access the data. 

     I just wonder why this happens and how to solve this problem. Thanks!

 

  • This happens because there is a reference in the runObjFile in the psf directory to the netlist directory (as a relative path). In the netlist directory, there are directories containing name mapping information (eg amap) which tell it how names are mapped from what they are called in the schematic to what they are called in the netlist (the simulator has different naming rules than Virtuoso).

    When you give a name starting with "/" you're using the schematic name. If you've moved the results and not taken the netlist dir with it, you can't use the schematic names any more. You can still use getData(), but you must use netlist names instead (which is what the outputs() function is telling you - it's showing you the names which are really in the result database without the mapping applied). You can see this with something like outputs(?map nil) (I forget if that's the actual keyword - you can check with arglist('outputs) .

    Regards,

    Andrew

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.