• 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. Assura ELW Source Code or Function Name

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 142
  • Views 14258
  • 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

Assura ELW Source Code or Function Name

archive
archive over 17 years ago

This is a somewhat specific case question and I'm not sure if it belongs here... but this is the most appropriate place that I know of:

After running Assura DRC on a cell, Assura's output is printed to a cellName.log file and passed to the ELW for parsing and viewing of errors by the user.

Does anyone know of the function name of the ELW window parser?

I am running assura through a Skill script and want to pass the output to the ELW for viewing.

Thanks!


Originally posted in cdnusers.org by ahamlett
  • Cancel
  • archive
    archive over 17 years ago

    I found the name of the Open Run function: _vuiLViewLayout()

    I think the Skill Tracer will allow me to see the name of the function that actually opens the Assura output...


    Originally posted in cdnusers.org by ahamlett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Skill Functions List in HTML :)
    http://uan.no-ip.com:8080/~ahamlett/uploaded/SkillFunctions.html


    Originally posted in cdnusers.org by ahamlett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    You might want to remove that HTML, because you're almost certainly breaking your license agreement by publishing this...

    Andrew.


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