Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13137
  • 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

Custom instance name for dcOp

markbeck

Greetings all,

I'm running on IC_6.15_ISR7 and I'm looking for a method to change the name of the spectre simulation that the netlist chooses.

For example:

If I have an ocean script, and I have the following expression:

analysis('dc ?saveOppoint t)

It will create the following bit of text in the input.scs file:

dcOp dc write="spectre.dc" maxiters=150 maxsteps=10000 annotate=status
dcOpInfo info what=oppoint where=rawfile

Now, if I wanted to include an analysis with an includeFile() statement that had a dcOp instance in it, it would cause the simulation to fail since there are two instances with the same name.

One solution is "Don't do that". However, I am forced to create the dc analysis due to Ocean-XL not allowing a test without an analysis statement.  see: www.cadence.com/.../20454.aspx

What I'm looking for is a method in either ocean/skill that allows me to alter the instantiated name of the analysis before netlist. e.g.:

 dcOp_foo dc write="spectre.dc" maxiters=150 maxsteps=10000 annotate=status
dcOpInfo_foo info what=oppoint where=rawfile

I've looked through the various asi functions and not found anything which seems to solve this issue.

Thanks,
Mark

  • Mark,

    Ancient post that didn't get answered at the time (not sure why), but rather than renaming the analysis (which you can't currently, at least not reliably), you can turn off ADE XL/OCEAN XL's check for there having to be an analysis defined:

    envSetVal( "adexl.simulation" "ignoreAnalysisCheck" 'boolean t)

    Regards,

    Andrew.

  • Hi Andrew,

    Thanks for the reply, if I remember correctly I submitted a ER and it got implemented as you described. I've been using that environmental variable for a while now, but forgot to go back and comment on the post (to help others).

    Thanks for the reply,
    Mark

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.