Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 12873
  • 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

Sensitivity simulation from ocean file on extracted view

raduionescu

Hello,

I am not sure this is the right forum for this, but I am running a sensitivity simulation from an ocean script. My issue I have a hierarchy in which one of the blocks is a parasitic extracted view, and I have issue if I try to use a parasitic output net.

I am building a line like

analysis('sens ?anaName "sens"  ?analyses_list list("dc")    ?instances list( ... here I add what I need )     ?net list("/VI"        "/VQ"    "/I1/I_extract/22:Vref_1V5"    )  )

I get sensitivity results in the dcOpSense psf for VI and VQ but not for the parasitic net and in the log I get the warnings

\o     WARNING (SPECTRE-8290): `I_DUT.I_S3732A21.22\': Not a signal, device
\o         instance, or a model.
\o     WARNING (SPECTRE-8293): Ignoring invalid output item
\o         `I_DUT.I_S3732A21.22\:Vref_1V5' in sensitivity request.

I assume I need to somewhow escape the : character but I am not sure how or where to look in the documentation. Does anyone have an idea? Thank you.

Regards,

Radu

Parents

  • Hi Radu,

    This would be best handled through support.cadence.com because there's guesswork otherwise, but I'd try either "/I1/I_extract/22\\:Vref_1V5" or "I1.I_extract.22\\:Vref_1V5".

    Note I've not tried a similar example, so this is a bit of a guess.

    Andrew.

Reply

  • Hi Radu,

    This would be best handled through support.cadence.com because there's guesswork otherwise, but I'd try either "/I1/I_extract/22\\:Vref_1V5" or "I1.I_extract.22\\:Vref_1V5".

    Note I've not tried a similar example, so this is a bit of a guess.

    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.