X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Message-ID: <20150910131034.32423.qmail@stuge.se> Date: Thu, 10 Sep 2015 15:10:34 +0200 From: "Peter Stuge (peter AT stuge DOT se) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] zero soldermask clearance not caught by DRC Mail-Followup-To: geda-user AT delorie DOT com References: <55F1640D DOT 5080703 AT envinsci DOT co DOT uk> <55F17B4F DOT 30207 AT jump-ing DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55F17B4F.30207@jump-ing.de> Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Markus Hitter (mah AT jump-ing DOT de) [via geda-user AT delorie DOT com] wrote: > > Are shorted nets detectable by some other means? > > Shorts are detected when optimizing rats. That's, case in point, not very intuitive. > DRC does just DRC, not connection checking. It could and should check connections too. I often find myself running DRC and optimizing rats (only to check connections!) together, it makes perfect sense to make connection checking part of DRC, either in addition to, or maybe instead of, rat optimization. //Peter