• 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. RF Design
  3. spectre mtline connection problem

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 64
  • Views 18287
  • 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

spectre mtline connection problem

jyang
jyang over 12 years ago

When using mtline model in cadence spectre schematic simulation, why I can not connect output of one mtline to output of another mtline? (warnings show there will be short circuit and floating nodes)

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Frank,

    First of all, there really is no such thing as a "few minute" fix. Fixes need to be implemented, reviewed, checked in and potentially merged into multiple streams, tested, regression tests implemented - all of which takes more time. Given that we end up with lots of small fixes such as this which are competing for attention, we tend to focus on those which are the biggest obstacles to be fixed in hotfixes. Other things will be planned for future releases during the planning phase for a release. If submitted before that planning phase, or even if the plate is too full for a particular release, they may be marked Inactive-Backlog. These are then reconsidered at the next planning phase - we cannot plan the next release as we go along as otherwise it would always be first-in first-out rather than assessing the overall requirements.

    So no need to campaign for this in public; it's not being ignored.

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Frank,

    First of all, there really is no such thing as a "few minute" fix. Fixes need to be implemented, reviewed, checked in and potentially merged into multiple streams, tested, regression tests implemented - all of which takes more time. Given that we end up with lots of small fixes such as this which are competing for attention, we tend to focus on those which are the biggest obstacles to be fixed in hotfixes. Other things will be planned for future releases during the planning phase for a release. If submitted before that planning phase, or even if the plate is too full for a particular release, they may be marked Inactive-Backlog. These are then reconsidered at the next planning phase - we cannot plan the next release as we go along as otherwise it would always be first-in first-out rather than assessing the overall requirements.

    So no need to campaign for this in public; it's not being ignored.

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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