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 Content-Type: multipart/alternative; boundary="Apple-Mail=_D853EA04-D724-4864-B31D-BE59787A846F" 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: To: geda-user AT delorie DOT com In-Reply-To: Message-Id: 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 Precedence: bulk --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 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=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.

On Jan 3, 2019, at 9:45 AM, gedau AT igor2 DOT repo DOT hu = wrote:

Hi all,

tEDAx is the Trivial EDA = eXchange format. Like 1000 other similar file
formats, it = is designed to allow different EDA tools to exchange data.
Unlike most other formats, the main objective of the tEDAx = format is to be
cheap to implement. It also has a free = specification under a very
permissive license.

I've just finished tEDAx drc block support in = pcb-rnd, both load and save,
so we have an implementation = anyone can use for testing.

tEDAx = specification: http://repo.hu/projects/tedax/

tEDAx drc block spec: http://repo.hu/projects/tedax/drc.html

If you maintain software that is dealing with printed circuit = board
geometry in any way, please consider implementing = support for the tEDAx
drc block.

Best regards,

Igor2

John Doty = Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com

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