• 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. Allegro X Scripting - Skill
  3. What do you know about RAVEL versus SKILL ?

Stats

  • Replies 1
  • Subscribers 19
  • Views 652
  • Members are here 0
More Content

What do you know about RAVEL versus SKILL ?

John T
John T 3 months ago

Show what you know! Can you answer these quick fire questions:

  1. True or False:  RAVEL is “declarative” while SKILL is “procedural/functional”?

  1. True or False: RAVEL violations can be cross‑probed in the layout via the DRC Browser?

 

  1. Choose the best option, “when to use”:
    A. SKILL to create new database objects; RAVEL to check rules/flag violations
    B. RAVEL to create symbols; SKILL to list DRCs
    C. SKILL only for DFM checks; RAVEL only for routing
    D. They’re interchangeable
  • Cancel
  • Sign in to reply
Parents
  • John T
    John T 2 months ago

    The answer to this is A:

    The RAVEL language was specifically designed to check and create custom design rules and flag design violations; unlike SKILL for accessing and manipulating database objects. 


    RAVEL is far better suited to writing custom DRCs than SKILL. The development effort needed and the code body text is much shorter. This in turn requires less effort to edit, repurpose or debug. Ravel rule files can be imported by menu, batch or a dedicated ui in the PCB Editor or Advanced Package Designer. 

      

    More information can be found here:

     BoardSurfers: Training Insights: Advanced Design Verification with RAVEL 

     BoardSurfers: Training Insights: How to Run a RAVEL Rule from the GUI 

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000006AhKSUA0&pageName=ArticleContent

    Do share any thoughts or experience you have with this language and features. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • John T
    John T 2 months ago

    The answer to this is A:

    The RAVEL language was specifically designed to check and create custom design rules and flag design violations; unlike SKILL for accessing and manipulating database objects. 


    RAVEL is far better suited to writing custom DRCs than SKILL. The development effort needed and the code body text is much shorter. This in turn requires less effort to edit, repurpose or debug. Ravel rule files can be imported by menu, batch or a dedicated ui in the PCB Editor or Advanced Package Designer. 

      

    More information can be found here:

     BoardSurfers: Training Insights: Advanced Design Verification with RAVEL 

     BoardSurfers: Training Insights: How to Run a RAVEL Rule from the GUI 

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000006AhKSUA0&pageName=ArticleContent

    Do share any thoughts or experience you have with this language and features. 

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
Cadence Guidelines

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.

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

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