Stats

  • Locked Locked
  • Replies 1
  • Subscribers 142
  • Views 13099
  • 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 scripting question

archive

Hello,

I'm a bit new to OCEAN, but understand that it falls in the category of SKILL.

Very often, in Analog Artist I will use a distributed processing option.  When netlisting, a popup dialog provides options for the distributed processing including an option to allow the job to be reused.

Now I have searched across the ocean documentation, and can't figure out how to properly set this option when using distributed processing in an ocean batch script.  Can anyone here provide some insight?  Thanks


Originally posted in cdnusers.org by superm1
Parents

  • The best you can do right now from OCEAN is to explicitly call the deleteJob() function once you're done with a job - this would allow the job name to be re-used.

    In IC5141 USR4 (due middle of September), PCR 664043 is being fixed such that the deleteJob cdsenv setting will be honoured during OCEAN submitted jobs. This means that:

    envSetVal("asimenv.distributed" "deleteJob" 'boolean t)

    This is the same cdsenv setting that is used to control the Reuse job name after completion checkbox on the submit job form in ADE.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
Reply

  • The best you can do right now from OCEAN is to explicitly call the deleteJob() function once you're done with a job - this would allow the job name to be re-used.

    In IC5141 USR4 (due middle of September), PCR 664043 is being fixed such that the deleteJob cdsenv setting will be honoured during OCEAN submitted jobs. This means that:

    envSetVal("asimenv.distributed" "deleteJob" 'boolean t)

    This is the same cdsenv setting that is used to control the Reuse job name after completion checkbox on the submit job form in ADE.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
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.