Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 14416
  • 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 LVS: Clarification on virtual connection using joinablePin() function.

ShrikantTI
Suppose if the there is unconnected net and if i create the pin on the two unconnected terminals and run the assura using joinablePin() function i would be able to clear the LVS and then go ahead and create the RCX netlist. When RCX netlist is created, how is this issue taken care? and what kind of parasitic's are extracted? Suppose there is net created between two terminals but still i go ahead and create pin on these terminals retaining the net and use joinablePin() again to create the short then run LVS amd then RCX, in that case what is be considered for the RCX extraction? which will have higher precedent ? short created because of the joinablePin() or actual layout existed for the net?
Parents

  • Hi Shrikant

    I think perhaps you meant "joinableNet" function because there is no joinablePin function. I am not quite sure what you meant by "what kind of parasitic's are extracted". If you had set "C-only" extraction in the QRC or RCX form, then only parasitic capacitors will be present in the netlist. If "RC" extraction has been selected, then you will get parasitic capacitors and resistors.

    Would you please provide more details for the problem?

    Best regards
    Quek

Reply

  • Hi Shrikant

    I think perhaps you meant "joinableNet" function because there is no joinablePin function. I am not quite sure what you meant by "what kind of parasitic's are extracted". If you had set "C-only" extraction in the QRC or RCX form, then only parasitic capacitors will be present in the netlist. If "RC" extraction has been selected, then you will get parasitic capacitors and resistors.

    Would you please provide more details for the problem?

    Best regards
    Quek

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.