Stats

  • Locked Locked
  • Replies 3
  • Subscribers 143
  • Views 2082
  • 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

Error plotting finesim psf results with OCEAN/artil

trdastidar

Hi,

I have a set of PSF results generated with the finesim simulator (run from ADE through OASIS). Now, I need to run some calculator functions on them.

When I open the results directory in OCEAN or artil, I get this message:

 WARNING (OCN-6152): Simulator finesim is not registered.
         Calculator data access functions (e.g., VT, IT, etc.) will not work.
         However, ocean data access functions (e.g., v, i, getData, etc.) will work.

The function that I try to evaluate is:

Max_Current = ymax(IS("some_signal"))

However, it doesn't work.

When I replace it with

Max_Current = ymax(i("some_signal" ?result srcSweep))

it works.

Any idea how to make it work in the original form?

Further, the signal names in the results ( as visible with the results() ) command use '.' as the hierarchy separator. However, in the OCEAN script, '/' is used as a hierarchy separator.

Is there a way I can get the OCEAN script to recognize the signal names without having to change the separator to '.'?

Regards,

Tathagato

Parents

  • Tathagato,

    Using the "/" hierarchy separator means that the name is a "schematic" name (i.e. the name it is in the original schematics). Presuming that finesim uses "." as its hierarchy separator, using a name which doesn't start with "/" means that it is a "simulator" (or netlist) name. This is the name that is actually stored in the psf result database - the "/" names work by mapping from one to the other using the mapping data stored in the netlist directory.

    However, for that to work, it needs access to the simulator integration. If using "ocean" (at least in IC5141, not sure which version you're using since you didn't say), or "artil", it probably doesn't have the integration loaded, hence the warning message. This is presumably being loaded in your .cdsinit somewhere (I don't know how it's done for finesim since it's a Synopsys product not a Cadence product), and the .cdsinit is not loaded when using "ocean" or "artil".

    You may be able to workaround that by loading the simulator integration from a .oceanrc file or from .artilinit (these are the initialization files for these two executables).

    Regards,

    Andrew.

Reply

  • Tathagato,

    Using the "/" hierarchy separator means that the name is a "schematic" name (i.e. the name it is in the original schematics). Presuming that finesim uses "." as its hierarchy separator, using a name which doesn't start with "/" means that it is a "simulator" (or netlist) name. This is the name that is actually stored in the psf result database - the "/" names work by mapping from one to the other using the mapping data stored in the netlist directory.

    However, for that to work, it needs access to the simulator integration. If using "ocean" (at least in IC5141, not sure which version you're using since you didn't say), or "artil", it probably doesn't have the integration loaded, hence the warning message. This is presumably being loaded in your .cdsinit somewhere (I don't know how it's done for finesim since it's a Synopsys product not a Cadence product), and the .cdsinit is not loaded when using "ocean" or "artil".

    You may be able to workaround that by loading the simulator integration from a .oceanrc file or from .artilinit (these are the initialization files for these two executables).

    Regards,

    Andrew.

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.