X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-TCPREMOTEIP: 50.201.94.142 X-Authenticated-UID: jpd AT noqsi DOT com From: John Doty Content-Type: multipart/alternative; boundary="Apple-Mail=_B69724C2-61C6-4780-83E8-7572800FD9DF" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: [geda-user] SAB processing patches Date: Wed, 9 Dec 2020 15:07:29 -0500 References: <20201130220505 DOT 0AE4282C54FD AT turkos DOT aspodata DOT se> <7c75ed03-456c-b408-8b50-0448f6b3a04f AT epilitimus DOT com> <1b2c64b3-6a36-c1f3-dd54-bb583c6bea17 AT epilitimus DOT com> <475f980e-fddd-60d1-9a02-a5bc5fb5805b AT epilitimus DOT com> <25887669-D8C1-48B8-BEE7-13EEBFC4D006 AT noqsi DOT com> <7caba1cb-6f7f-d3b8-d60d-88dd242310df AT epilitimus DOT com> To: "Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com]" In-Reply-To: <7caba1cb-6f7f-d3b8-d60d-88dd242310df@epilitimus.com> Message-Id: X-Mailer: Apple Mail (2.3608.120.23.2.4) 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=_B69724C2-61C6-4780-83E8-7572800FD9DF Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Dec 9, 2020, at 1:52 PM, Glenn (glimrick AT epilitimus DOT com) [via = geda-user AT delorie DOT com] wrote: >=20 > John Doty wrote: >>=20 >>=20 >>> On Dec 9, 2020, at 12:42 AM, Glenn (glimrick AT epilitimus DOT com >>> ) [via geda-user AT delorie DOT com >>> ] >> > wrote: >>>=20 >>>> So the gnetlist backend to generate the xspice netlist needs the >>>> bridge devices in the schematic (the sim context) >>=20 >> Not true. With gnet-spice-noqsi, you may put the bridge devices = either >> in a subcircuit that=E2=80=99s referenced by the spice-prototype = attribute, or >> directly in the spice-prototype attribute. >>=20 >>>> but other non >>>> simulation netlists (the ab context), e.g. pcd or partslist, need = them >>>> removed. At the risk of starting another discusson, this is why the >>>> spice-noqsi backend was not going to work, it works in the sim >>>> context. >>=20 >> The stuff in a spice-prototype attribute is ignored by every other >> netlister. That=E2=80=99s how you can keep the sims domain separate = from from >> other domains. >>=20 > The whole point here is that the bridge devices and other simulation > components show up when processing the schematic for a parts list or > some other non simulation context. That=E2=80=99s because you put them in as symbols in the schematic. = Don=E2=80=99t do it that way. Give your components the interfaces they = need behind their pins. Use explicit SPICE code in the spice-prototype = or draw a simulation schematic of the component and refer to that as a = subcircuit in your spice-prototype, but not in a source attribute. >=20 > Glenn >=20 John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_B69724C2-61C6-4780-83E8-7572800FD9DF Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8


John = Doty wrote:


On Dec 9, = 2020, at 12:42 AM, Glenn (glimrick AT epilitimus DOT com
<mailto:glimrick AT epilitimus DOT com>) [via geda-user AT delorie DOT com
<mailto:geda-user AT delorie DOT com>] <geda-user AT delorie DOT com
<mailto:geda-user AT delorie DOT com>> wrote:

So the = gnetlist backend to generate the xspice netlist needs the
bridge devices in the schematic (the sim context)

Not true. With = gnet-spice-noqsi, you may put the bridge devices either
in = a subcircuit that=E2=80=99s referenced by the spice-prototype attribute, = or
directly in the spice-prototype attribute.

but other non
simulation = netlists (the ab context), e.g. pcd or partslist, need them
removed. At the risk of starting another discusson, this is = why the
spice-noqsi backend was not going to work, it = works in the sim
context.

The stuff in a = spice-prototype attribute is ignored by every other
netlister. That=E2=80=99s how you can keep the sims domain = separate from from
other domains.

The whole point here is that the bridge devices = and other simulation
components show up when processing = the schematic for a parts list or
some other non = simulation context.

That=E2=80=99s because you put them in as symbols in = the schematic. Don=E2=80=99t do it that way. Give your components the = interfaces they need behind their pins. Use explicit SPICE code in the = spice-prototype or draw a simulation schematic of the component and = refer to that as a subcircuit in your spice-prototype, but not in a = source attribute.


Glenn


John Doty    =           Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com




= --Apple-Mail=_B69724C2-61C6-4780-83E8-7572800FD9DF--