• 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. forking ocean scripts?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 13546
  • 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

forking ocean scripts?

markbeck
markbeck over 15 years ago

I'm trying to figure out amethod to fork a simulation from ICFB. 

Currently, I'm creating an ocean script that sets up the simulation in ICFB, and then spawns off an ocean session that then runs the simulation.  I'm doing this to keep the simulation from hanging the ICFB session while running.  This is working fairly well, but the main issue I'm encountering is that when I'm running small jobs, the time it takes the ocean session to spawn and statup is longer than the actual simulation.

Does anyone know how to issue a 'run()' command inside of ICFB that will fork off a new process that doesn't hang the ICFB session?

 Mark

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    If you use:

    option(?categ 'analog 'info "no")
    option(?categ 'analog 'warn "no")
    option(?categ 'analog 'note "no")

    that will massively reduce the output produced.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

    If you use:

    option(?categ 'analog 'info "no")
    option(?categ 'analog 'warn "no")
    option(?categ 'analog 'note "no")

    that will massively reduce the output produced.

    Regards,

    Andrew.

    • 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