• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. OCEAN script generated for AMS + APS simulation

Stats

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

OCEAN script generated for AMS + APS simulation

alleyor
alleyor over 11 years ago

Hi all,

I was recently working on a mixed-singal simulation with AMS. To speed up the simulation, in ADE, I chose simulation performance mode as "APS", and manually chose 8 threads. In ADE, everything goes well, 8 cpu cores were brought up for the simulation, the simulation finished quite soon.

Then I generated an ocean script from ADE, and tried to run the script in OCEAN enviorment. But this time, it seems only one cpu cores was working and thus a very long simulation time was experienced. I checked there are the following warnings:  

 

  •  WARNING (OCN-6012): Invalid option: numThreads. Use ocnDisplay('option) to see the list of options, or
  •         use ocnHelp('option). You can also refer to online help on simulator.
  • WARNING (OCN-6012): Invalid option: mtOption. Use ocnDisplay('option) to see the list of options, or
  •         use ocnHelp('option). You can also refer to online help on simulator.
  • WARNING (OCN-6012): Invalid option: uniMode. Use ocnDisplay('option) to see the list of options, or
  •         use ocnHelp('option). You can also refer to online help on simulator.

 

 I use Cadence ic6.1.5-64b.500.16.2; MMSIM 121

the machine I used has 8 cores. 

The automatic generated ocean script was as following (simplified) :

--------------------------------------------------------------------------------------------------- 

simulator( 'ams )

solver( 'Spectre )

design(....)

ocnAmsSetOSSNetlister()

resultsDir( "..." )

connectRules()

globalSignal(?name "gnd!" ?lang "CDBA" ?wireType "wire" ?discipline "" ?ground "YES")

globalSignal(?name "vdd!" ?lang "CDBA" ?wireType "wire" ?discipline "" ?ground "NO")

modelFile( )

analysis('tran ?stop "30n"  )

desVar(  "vdd" 1.5 )

envOption(

'netlisterMode  "OSS-based" 

'invocationStyle  "irun" 

'builtinuser  nil 

'cleanSnapShot  list(t) 

)

option( ?categ 'amsTurboOpts

'numThreads  "8" 

'mtOption  "Manual" 

'uniMode  "Turbo" 

)

temp( 27 ) 

run() 

 

Thanks in advance for your help! 

  • Cancel
Parents
  • alleyor
    alleyor over 11 years ago
    Sorry, the 'uniMode should be "APS", not "Turbo".
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • alleyor
    alleyor over 11 years ago
    Sorry, the 'uniMode should be "APS", not "Turbo".
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information