= . Simulation-only components may appear in =E2=80=9Ctest fixture=E2=80=9D = schematics. Flow of revisions from master (layout) to tinkering = (simulation) may be controlled by a Makefile. Using SPICE to expand = hierarchy for simulation while flattening hierarchy for layout allows = for simulation-only components, where the spice-prototype rules = simulation, while a source file with no components (but possibly = connections) rules layout. For me, the missing piece is attributes on net segments. These could be = used for series parasitics in SPICE (using a suitable spice-prototype) = as well as communicating current-carrying capacity, impedance, and = topological constraints to layout. Right now, attributes can be attached = to nets with graphical symbols, but topological information is lost. I intended spice-noqsi to augment the toolkit approach, so it doesn=E2=80=99= t cover things that your configuration files, makefiles, sources, and = SPICE itself can accomplish. John Doty Noqsi Aerospace, Ltd. jpd AT noqsi DOT com --Apple-Mail=_C578FF05-A42C-4953-B153-880DD468CF21 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8

On Oct 15, 2020, at 11:31 PM, Glenn (glimrick AT epilitimus DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

I did look at spice-noqsi but it = didn't look to me like it solved the
problem.

The= spice-prototype attribute in spice-noqsi can do much of what you = want.

A component omitted from = simulation has:

spice-prototype=3D* = comment on reason for omission.

A = two terminal component to be short-circuited in simulation = has:

spice-prototype=3DR? #1 #2 = 0

There=E2=80=99s great benefit in = separating simulation and layout environments, see https://github.com/noqsi/gnet-spice-noqsi/wiki/Broadband-amplif= ier-board. Simulation-only components may appear in =E2=80=9Ctest = fixture=E2=80=9D schematics. Flow of revisions from master (layout) to = tinkering (simulation) may be controlled by a Makefile. Using SPICE to = expand hierarchy for simulation while flattening hierarchy for layout = allows for simulation-only components, where the spice-prototype rules = simulation, while a source file with no components (but possibly = connections) rules layout.

For me, = the missing piece is attributes on net segments. These could be used for = series parasitics in SPICE (using a suitable spice-prototype) as well as = communicating current-carrying capacity, impedance, and topological = constraints to layout. Right now, attributes can be attached to nets = with graphical symbols, but topological information is = lost.

I intended spice-noqsi to = augment the toolkit approach, so it doesn=E2=80=99t cover things that = your configuration files, makefiles, sources, and SPICE itself can = accomplish.

John Doty = Noqsi = Aerospace, Ltd.

jpd AT noqsi DOT com

= --Apple-Mail=_C578FF05-A42C-4953-B153-880DD468CF21--