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-transfer-encoding;
        bh=EuGFZuqg2ggE1Ho593/3ofBVh7m/0pxZHTuvOJp0VEM=;
        b=ZNFqjXFUXZX5vdcv57wPShyAS+eCfpkMsY2GW3g/esfhHXW7dknld+20CYMFtEUKOX
         ss5ptRJIy+xqCTnilx2YU4TJW6wbXYKTCXvyJoBsQQxQhQNxHBoMaPgNc3shyiQiEZTg
         LM75ZCKoixPtbhsG4Q0WI9buLfala19jQwBlg2pmdz704NfFVoee9VX9jnhtpuvaFE5m
         OtklVjUD4jfKLB7KdsrGM5tWmuGAdhL4BvJ+ZOB1NGaWkmpte5z8pePFlqM7FeS5/BeI
         Rk0HNGXrvAVPPX4eWoV6SJwGS/w875QD/n1nef1iw5AXc3XuDXrQ39tKCSpiG3TzPk2B
         lbvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to:content-transfer-encoding;
        bh=EuGFZuqg2ggE1Ho593/3ofBVh7m/0pxZHTuvOJp0VEM=;
        b=IMtgc5/wUOQGt7b0CPk3typ22hXbsTZ82cUOhIe2QMl16/PL0cHtAWBomtr65H4wxC
         SGwiTfymGqFButAHfjCTGaN9ESYwF0Zz5xctUlb1FTm95dDqw0cKjeZaPN4BXYHaGYDg
         GAlptSjieWT4rNIni5XzOJriX5ENwjeAcWldAWe7m6B1HnIHYpjxZTa13BO+/Qgogauj
         J8atStRbwFLEwTTvEyODpniRlmRSTG8wQCfAKyZrCWAs0lcbTPhYHJYi0QjMexSB+HRm
         TpJtMw6rVCHWc6aJscpYhEZqlKXijZzGK5keOgwpDyCkORxGBrWmE1CUpPGP3UXn4m5a
         xt4A==
X-Gm-Message-State: AD7BkJK4Mz8heFWoJDNDNIMftmId/1WWyIMAG3tTkvft2cVaMY6V0Ufn5t/ChnvbH28B+kDnf5SgzEd1n/vZqw==
MIME-Version: 1.0
X-Received: by 10.31.149.78 with SMTP id x75mr9204932vkd.103.1456694776278;
 Sun, 28 Feb 2016 13:26:16 -0800 (PST)
In-Reply-To: <D1E8415E-11EF-434B-B857-E2C1A47CB99D@noqsi.com>
References: <20160215215221 DOT fd472794e7b9446a243bfc40 AT gmail DOT com>
	<20160216081722 DOT 1065cbed6653d3da4ffc7498 AT gmail DOT com>
	<201602160724 DOT u1G7Ox26001785 AT envy DOT delorie DOT com>
	<20160216085628 DOT b70143c330cd4da98a4603d3 AT gmail DOT com>
	<201602160805 DOT u1G85d8c003148 AT envy DOT delorie DOT com>
	<20160216092912 DOT 7f7439f703b49175a21dbb1b AT gmail DOT com>
	<CAJXU7q_w5NunkojiCr36RHRTq0hJ+PZP1e0GumTRMoGXcvgRXQ AT mail DOT gmail DOT com>
	<201602161715 DOT u1GHFMBB028078 AT envy DOT delorie DOT com>
	<CAC4O8c9jr_b376SpuUk5HrJApP1c75oxsEBemn-i_xtC-rt-Zw AT mail DOT gmail DOT com>
	<201602162032 DOT u1GKWL7Y005291 AT envy DOT delorie DOT com>
	<CAC4O8c-ig=0UVAqagNXH_DBmC9uVQDu3Y1Gx7LBGmRCo0-_kVQ AT mail DOT gmail DOT com>
	<E75ECBB6-14E7-437A-B374-E0CF86BDFF1A AT noqsi DOT com>
	<CAC4O8c8z4JiJr=mgA+co4pX-yxu_pVsXpeKRYqneuxZNnYqh8g AT mail DOT gmail DOT com>
	<CAC4O8c8ejSN3GrmB1Zw=Dx9Pm-3Y0jwjNs=yjmwgsqcoVW5ACw AT mail DOT gmail DOT com>
	<59CE9019-7A56-49D6-BC2B-680A7253B055 AT noqsi DOT com>
	<nauuv2$m6r$1 AT ger DOT gmane DOT org>
	<20160228153707 DOT 6ca09160d8b85ac77357302b AT gmail DOT com>
	<87h9gsycrl DOT fsf AT rover DOT gag DOT com>
	<20160228211220 DOT 2042e36fa5dcca51062a40ea AT gmail DOT com>
	<D1E8415E-11EF-434B-B857-E2C1A47CB99D AT noqsi DOT com>
Date: Mon, 29 Feb 2016 02:56:16 +0530
Message-ID: <CALT8Ef4jgS0DpVQQmOqiZDa0mKPP+25z8bfwB8hLfsUxoR7Gzw@mail.gmail.com>
Subject: Re: [geda-user] pcb import --> Symbol heavifier
From: "Shashank Chintalagiri (shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id u1SLQJrI005037
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

I have a (fairly unwieldy and heavy) framework in-place / in-the-works
to do almost exactly that. It's far from being generally usable,
though. It's fairly complicated to setup, makes a lot of assumptions
and is overly susceptible to changes in vendor websites . The sources
are all up on github[1]. If you're interested in it you can get in
touch and I can try to help walk you through evaluating / setting it
up.

[1] https://github.com/chintal/tendril

Chintalagiri Shashank


On Mon, Feb 29, 2016 at 2:30 AM, John Doty <jpd AT noqsi DOT com> wrote:
>
> On Feb 28, 2016, at 1:12 PM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>>>> A BOM generator which automatically heavify symbols with ordering
>>>> information is what I ultimately want to write. Of course there have
>>>> to be a database with values to pick from.
>>>
>>> Keith and I recently put something like this together for Altus Metrum.
>>>
>>> We now, by default, only set three attributes on a part: 'device',
>>> 'footprint', and 'value'.  We have a "preferred parts" database that's
>>> just a tab-separated-values flat file, and a couple awk scripts that
>>> take the attributes for each part in a csv file, use the triplet above
>>> to index into the database, and fill in any missing attributes.
>>>
>>> This means that for almost all parts, we only have one place to update
>>> when we change manufacturer part data or vendor info for our 'preferred
>>> parts', yet we can override any attribute we need to on a per-design
>>> basis. ...
>>
>> In particular there will be no need to update schematic then there are no changes to schematic.
>>
>> This is particularly useful if there is a need for distributor part number.
>>
>>
>> Nicklas Karlsson
>>
>
> What I do is to make a key from four attributes: device, value, spec, and footprint. Spec is something like “50WVDC X7R” or “1% 1/10W”. Together, these form a sufficiently unique key to identify a part.
>
> But it gets tricky then, because there are generally separate organizations involved with their own approaches. The folks who order parts will have a “database” (really a spreadsheet) of approved parts. The board assembly house will have their own form they want. So, I have to customize the scripts frequently. One project has used three different layout shops and four different assembly shops for different phases.
>
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com
>
>