• 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. files missing in Spectre psf result directory when running...

Stats

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

files missing in Spectre psf result directory when running simulation from command line

HansB
HansB over 7 years ago

sHi,

I’m running Spectre transient simulation from command line (actually from within a Skill/Ocean script)

Jobs run ok but when post processing the data I noticed a couple of files are missing compared to when same simulations are executed from ADE-L environment.

The files missing are

variables_file

simRunData

runObjFile

artistLogFile

The files are needed to extract variable values and to determine the simulator.

How can I get to full set of files in PSF result dir when running simulations from command line ?

kind regards

Hans

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    Hans,

    Presumably you're not running it via the run() function in OCEAN, because that would then write out the variables database and set up the runObjFile to reference it. How are you running the simulation?

    If you had an info analysis in the netlist:

    designParamVals info what=parameters where=rawfile

    Then you'd be able to access the variables using:

    pv("top-level" "CAP" ?result 'designParamVals)

    where CAP is the variable name. No need for the other stuff, which is additional info that ADE/OCEAN outputs.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HansB
    HansB over 7 years ago in reply to Andrew Beckett

    Andrew,

    Thanks for quick response!

    Indeed, the script submits one or more jobs using  ipcBeginProcess(run_string "")  instead of the Ocean Run().

    And then ipcWait() before starting the post processing.

    For the Spectre simulator the input.scs contains "designParamVals info what=parameters where=rawfile" allowing the expression pv("top-level" "CAP" ?result 'designParamVals). But I have one other simulator that does not generate that info...

    Just to be sure: I went through Skill and Ocean language reference manuals in search of a function that generates the files missing in the psf. I've observed they are generated/written during run time. But did not find anything. The file creation is undocumented ?

    kind regards

    Hans

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to HansB

    Hans,

    There's no standalone function to do this, because it's intended to be done as part of ADE or OCEAN running the simulation. If you're bypassing that, you're also bypassing the component of ADE which records the design variables it has passed to the simulator - because it didn't know you'd even called the simulator.

    Why don't you just use run()?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • HansB
    HansB over 7 years ago in reply to Andrew Beckett

    Andrew,

    My thinking was that even when "bypassing" the ADE framework  there could have been an oasis function that generates the files now missing in psf, given that e.g. netlist + psf directories and simulator are all known the moment the simulator is called ? I would just need to call that function in parallel and drop the files into the psf.

    The ipcBeginProcess()  for running the simulator was inherited.... You are saying that run() can be a full equivalent, even when running third party simulator and interactively running multiple parallel simulations ?  

    kind regards,

    Hans

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • HansB
    HansB over 7 years ago in reply to Andrew Beckett

    Andrew,

    My thinking was that even when "bypassing" the ADE framework  there could have been an oasis function that generates the files now missing in psf, given that e.g. netlist + psf directories and simulator are all known the moment the simulator is called ? I would just need to call that function in parallel and drop the files into the psf.

    The ipcBeginProcess()  for running the simulator was inherited.... You are saying that run() can be a full equivalent, even when running third party simulator and interactively running multiple parallel simulations ?  

    kind regards,

    Hans

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to HansB

    Hans,

    Not sure why there would need to be a public function to do this. It's part of ADE and the expectation is that there would be no need to run it separately. So there isn't a public function to do this as a separate step.

    If you can run the third party simulator in ADE, you can run it using run(). Parallel simulations are possible via the distributed mechanism (you can use the command-line mode if you're not really using a distributed mechanism). The variables database is a bit of a legacy thing anyway.

    Regards,

    Andrew.

    • 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