• 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. ADEXL: Post-Processing Ocean Scripts - Results Access

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 2505
  • 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

ADEXL: Post-Processing Ocean Scripts - Results Access

ronanc
ronanc over 11 years ago

Hi,

 

I would like to call an ocean script I have that in turn calls an Octave (Matlab alternative) script.
I’d like my ADEXL corner simulations to automatically launch this ocean script, post process
each individual corner, and then read back in the text file that’s output by Octave.
 
I’ve managed to launch a simple Ocean script by adding it to my outputs in my ADEXL session,
but I’m not sure how to access the results database. The axlCurrentResultsPath variable does not appear
to be set. Also, axlGetMainSetupDB requires a “session name”, which to me seems will change each
time I run a new batch of corners.
 

Any help would be greatly appreciated. Thanks.
 
Best regards,

Ronan 

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

    Ronan,

    axlCurrentResultsPath is only supported in Matlab measurements, not in OCEAN. Also, you cannot use the spectre toolbox for Matlab with Octave - whilst Octave has a source code compatible API to add custom commands at the C level, I don't believe you can use a shared library built for Matlab in Octave instead. We do not support a similar toolbox for Octave (mostly because the software license for Octave presents problems for a commercial software company).

    From an OCEAN script, you should be able to call openResults() (with no arguments) to find out where the results directory is - but I'm not sure how this would help you if you were to then invoke Octave from the OCEAN script (e.g. with ipcBeginProcess()), since there's nothing in Octave to read the results database. Maybe you could use OCEAN to access the data you want, write it to an ASCII file (e..g using ocnPrint), invoke Octave to do the post-processing reading from the ASCII file and writing a new one, and then reading that in the OCEAN script. Sounds quite a bit of work...

    There is also the axl API too - but it's not that clear precisely what you're trying to do?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Ronan,

    axlCurrentResultsPath is only supported in Matlab measurements, not in OCEAN. Also, you cannot use the spectre toolbox for Matlab with Octave - whilst Octave has a source code compatible API to add custom commands at the C level, I don't believe you can use a shared library built for Matlab in Octave instead. We do not support a similar toolbox for Octave (mostly because the software license for Octave presents problems for a commercial software company).

    From an OCEAN script, you should be able to call openResults() (with no arguments) to find out where the results directory is - but I'm not sure how this would help you if you were to then invoke Octave from the OCEAN script (e.g. with ipcBeginProcess()), since there's nothing in Octave to read the results database. Maybe you could use OCEAN to access the data you want, write it to an ASCII file (e..g using ocnPrint), invoke Octave to do the post-processing reading from the ASCII file and writing a new one, and then reading that in the OCEAN script. Sounds quite a bit of work...

    There is also the axl API too - but it's not that clear precisely what you're trying to do?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information