[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
gEDA-user: Autorouter issues...
- To: geda-user@xxxxxxxx
- Subject: gEDA-user: Autorouter issues...
- From: Vanessa Dannenberg <vanessadannenberg@xxxxxxxxx>
- Date: Thu, 9 Mar 2006 05:22:58 -0500
- Delivered-to: archiver@seul.org
- Delivered-to: geda-user-outgoing@seul.org
- Delivered-to: geda-user@seul.org
- Delivery-date: Thu, 09 Mar 2006 05:24:47 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:reply-to:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=JSak4r862i7VU7g3yKMfIAPHy0xnVrTMBE9BqBxoV+YsQfD7OWn3J/UB2KbtD4QEIxQqan47KRHVG2EC7UARmCJw+xi1v9a57JH1TGll9JjB791qBPxI/iMOEF7oZxjMeC6si0MYaZngXj1oJXH+OnNkR/BnhOB/nib7Q8zHFRQ=
- Reply-to: geda-user@xxxxxxxx
- Sender: owner-geda-user@xxxxxxxx
- User-agent: KMail/1.9.1
Don't you just love when someone starts messing with the more obscure stuff
and finds little bugs here and there? :-)
The autorouter seems to work fine, except it does not appear to avoid polygons
as was originally thought. Harry, is it strictly necessary to place the
"keepout workaround" polygons on *all* layers, or just on the four I'm
routing on?
Another issue popped up today, which is not so much the autorouter itself, but
the optimizing functions... Most of them seem to work fine, but using the
"miter" optimizer (Connects->Optimize Routed Tracks->Miter) results in
multiple spacing violations when I run a follow-up DRC. Of course, before
Mitering, DRC comes back clean.
The result of the miter function does look nice though. Could it be possible
to add 45-degree increments to the autorouter so that the separate miter step
isn't necessary?
--
"Sometimes paranoia can be helpful. Usually it
isn't, and when you learn that, life improves."
Vanessa Dannenberg