delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2015/01/18/03:12:33

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
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:content-transfer-encoding;
bh=heLoA4t7hZGvxpgmLtirjTtf9sQ9VwZ0epwjLy2KeUs=;
b=RwH6KzQzT3puzsUPlP3q2aRCcaf1aUQQjPyKrEsrf/DWgK5Y9YlmBhzxKNAmYQZl43
EClzOt/EnnAciUCIecDY0GTZHCE7LpS0nGLBSEuQx4BhFkcN7KCmETFPEqnMzSqp2SNV
YGNPufDqNkRYFTRAVG0nung4n6ImjQYS+mrqG+E3taS25AQbsmE8ZdbXK6REJ658F8Dz
yon+GjwtvX8FFHgwxnFJe1VhfLCXwgtK320oUq63dvpYDVxuOAiY0qCueV2nNdrzHbaV
5wachjU5vwH4eTJ0T3VLXti0R/8zxi+iBhYG+UXDQnjzOUcjR87H5B2nsupPo+GagptP
KAzg==
MIME-Version: 1.0
X-Received: by 10.112.44.171 with SMTP id f11mr23669069lbm.65.1421568655767;
Sun, 18 Jan 2015 00:10:55 -0800 (PST)
In-Reply-To: <20150118082153.Horde.YgV6W76ZDu7RKixhWgme4w1@webmail.in-berlin.de>
References: <20150116121619 DOT Horde DOT nPQGevRm4SzyvBjA40aa6Q2 AT webmail DOT in-berlin DOT de>
<5ff846f7 DOT 421e8d2d DOT 54b90bbc DOT c5ac2 AT o2 DOT pl>
<CAM2RGhQYcggzhw6embXFeJ3Chy_tZ2E9BTqoidMfbn5AQjndEg AT mail DOT gmail DOT com>
<20150118082153 DOT Horde DOT YgV6W76ZDu7RKixhWgme4w1 AT webmail DOT in-berlin DOT de>
Date: Sun, 18 Jan 2015 03:10:55 -0500
Message-ID: <CAM2RGhRukOO9bXpPQprQeWO=BtJxf9TvLTpQ5ndyigLpngj=jg@mail.gmail.com>
Subject: Re: [geda-user] Bunch Simulation ngspice
From: Evan Foss <evanfoss AT gmail DOT com>
To: geda-user AT delorie DOT com
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t0I8B44D031231
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

Ultimately I do generate 1 netlist for every combination but I do that
via make but I do not do it with one schematic for every variation.
Make exists to automate the development process. I am far from a
wizard at using it. I tend to just hack things together quickly
because the projects are more interesting to me than having ideal
design automation. The idea is this take the stuff that changes and
give it distinct schematic files. Take the stuff you are actually
designing and keep it in separate schematic file(s).

I used to think it would be good to keep one set of schematics for
everything (simulation and pcb layout). Reality how ever gave me a
swift kick.

I can talk more but it is damn late in my timezone. More another day.

Evan


On Sun, Jan 18, 2015 at 2:21 AM, Hagen SANKOWSKI
<hsank AT nospam DOT chipforge DOT org> wrote:
> Hello Evan.
>
> I see.. You have one schematic/netlist for every variation, right?
> This was also one of my ideas - and keep it beside. I argued myself
> against this like: "How I can keep other parts (than the variation) of
> my schematic/netlist constistent during the whole development process?"
> It would be a mess of 'diff'ing text files (gschem,spice) all the time.
>
> Well, nevertheless, do you have a piece of Makefile which you can hand
> me out as an example? I'm sorry, I am very bad in writing good Makefiles.
> Thank you, Evan.
>
> Any other solutions?
>
> Regards,
> Hagen.
>
>
>
> Quoting Evan Foss <evanfoss AT gmail DOT com>:
>
>> I typically do this via Makefiles. I have the different parameters for
>> the simulations in the schematics that way they are printed along with
>> everything else when I do post script export of the schematics. I have
>> the different things that need to be connected in the circuits split
>> off again in different schematic pages. The Makefile just runs the
>> simulations mixing and matching schematic pages.
>>
>> Not to kick off the holy war but this is exactly what we have make for.
>>
>> Evan
>>
>> On Fri, Jan 16, 2015 at 8:01 AM, michalwd1979 <michalwd1979 AT o2 DOT pl> wrote:
>>>
>>> Hello Hagen,
>>>
>>> I've done something like this using Python. I've used the output file to
>>> load data and plot them with Matplotliob and I've manually (from python)
>>> modified the simulation file.
>>> The problem is that You have to prepare the CIR file right, for example
>>> use
>>> .control, .endc block and include write command there. It is quite
>>> possible
>>> that I will find some examples of my old simulations if You are
>>> interested.
>>>
>>> Now look at the ngspice.py module, "runng" and "fromng" should be most
>>> important functions. There is also a "topwl" function that can create a
>>> PWL
>>> source subcircuit from given waveform data - nice to include real world
>>> signals gathered on scope to simulation.
>>>
>>> Best Regards,
>>> Michael W.
>>>
>>>
>>> Dnia 16 stycznia 2015 12:16 Hagen SANKOWSKI <hsank AT nospam DOT chipforge DOT org>
>>> napisaƂ(a):
>>>
>>>
>>>
>>> Hello geda-users!
>>>
>>> I like to run a bunch of simulations with ngspice, in the way of
>>> - run a netlist
>>> - change not only one parameter (sweep I know) but also replace
>>> circuits/models
>>> - run the modified netlist again
>>> - compare the results 'auto-magic'
>>> all controled by a script.
>>>
>>> The Tcl Interface (in contrast to the geda scheme stuff) I already
>>> noticed.
>>> I wonder if someone has an idea/script/example/hint how to do this
>>> efficently?
>>>
>>> Regards,
>>> Hagen.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Home
>> http://evanfoss.googlepages.com/
>> Work
>> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/
>
>
>
>
> --
> "They who can give up essential liberty to obtain a little temporary
> safety, deserve neither liberty nor safety." Benjamin Franklin (1775)
>
>



-- 
Home
http://evanfoss.googlepages.com/
Work
http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019