Stats

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

. dot vs / slash when saving signals in Ocean

zaratustra

I'm exporting all the net voltages (for a specific time) from a circuit and I noted that if I perform the simulation with APS++ and XPS the signals are saved with the slash notation. Example:

option( ?categ 'turboOpts
    'apsplus  t
    'uniMode  "XPS MS"
)

In this case the signals are saved as:

/NET<0>

/I0/netX<0>

If I simulate with spectre only the signals are saved as:

NET\<0\>

I0.netX\<0\>

Note the \ to scape the <> too.

Is there an option to set one style or the other ?

  • Andrew Beckett

    Hmm, this doesn't sound correct to me. Spectre actually always saves signals with the dot hierarchy separator, because that's Spectre's namespace - it has to match the names in the netlist. However, in the results browser, names are normally reverse mapped into "schematic" names (i.e. names that begin with slash, and use slash as the hierarchy separator). So effectively requests to save signals or probe signals start from a hierarchical schematic names (with slashes) and end up translated to spectre's namespace, and then when you look at the named results (e.g. with the outputs() function in OCEAN or the results browser, they're translated back into schematic names).

    In OCEAN you can normally do:

    selectResult('tran)
    outputs()

    or 

    outputs(?map nil)

    (the latter will show the unmapped names).

    I see no reason why it being APS/XPS or spectre would make a difference to this mapping.

    Andrew.

  • zaratustra
    in reply to Andrew Beckett

    Thank you, Andrew. I will give it a try with outputs(?map nil).

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.