www.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2019/01/04/09:15:43

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 173.48.170.224
X-Authenticated-UID: jpd AT noqsi DOT com
From: John Doty <jpd AT noqsi DOT com>
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [geda-user] [tEDAx] drc block: spec and ref implementation
finished
Date: Fri, 4 Jan 2019 09:12:44 -0500
References: <alpine DOT DEB DOT 2 DOT 00 DOT 1901031533140 DOT 21900 AT igor2priv>
To: geda-user AT delorie DOT com
In-Reply-To: <alpine.DEB.2.00.1901031533140.21900@igor2priv>
Message-Id: <EC7FE5E0-8E90-47D4-AD98-F12A399F210E@noqsi.com>
X-Mailer: Apple Mail (2.3273)
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

--Apple-Mail=_D853EA04-D724-4864-B31D-BE59787A846F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

A few comments from a SPICE simulation/IC design perspective.

Having separate value and device attributes for SPICE is a good idea.

The rest of your SPICE concept seems not to address the difficulties. =
Merely having a component value is not enough in many cases. See the =
prototypes at the end of =
https://github.com/noqsi/gnet-spice-noqsi/wiki/Reference. These only =
cover the most common cases: this needs to be user-extensible.

Your pin sequence/slot concept seems to follow the gschem/gnetlist =
approach. This has historically caused a lot of trouble, a rare =
fundamental design error in geda-gaf.

It looks like you=E2=80=99re planning to support hierarchy in the =
future. This would be very handy for simulation, and it is essential in =
flows that feed SPICE netlists to layout tools.

> On Jan 3, 2019, at 9:45 AM, gedau AT igor2 DOT repo DOT hu wrote:
>=20
> Hi all,
>=20
> tEDAx is the Trivial EDA eXchange format. Like 1000 other similar file=20=

> formats, it is designed to allow different EDA tools to exchange data.=20=

> Unlike most other formats, the main objective of the tEDAx format is =
to be=20
> cheap to implement. It also has a free specification under a very=20
> permissive license.=20
>=20
> I've just finished tEDAx drc block support in pcb-rnd, both load and =
save,=20
> so we have an implementation anyone can use for testing.
>=20
> tEDAx specification: http://repo.hu/projects/tedax/
>=20
> tEDAx drc block spec: http://repo.hu/projects/tedax/drc.html
>=20
> If you maintain software that is dealing with printed circuit board=20
> geometry in any way, please consider implementing support for the =
tEDAx=20
> drc block.
>=20
> Best regards,
>=20
> Igor2
>=20

John Doty              Noqsi Aerospace, Ltd.
jpd AT noqsi DOT com




--Apple-Mail=_D853EA04-D724-4864-B31D-BE59787A846F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">A few comments from a SPICE simulation/IC design =
perspective.<div class=3D""><br class=3D""></div><div class=3D"">Having =
separate value and device attributes for SPICE is a good idea.</div><div =
class=3D""><br class=3D""></div><div class=3D"">The rest of your SPICE =
concept seems not to address the difficulties. Merely having a component =
value is not enough in many cases. See the prototypes at the end =
of&nbsp;<a =
href=3D"https://github.com/noqsi/gnet-spice-noqsi/wiki/Reference" =
class=3D"">https://github.com/noqsi/gnet-spice-noqsi/wiki/Reference</a>. =
These only cover the most common cases: this needs to be =
user-extensible.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Your pin sequence/slot concept seems to follow the =
gschem/gnetlist approach. This has historically caused a lot of trouble, =
a rare fundamental design error in geda-gaf.<br class=3D""><div =
class=3D""><br class=3D""></div><div class=3D"">It looks like you=E2=80=99=
re planning to support hierarchy in the future. This would be very handy =
for simulation, and it is essential in flows that feed SPICE netlists to =
layout tools.</div><div class=3D""><br class=3D""></div><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On Jan 3, 2019, at 9:45 AM, <a =
href=3D"mailto:gedau AT igor2 DOT repo DOT hu" class=3D"">gedau AT igor2 DOT repo DOT hu</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">Hi all,<br class=3D""><br class=3D"">tEDAx is the Trivial EDA =
eXchange format. Like 1000 other similar file <br class=3D"">formats, it =
is designed to allow different EDA tools to exchange data. <br =
class=3D"">Unlike most other formats, the main objective of the tEDAx =
format is to be <br class=3D"">cheap to implement. It also has a free =
specification under a very <br class=3D"">permissive license. <br =
class=3D""><br class=3D"">I've just finished tEDAx drc block support in =
pcb-rnd, both load and save, <br class=3D"">so we have an implementation =
anyone can use for testing.<br class=3D""><br class=3D"">tEDAx =
specification: <a href=3D"http://repo.hu/projects/tedax/" =
class=3D"">http://repo.hu/projects/tedax/</a><br class=3D""><br =
class=3D"">tEDAx drc block spec: <a =
href=3D"http://repo.hu/projects/tedax/drc.html" =
class=3D"">http://repo.hu/projects/tedax/drc.html</a><br class=3D""><br =
class=3D"">If you maintain software that is dealing with printed circuit =
board <br class=3D"">geometry in any way, please consider implementing =
support for the tEDAx <br class=3D"">drc block.<br class=3D""><br =
class=3D"">Best regards,<br class=3D""><br class=3D"">Igor2<br =
class=3D""><br class=3D""></div></div></blockquote></div><br =
class=3D""><div class=3D"">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px; font-variant-ligatures: normal; =
font-variant-east-asian: normal; font-variant-position: normal; =
line-height: normal;"><div style=3D"word-wrap: break-word;" =
class=3D""><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-ligatures: =
normal; font-variant-caps: normal; font-variant-east-asian: normal; =
font-variant-position: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; text-indent: 0px; text-transform: none; =
orphans: 2; white-space: normal; widows: 2; word-spacing: 0px;"><p =
style=3D"margin: 0px;" class=3D""><font face=3D"Helvetica" size=3D"3" =
style=3D"font-style: normal; font-variant-caps: normal; font-weight: =
normal; font-size: 12px; line-height: normal; font-family: Helvetica;" =
class=3D"">John Doty<span class=3D"Apple-converted-space">&nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-converted-tab">&nbsp; &nbsp;<span =
class=3D"Apple-converted-space">&nbsp;</span></span></span>Noqsi =
Aerospace, Ltd.</font></p><p style=3D"margin: 0px;" class=3D""><a =
href=3D"mailto:jpd AT noqsi DOT com" class=3D"">jpd AT noqsi DOT com</a></p><br =
class=3D"Apple-interchange-newline"></span></div></span><br =
class=3D"Apple-interchange-newline">
</div>
<br class=3D""></div></body></html>=

--Apple-Mail=_D853EA04-D724-4864-B31D-BE59787A846F--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019