X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:content-type;
	bh=GeTNt2HCE0pOXd55n/qZw8sOIgVmnBGD7CPUam9okOY=;
	b=B+JcdFrtlYq2OkUs7oNr/wi2VDVX7j2ECQ71klXFArU/NmZLnqMfzcnK5ZUfoXOBbm
	0d/kWyYNSi6zMiZkGXbK4l4T0eqUO4s9Zs/+7+yp39GvSmUJ4uRtJ4T5wPd1j+Ua3NSY
	8Z843R7CS3w0ewwqhbn9SDgfjlyLKWoeEcnhR6yjT8M6h/F9W6tSakiG3Um1wyXiBxqw
	Iq86KRYV0IbJqccOmv8ZZqjVdiSb40hRdodsFxuTYYw4HMniVWgK91TOKTIGiZehzibC
	c1Ge5aOFNpiXfDHlBJce1lOpq3EZQAxqbP11Hx9BxvXsQeymfQ+93QTWi7ljrfZkeeNv
	9lig==
MIME-Version:	1.0
X-Received:	by 10.107.129.215 with SMTP id l84mr298954ioi.78.1437110573396;
	Thu, 16 Jul 2015 22:22:53 -0700 (PDT)
In-Reply-To:	<201507162045.t6GKj06r028442@envy.delorie.com>
References:	<CAM2RGhQ70Pex5aNeQ86vKHc7sKf_Vpws69__CPb2QKg6fJTeHg AT mail DOT gmail DOT com>
	<20150712224637 DOT 2d4cc2de AT wind DOT levalinux DOT org>
	<55A2E9B7 DOT 9040502 AT neurotica DOT com>
	<CAM2RGhSmFhz9=oRaaj2EDL79c5XVmeuwmX_RdLqMv0evEHCyTw AT mail DOT gmail DOT com>
	<CACwWb3DbmOZbtb9Hrp2JvvG7-toryXuequQA=YV7X6ss762zsw AT mail DOT gmail DOT com>
	<20150713131707 DOT GA782 AT recycle DOT lbl DOT gov>
	<CAM2RGhTT__nWCkA4y36rb24yT8xP=o1nR04H=DNqTJiu=naSGA AT mail DOT gmail DOT com>
	<55A4042E DOT 5060402 AT neurotica DOT com>
	<CAM2RGhS=5xq0_oN4e0M55Kor4bcnXNn3NfLvRZoi7Vw9Aq1ZXg AT mail DOT gmail DOT com>
	<55A41B30 DOT 50602 AT neurotica DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1507151114560 DOT 2113 AT nimbus>
	<254F9AFE-1A3E-4D88-BABF-E6E0F87A56B1 AT icloud DOT com>
	<1436960577 DOT 1072 DOT 6 DOT camel AT ssalewski DOT de>
	<EE9F72D6-E17A-4F5C-8E9E-45F12C901C9F AT noqsi DOT com>
	<201507151820 DOT t6FIKYME001704 AT envy DOT delorie DOT com>
	<201507152007 DOT t6FK7lv8005229 AT envy DOT delorie DOT com>
	<24AD56C6-B7C2-4D7E-B69A-F68DBACCBFDC AT noqsi DOT com>
	<4DD9C29A-2105-45DC-9F17-82DA23433919 AT icloud DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1507160907360 DOT 3383 AT nimbus>
	<CAOP4iL2koQTZe03R8g8eWfTO4sTPoGNyjvi_+c4eCFExd=udWA AT mail DOT gmail DOT com>
	<74093FC3-C9AA-4AFF-A158-720676E70E49 AT noqsi DOT com>
	<201507162045 DOT t6GKj06r028442 AT envy DOT delorie DOT com>
Date:	Thu, 16 Jul 2015 22:22:53 -0700
Message-ID:	<CAOP4iL2vCMun8fg+5WHpudu7=h39Y=LocXWaR=1jXh-OjJftaA@mail.gmail.com>
Subject:	Re: [geda-user] Net attributes
From:	"Ouabache Designworks (z3qmtr45 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Note-from-DJ:	This may be spam
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

--001a113ec6ac3afa49051b0b61e8
Content-Type: text/plain; charset=UTF-8

On Thu, Jul 16, 2015 at 1:45 PM, DJ Delorie <dj AT delorie DOT com> wrote:

>
> > What happens if the same segment in different instances of a
> > subcircuit has different properties, for example?
>
> Does our heirarchy system even have a way of parameterizing
> subcircuits?  I mean, if you had a subcircuit for a generic low-pass
> filter, could you specify the cutoff in the parent somehow?
>


This is called elaboration or uniquification in the ic world. If you
instantiate a component x times with different attributes then you need to
expand it to x copies that each show one set of attributes. It is a step
you must do before flatting.


We also need a way to support adding schematcs to a schematic as well as
symbols. If you are doing a stereo amp then you do one schematic of a
channel with XXX in every instance name and net name. Then you add that
schematic to your design by macro replacing xxx with right and again
replacing xxx with left to get both channels.


John Eaton

--001a113ec6ac3afa49051b0b61e8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Jul 16, 2015 at 1:45 PM, DJ Delorie <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dj AT delorie DOT com" target=3D"_blank">dj AT delorie DOT com</a>&gt;</span=
> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex"><span class=3D""><br>
&gt; What happens if the same segment in different instances of a<br>
&gt; subcircuit has different properties, for example?<br>
<br>
</span>Does our heirarchy system even have a way of parameterizing<br>
subcircuits?=C2=A0 I mean, if you had a subcircuit for a generic low-pass<b=
r>
filter, could you specify the cutoff in the parent somehow?<br>
</blockquote></div><br><br></div><div class=3D"gmail_extra">This is called =
elaboration or uniquification in the ic world. If you instantiate a compone=
nt x times with different attributes then you need to expand it to x copies=
 that each show one set of attributes. It is a step you must do before flat=
ting. <br><br><br></div><div class=3D"gmail_extra">We also need a way to su=
pport adding schematcs to a schematic as well as symbols. If you are doing =
a stereo amp then you do one schematic of a channel with XXX in every insta=
nce name and net name. Then you add that schematic to your design by macro =
replacing xxx with right and again replacing xxx with left to get both chan=
nels.<br><br><br></div><div class=3D"gmail_extra">John Eaton<br><br><br><br=
></div></div>

--001a113ec6ac3afa49051b0b61e8--

- Raw text -