Stats

  • Locked Locked
  • Replies 6
  • Subscribers 143
  • Views 16170
  • 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

Running multiple AC simulations with multiple stimulus files using Ocean Script

lartola

Dear all,

I would run multiple AC simulations (with Spectre simulator) using an Ocean Script. However I would change for each loop the stimulus file. I don't know how to specify the changing of the name of the stimulus file for each run.

 

Thanks in advance for  your help

 

laurent 

Parents

  •  Hi Laurent,

    The problem is that each time you call stimulusFile() with a different file, it adds to the list of stimulus files. The usual way of solving this with OCEAN is to use the delete() function to reset the particular item (you can delete analyses, saves etc), but unfortunately delete('stimulusFile) hasn't been implemented yet.

    This is described in my solution 1026408 on Cadence Online Support. The workaround is to use::

    asiSetEnvOptionVal(asiGetCurrentSession() 'stimulusFile list(stimFile))

    where stimFile is the file you want to set. This will override any previous stimulus file lists that have been set.

    Regards,

    Andrew.

Reply

  •  Hi Laurent,

    The problem is that each time you call stimulusFile() with a different file, it adds to the list of stimulus files. The usual way of solving this with OCEAN is to use the delete() function to reset the particular item (you can delete analyses, saves etc), but unfortunately delete('stimulusFile) hasn't been implemented yet.

    This is described in my solution 1026408 on Cadence Online Support. The workaround is to use::

    asiSetEnvOptionVal(asiGetCurrentSession() 'stimulusFile list(stimFile))

    where stimFile is the file you want to set. This will override any previous stimulus file lists that have been set.

    Regards,

    Andrew.

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.