Stats

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

soft_bin option

Eshar

I am trying to use the soft_bin option.

1) I created a stimulus file containing the line: soft_bin=allmodels

2) I included the file using the stimulusFile command in Ocean 

 However, I received the following runtime error:

 soft_bin: Too few terminals given (0 < 2)

 

What are "terminals" that this message refers to?

I couldn't find much information regarding this simulation option so I would appreciate any guidance. 

Parents

  • Add this  in your stimulus file:

    instanceInfo info what=inst where=logfile

    and it will output information on each instance, including the name of the model (including the bin number) that was used, into the log file (spectre.out if run from OCEAN). You can use where=file if you want it to go to an ASCII file.

    It's also stored in the binary results database (from selectData('instance), but currently requires a private SKILL function to access it - there's a CCR to make a public function available - if you want that, please log a service request with customer support to add yourself to the customers requesting this.

    Andrew.

Reply

  • Add this  in your stimulus file:

    instanceInfo info what=inst where=logfile

    and it will output information on each instance, including the name of the model (including the bin number) that was used, into the log file (spectre.out if run from OCEAN). You can use where=file if you want it to go to an ASCII file.

    It's also stored in the binary results database (from selectData('instance), but currently requires a private SKILL function to access it - there's a CCR to make a public function available - if you want that, please log a service request with customer support to add yourself to the customers requesting this.

    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.