X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.4 at av02.lsn.net Message-ID: <559E86A4.3040109@ecosensory.com> Date: Thu, 09 Jul 2015 09:35:16 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.6.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] Back annotation References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 07/09/2015 06:31 AM, Roland Lutz wrote: > Could you explain how you imagine back annotation to work? It could be as little as a command/button in gschem to import data from a layout. That would trigger parsing through all the data for attributes. Missing components would add to a "reverse rat list" of schematic symbols needing addition. existing components would take the tally of all the annotations and use them to update the schematic symbol. For instance, a printed resistance changes value based on the different area found by tallying attributes from the layout. Getting those attribs in the layout to be correct could be a separate step like: measure area with attrib R23 associated, and mark segments with correct resistance attribute, accounting for bend effects, or consolidate into one R value attrib attached to the group of segments. (See how that needs a new feature already? groups! essential to forward progress!) Another for instance would be: tally capacitance attribs for every segment that also has a net attrib, and add that up and update the schematic attrib corresponding to that net. Another for instance: First, run a program that uses geometry and an attrib on a footprint pin to search for capacitor components in a radius from the pin that are also attached by conductor, and gather up their frequency bands of good functioning attribs in a list. Then run an import function in gschem to update the schematic with those corresponding attrib lists. The corresponding attrib is not on the capacitor, but on the pin, and once you have the pin updated with lists, you run a DRC to tell if enough bypassing is done properly, and maybe where there is excess, but probably leave the analyzing of excess to human eyes. And on and on to richer, more complete DRCs on your design intent.