X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Message-ID:	<1438015655.2045.2.camel@ssalewski.de>
Subject:	Re: [geda-user] high freq, trace lengths (was: pcb-rnd feature
	poll: please vote)
From:	Stefan Salewski <mail AT ssalewski DOT de>
To:	geda-user AT delorie DOT com
Date:	Mon, 27 Jul 2015 18:47:35 +0200
In-Reply-To:	<CALT8Ef4rHxRL_4QhbKKNJhOXy2okUbPBNnOZia05hyxkQBqfZA@mail.gmail.com>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1507251201460 DOT 6924 AT igor2priv>
	<201507251534 DOT t6PFYRiK016181 AT envy DOT delorie DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1507251743490 DOT 6924 AT igor2priv>
	<201507260205 DOT t6Q257OU004585 AT envy DOT delorie DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1507260417410 DOT 6924 AT igor2priv>
	<20150727081830 DOT GC31594 AT visitor2 DOT iram DOT es>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1507271029180 DOT 6924 AT igor2priv>
	<20150727104850 DOT GA31438 AT visitor2 DOT iram DOT es>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1507271405400 DOT 6924 AT igor2priv>
	<CAOP4iL2NPg2OpivV_VVA5cq+Z_2n4RzQ4_GUagj2hB=fnTgU1w AT mail DOT gmail DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1507271603470 DOT 6924 AT igor2priv>
	<CALT8Ef5q52=3LJ7dV69vkDgdNXWQYXjgW0qsukdp+UgrBGL=LA AT mail DOT gmail DOT com>
	<CALT8Ef4rHxRL_4QhbKKNJhOXy2okUbPBNnOZia05hyxkQBqfZA AT mail DOT gmail DOT com>
X-Mailer:	Evolution 3.12.11
Mime-Version:	1.0
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

On Mon, 2015-07-27 at 20:21 +0530, Shashank Chintalagiri
(shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> (a python object hierarchy)
> 
> On Mon, Jul 27, 2015 at 8:18 PM, Shashank Chintalagiri
> <shashank DOT chintalagiri AT gmail DOT com> wrote:
> > Measuring trace lengths for a parallel bus is one of the things I'd
> > like to have as well.
> >
> > To that end (and various others), I've been working on a parser that
> > converts a PCB file into an object hierarchy. It's not even close to
> > doing anything useful yet, but I'm happy to share the core if you
> want
> > to use it. Of course, none of what I've written will actually work
> > _within_ pcb, but more as an external after-the-fact analysis tool.
> >

Sorry I have no idea about what you exactly intend -- can you give some
more details?

Convert PCB data into Python object? And what is the "after-the-fact
analysis tool"?

- Raw text -