Stats

  • Locked Locked
  • Replies 5
  • Subscribers 62
  • Views 8305
  • 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

How to count number of paths in RTL-compiler group?

dkos

 Hello all!

 Does anybody knows how to count number of paths in group, created by 'path_group' command? Or, at least, determine is group empty or not?

Thanks, dkos

Parents
  • grasshopper

     Hi dkos,

    another alternative if you are up to some scripting is to rely on the timing_info attribute associated with every startpoint and endpoint. In addition you can use the startpoint and endpoint attribute to identify which pins are which. This attribute will provide you with the cost_group information for every endpoint as well as all exception associated with it. Amonst all the exception is the path_group information. As you can tell, it is essential to be clear on the distinction between path_group and cost_group to get the script to work right. Another caveat I would keep in mind is the use of multi-mode constraints since different mode could result in different cost groups as well. Anyhow, hope this helped

    gh-

Reply
  • grasshopper

     Hi dkos,

    another alternative if you are up to some scripting is to rely on the timing_info attribute associated with every startpoint and endpoint. In addition you can use the startpoint and endpoint attribute to identify which pins are which. This attribute will provide you with the cost_group information for every endpoint as well as all exception associated with it. Amonst all the exception is the path_group information. As you can tell, it is essential to be clear on the distinction between path_group and cost_group to get the script to work right. Another caveat I would keep in mind is the use of multi-mode constraints since different mode could result in different cost groups as well. Anyhow, hope this helped

    gh-

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.