X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=bAZYW8Me7xFJvgjs7UPVYdj2q6uUgJc5DzCheYu4WdU=;
	b=MFMo6UoJz23UiGjpg/TwoSJ27gyPEiy5amvN3CM1hoz95/Nz4xRm4MNP20w2AiwzpN
	PWShON3XGAWfgY4sMQPo70Td/RfVqUYVfujHGQv6OrGXQamOof3zVrrznGGizshfCUYV
	GK35p4ILeoijfIUJO9GbTV5xAHi29XdYlbGTKL70fqb3MsabdOzPBVVPFeabMmfYIsJv
	7gqwRaljEEu1kr9yhkxpVihaHpCOIGxM9wF4ynvUMN1Ji+bnqwcj8Qk95+ba8EwVlExy
	g9F881FkKqNGh08aF5SgcvMathIqLAKq8GxBqKiFaDHa6rbvT5uCsHPO3X1pt8DWSy8M
	cmFA==
MIME-Version:	1.0
X-Received:	by 10.180.93.168 with SMTP id cv8mr11638584wib.54.1444603339347;
	Sun, 11 Oct 2015 15:42:19 -0700 (PDT)
In-Reply-To:	<mv4l1j$c2c$1@ger.gmane.org>
References:	<20151003210701 DOT de392b925f54dadb0a5fedd8 AT gmail DOT com>
	<1443903758 DOT 1873 DOT 13 DOT camel AT ssalewski DOT de>
	<56104A0A DOT 9020507 AT xs4all DOT nl>
	<1443909591 DOT 1873 DOT 18 DOT camel AT ssalewski DOT de>
	<CAC4O8c_g7e562Gaotrbi6gLfjP6cJU1ys=MtEkDE7bSh4F9dfg AT mail DOT gmail DOT com>
	<1443975731 DOT 671 DOT 52 DOT camel AT ssalewski DOT de>
	<20151004191717 DOT bf8223417541a9306bfbd9ea AT gmail DOT com>
	<CAC4O8c9Bi5HJfcW6wUgm_+4O2gs4vDdBMbS2hF_0dCqnBuJahQ AT mail DOT gmail DOT com>
	<1443997480 DOT 2068 DOT 32 DOT camel AT ssalewski DOT de>
	<CAC4O8c-bnGky=Nab59-pOTJkB8Q9Tc5t5hqE+dnEF-777hUjMg AT mail DOT gmail DOT com>
	<1444070851 DOT 1014 DOT 20 DOT camel AT ssalewski DOT de>
	<muv4ua$hat$1 AT ger DOT gmane DOT org>
	<1444157156 DOT 1949 DOT 52 DOT camel AT ssalewski DOT de>
	<56141CCE DOT 2030301 AT ecosensory DOT com>
	<1444165764 DOT 1949 DOT 78 DOT camel AT ssalewski DOT de>
	<mv4l1j$c2c$1 AT ger DOT gmane DOT org>
Date:	Sun, 11 Oct 2015 14:42:19 -0800
Message-ID:	<CAC4O8c_o6zem5Kfr89BR3jBZBiNj78vR80-4W+B7YhHOiY2=Ww@mail.gmail.com>
Subject:	Re: [geda-user] GTK3, Glade interface designer (router, auto?)
From:	"Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
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

--f46d043c7fbae222d90521dbec40
Content-Type: text/plain; charset=UTF-8

On Wed, Oct 7, 2015 at 6:39 PM, Kai-Martin Knaak <kmk AT familieknaak DOT de>
wrote:

> Stefan Salewski wrote:
>
> > The toporouter as described in in the PhD thesis of Tal Dayan from
> > 1997 assumes that there is an empty area for routing, which is only
> > restricted by the size of pads and pins. So each already existing
> > trace is a problem.
>
> I suspected so. So this is worse than just a not yet coded feature.
> Unfortunately, doing some portions in advance manually is key to deal
> with many special cases. Examples:
>

Yes I like to do manual first too.  To make it useful, what's needed is
first a "discovery pass"
on the existing board to take it back to topology.  I think you can't put
that much burden
of keep-outs on cost function or geometry portion of the algorithm and have
it work right.
I've very excited to try to write this if someone else doesn't beat me to
it:)

Britton

--f46d043c7fbae222d90521dbec40
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Oct 7, 2015 at 6:39 PM, Kai-Martin Knaak <span dir=3D"ltr">&lt;=
<a href=3D"mailto:kmk AT familieknaak DOT de" target=3D"_blank">kmk AT familieknaak DOT d=
e</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Stefan Salewski w=
rote:<br>
<br>
&gt; The toporouter as described in in the PhD thesis of Tal Dayan from<br>
&gt; 1997 assumes that there is an empty area for routing, which is only<br=
>
&gt; restricted by the size of pads and pins. So each already existing<br>
&gt; trace is a problem.<br>
<br>
I suspected so. So this is worse than just a not yet coded feature.<br>
Unfortunately, doing some portions in advance manually is key to deal<br>
with many special cases. Examples:<br></blockquote><div><br></div><div styl=
e=3D"">Yes I like to do manual first too.=C2=A0 To make it useful, what&#39=
;s needed is first a &quot;discovery pass&quot;</div><div style=3D"">on the=
 existing board to take it back to topology.=C2=A0 I think you can&#39;t pu=
t that much burden</div><div style=3D"">of keep-outs on cost function or ge=
ometry portion of the algorithm and have it work right.</div><div style=3D"=
">I&#39;ve very excited to try to write this if someone else doesn&#39;t be=
at me to it:)<br></div><div><br></div><div style=3D"">Britton</div><div><br=
></div></div></div></div>

--f46d043c7fbae222d90521dbec40--

- Raw text -