• 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. RAVEL DRC Programming for IC Packaging and…
  3. Using ravCheckAndReport with multiple generic rule deck...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 23
  • Views 16636
  • 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

Using ravCheckAndReport with multiple generic rule decks

GMaggy
GMaggy over 10 years ago

How do I use the ravCheckAndReport command to evaluate multiple generic rule decks using a single control file?  I was able to do this using earlier versions of Ravel prior to 2.18.  However, with the check that was added to Ravel version 2.18 that raises an error when a control file lists rules that do not exist in the rule deck, this method no longer works?  Is this even possible anymore?

For example:

ravCheckAndReport(list("path_to_die.ravge" "pad_size.ravge" "sm_opening.ravge") ?tag nil ?control "my_control_file.ravgc")

now throws an error:

E- *Error* Checks in control file not matched by rules in deck: ((check ("Path to Die" "Path to Die Edge Distance")) (check ("Pad Size" "Pad Width")) (check ("Pad Size" "Pad Length")) (check ("SM Opening" "SM Opening")))

  • Cancel
  • Bjoern L
    Bjoern L over 10 years ago

    Hello,

    this check was made more restrictive to prevent the situation where a misspelled rule name in a control file would cause the rule to be silently omitted. The danger was that the user might believe that rules were being checked that in reality were not. The use case that you mention is also a reasonable one, and we will have to look at how to accommodate both. At the moment there is no workaround, because the report generation will run each generic rule deck in turn with the control file, and will encounter the mismatch in rule names.

    Best regards,

    Björn

    • 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