• 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. screen with ocean

Stats

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

screen with ocean

vikram1977
vikram1977 over 13 years ago
hello i invoke an ocean script from within a bash file many times (in a for loop) i use screen to detach my running program when i reattach the screen program, i figure out that ocean was run only one time and dosn't carry on can you please help to find what make the main loop don't work best regards
  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    I've not really used the screen command, but having taken a quick look at it, I think you'll need to describe more about the specifics of what you're doing so that there's a chance somebody might be able to comprehend and answer your question.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ebecheto
    ebecheto over 13 years ago

     Did you try first with nohup ?

    Also a warning, I suppose you run  ocean for different Hierarchy. Indeed, if you run spectre for a same design, it will overwrite the result directory (psf) so you will get only the last simulation.

    NB : if you want a clearer answer, ask a clear/detailed question.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vikram1977
    vikram1977 over 13 years ago
    Thank you Andrew, ebecheto sorry about the ambiguity i found the source of the probleme the probleme actually is not screen but the ocean script when you run the ocean script with the -nograph option , you have to explicitly add an exit() at the end of the ocean script, otherwise it will hang that what was happenning with me.
    Unknown said:
    For example, while using OCEAN with the -nograph option, your oceanScript.ocn file must have an exit() statement at the end. Otherwise, OCEAN hangs. The reason for this is that when the workbench is started in the non-graphical mode, it does not redirect standard I/O as it normally does; instead, it lets the SKILL human interface (HI) handle the standard I/O. HI expects an explicit exit() statement at the end of the OCEAN script and OCEAN exits only when it detects an exit() at EOF.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vikram1977
    vikram1977 over 13 years ago

     for clarification that was the context of the question

    foreach myvariable ("case1" "case2" "case3")

    ocean -nograph < oeanScript.ocn

    end

    the problem was that the the ocean script was invoked only for case1, and the cause was that ocean hanged since there was no exit() statement at the end of the oceanScript.ocn file

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vikram1977
    vikram1977 over 13 years ago
    sorray again waht do you mean by nohup, i can't find it on ocean manual regards
    ebecheto said:

     Did you try first with nohup ?

    Also a warning, I suppose you run  ocean for different Hierarchy. Indeed, if you run spectre for a same design, it will overwrite the result directory (psf) so you will get only the last simulation.

    NB : if you want a clearer answer, ask a clear/detailed question.

    • 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