• 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. ocean script

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 13989
  • 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 script

Stefan Bormann
Stefan Bormann over 13 years ago

 Hi,

I have an oceanscript (originally created by adexl) and I want to write the output from one fuction to a file:

I have this part:

of = outfile( "output_log" "w")

port:"output_log"
ocnxlOutputSummary(?yieldSummary t ?exprSummary nil ?specSummary nil ?detailed nil)

Yield summary:
==============
  test:nch_model_test:1:
    Name            Yield  Min  Target     Max    Mean   sigma To Target   sigma   Errors
    IDC("/M0/D")_C17:mctt 100 2.803u         info 11.33u 5.958u                     2.253u       0
Estimated yield = 100.000000% (10/10), 0 errors
Estimated yield (No opregions) = 100.000000% (10/10)t

 

if I try to use fprintf(of "%s" ocnxlOutputSummary(?yieldSummary t ?exprSummary nil ?specSummary nil ?detailed nil))

it create an empty file ...

 

I also tried to use the command ocnPrint but this created only a file with the status (t, nil) of the print.

 any ideas to get the command line print from ocean out to a file?

 Thanks

-Stefan

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Stefan,

    Not sure which version you're using, but ocnxlOutputSummary() has a ?fileName argument now to write to a file. If that's not available, I have a workaround - but please state which version you're using.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Stefan Bormann
    Stefan Bormann over 13 years ago

    Hi Andrew,

    thanks for the quick reply.

    I looked into the Ocean refence (6.1.5) but under ocnxlOutputSummary() is no argument like ?fileName listed.

    I'm using virtuoso 6.1.5.500.5 and typing version at the ocean prompt gives me this: "v2008.4_28.20".

     

    Regards

    -Stefan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Stefan,

    This was added in IC615 ISR8 (6.1.5.500.8). Can you use a later subversion? Note that typing "version" at the OCEAN prompt is presumably telling you the value of some SKILL variable in your environment/customization (it's not from us). You'd type getVersion() or getVersion(t) to get the subversion in SKILL.

    The workaround if you really cannot use a later subversion is to use:

    Currently the ocnxlOutputSummary does not support writing the summary information to a file. If you want to do this, the following wrapper around ocnxlOutputSummary may be used. This takes the same arguments as ocnxlOutputSummary, but adds an extra ?output argument to allow a file output handle to be specified:

    procedure(TrOcnxlOutputSummary(@key (output poport) @rest args)
      let(((poport output))
        apply(’ocnxlOutputSummary args)
      )
    )

    An example of using this:

    prt=outfile("summaryReport.txt")
    TrOcnxlOutputSummary(?output prt ?exprSummary t ?detailed nil)
    close(prt)

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Stefan Bormann
    Stefan Bormann over 13 years ago

     Thanks. It works good. And parallel I will force to install the latest  virtuoso version here at our site.

     

    Regards

    -Stefan

    • 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