X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 26 Aug 2015 18:19:03 +0200 (CEST)
X-X-Sender: igor2 AT igor2priv
To: geda-user AT delorie DOT com
X-Debug: to=geda-user AT delorie DOT com from="gedau AT igor2 DOT repo DOT hu"
From: gedau AT igor2 DOT repo DOT hu
Subject: Re: [geda-user] Antifork
In-Reply-To: <20150826180132.2828eeae@Parasomnia.thuis.lan>
Message-ID: <alpine.DEB.2.00.1508261816280.6924@igor2priv>
References: <55D8D8B8 DOT 7050907 AT jump-ing DOT de> <CAM2RGhSZ1vi_DFKqZdZYxhto4ZaXLLscBt5m5kk+PH2ZoYW_vw AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1508230609370 DOT 6924 AT igor2priv> <55D9BDC7 DOT 4000608 AT jump-ing DOT de> <alpine DOT DEB DOT 2 DOT 00 DOT 1508231450350 DOT 6924 AT igor2priv>
 <CAM2RGhSC6UfCr8ixF5iuffmUhcdgVuz9nA+YjiZNk8-f7Q5r-A AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1508231935040 DOT 6924 AT igor2priv> <CAC4O8c8PyLQNgxz1SP-98ZhyH5KPDmnNpiULVvdL+TMo-DhN4w AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1508240407100 DOT 6924 AT igor2priv>
 <CAC4O8c_HdSL-3+etrvPozAZuqUX-Rqx4FGACkchttRkZsFhYPA AT mail DOT gmail DOT com> <CAM2RGhQMUdE_Z6OnJPTgTbkcQ4fWp6rGnrXib48S71tsGmMMSw AT mail DOT gmail DOT com> <CAC4O8c8N53Yf=AXwNhVYX=NJ_ua5gKVD4zBipTHsrFcaFRbt-w AT mail DOT gmail DOT com> <20150826180132 DOT 2828eeae AT Parasomnia DOT thuis DOT lan>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
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



On Wed, 26 Aug 2015, Bas Gieltjes wrote:

>
>
>>> I keep seeing mentions of this legendary router. I have been these
>>> gEDA lists +10 years but I don't remember it. What was the big
>>> appeal if it?
>>
>> It's a non-orthogonal router with good performance metrics.  The
>> description is academic but it looks not too hard to add keep-out
>> areas, additional costs to the cost functions, etc.  I don't know how
>> far Stefan ever got with those real-life
>> features.  I've lost the paper its based on but it was fairly
>> readable.
>
> See PCB's toporouter.c file, it mentions five publications.
>
> Here is Stefan's reimplementation using Ruby, including images:
> http://www.ssalewski.de/Router.html.en

Nice. If anyone feels like investing time in it, I can provide all support 
from pcb-rnd's side to get this a working pcb-rnd script. Form the user's 
perspective this'd mean full integration.

Regards,

Igor2