Shorts and DRC

Here is a solution that fits pretty much anywhere:   https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000007MqM1UAK&pageName=ArticleContent

Does it require the use of Concept?  It is pretty nifty solution, my ATE guys would love this, but the front end does look like Concept and not Capture.  Please let me know if I'm wrong on this.

Kind Regards,

Wild

I did not know you were using Capture!     The documentation specifies DEHDL but you may want to file a case and ask Cadence about doing this in Capture or just give it a try.  I use it a lot for far end star single source clocks in addition to sense lines.

Not sure what the original poster uses, but my team is in the capture land.  I've used the netshorting trick for a number of years (too many), only issue I've had is that the cam file check at fab shows an unconnected net between the netshorts.    I usually just approve and move on, this scheme looks like it is a better solution.  I may enter a ticket on this one.  Many thanks!

Not sure what the original poster uses, but my team is in the capture land.  I've used the netshorting trick for a number of years (too many), only issue I've had is that the cam file check at fab shows an unconnected net between the netshorts.    I usually just approve and move on, this scheme looks like it is a better solution.  I may enter a ticket on this one.  Many thanks!

I believe it usually shows as two or multiple nets shorted.  I drive a lot of things grammatically and in my environment the user ends up with  a standard note to add to the fab drawing detailing each use of the forcesense symbol detailing location and nets shorted.   One of either ODB++ or 2581 also tags it nicely as a net short instance.  I forget which at the moment.