• 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. ocean issue in OA

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 12829
  • 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 issue in OA

VictorB
VictorB over 14 years ago

Hi,

When I start from virtuoso(OA) with the command,
sh( strcat( "setenv SHELL /bin/ksh; chmod +x ./ocean/ocean_runner; xterm -T 'Ocean runner' -geometry 120x30+150+40 -fn *-fixed-*-*-*-20-* -e 'cd ocean; ocean; bash'&" ) )

the library manager loses the link to all libraries, they disappear .The libraries will reappear when restarting the library manager.In cadence 5 there was no issue. The command above launches a xterm and starts ocean, leaving out the last command ''ocean'' to start ocean, then there’s no issue

.sh( strcat( "setenv SHELL /bin/ksh; chmod +x ./ocean/ocean_runner; xterm -T 'Ocean runner' -geometry 120x30+150+40 -fn *-fixed-*-*-*-20-* -e 'cd ocean; bash'&" ) )

I hope someome can help,

rgdsRobert

 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    The problem is probably because of the child process inheriting the "MPS" session information from the parent, which is confusing communications between the tools. Try passing "-mpssession dummy" or something similar as an argument to "ocean".

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • VictorB
    VictorB over 14 years ago

    Thanks Andrew,

     passing "-mpssession dummy"  solved the issue.

    regards

    Robert

     

    • 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