• 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 SKILL
  3. question about Ocean "resultsDir"

Stats

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

question about Ocean "resultsDir"

DavidLou
DavidLou over 6 years ago

hello export,

I'm trying to run an ocean script multiple times simultaneously as regression. for that, I need each simulation to go different directory without clashing other running ones. but seems ”resultsDir“ command only relocates psf result, not the netlist folder which still located at "~/simulation/top_test/ams/cosim_config/netlist/". 

should there be any other command I can use to redirect the netlist folder? 

thanks a lot,

David

IC6.1.7-64b.500.9

simulator( 'ams )
solver( 'Spectre )

; for config based case
design( "lib" "top" "cosim_config" "r")

resultsDir( result_dir )

ocnAmsSetOSSNetlister()

connectRules("ConnRules_mid")

modelFile( 
'("....._usage.scs" "tt_lib")
)
analysis('tran ?stop "1" ?errpreset "conservative" )

envOption(
'amsIEsList '((t "global" "" "1.8" "connectLib.CR_full_fast" "" "logic" "discipline=logic;" "Built-in"))
'builtinuser nil
)

temp( 27 )

run()

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    You would need to change the projectDir env var to change the top level dir for each run before you call the simulator() function (envSetVal("asimenv.startup" "projectDir" 'string "...")

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DavidLou
    DavidLou over 6 years ago in reply to Andrew Beckett

    perfectly working now. thanks Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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