• 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. Shell commands in an OCEAN script

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 15077
  • 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

Shell commands in an OCEAN script

Ueue
Ueue over 16 years ago

Dear all,

 I would like to execute shell commands in an OCEAN script. For example removing files in order to increase the space on the disk between a simulation and the next. Is it possible?

 Thanks in advance.

  • Cancel
  • archive
    archive over 16 years ago

     Try the sh, shell, or system commands as documented in <cds dir>/doc/sklangref/sklangref.pdf

     Cheers,

     Roger

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 16 years ago

    Hi,

    While Roger is correct, there are also built-in SKILL commands for accessing the filesystem and in cases such as this it would be better to use those instead, for example:

    when(isFile("myFileToDelete")

       deleteFile("myFileToDelete")

    ); when

    Other commands that may be useful include getDirFiles(), fileTimeModified(), isFileName(), makeTempFileName() and getTempDir().

    Hope this helps you!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 16 years ago

    Hi,

    I forgot another very useful command: getWorkingDir(). 

    Also there are isDir(), createDir() and deleteDir().

    Regards,

    Lawrence.

    • 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