Re: Contribute
Henrik Johansson
Hi Arcadie,
Sorry about the late reply. I'm happy to hear that you are interested
in the project and would like to participate.
The simulator interfacing/post processing part of pycircuit is at the
moment not very developed so any contribution is more than welcome.
Most of the code was written to do limited post-processing of
simulation data from Eldo in PSF format. So just having other people
using it with different simulators and setups and report/fix bugs
would help alot.
Other areas that need more work are:
* Setting up a workflow from netlisting to post-processing. The
netlisting part is completely missing today and would probably need
some Skill/TCL/Shell scripting code to be written.
* Adding more post-processing helper functions like the ones in
https://github.com/henjo/pycircuit/blob/master/pycircuit/post/functions.py
* Writing a graphical waveform viewer in Python
* More examples in the documentation
Ultimately it would like to see a unified simulator interface that allows the
user to build simulator independent unittests for circuits. That
would require a well defined API for setting up analyses, parameters,
sweeps, modifying netlists etc.
A more short-term goal is to just have a solid flow that can
generate a netlist, add some analyses, run the simulator and finally
read back the data as waveforms and do some post-processing.
Numai bine,
Henrik
PS. Acum invăt românește la o universitate în Suedia, știu doar
puțin pentru ca am început toamna aceasta.
On 5 December 2010 20:58, Arcadie Cracan <acr...@gmail.com> wrote:
> Hello all,
>
> I just came across this project and it really got me interested. I had
> always wished to have a python package to interface Spectre/Eldo
> results, and also to be able to do some circuit simulations. I liked
> pycircuit this far and would like to contribute.
> I am a phd student at the Faculty of Electronics, Telecommunications
> and IT of the Technical University of Iasi, Romania. My interest is in
> analog circuit design, IC analog filters. I am quite familiar with
> Cadence's Spectre and Mentor Graphics' Eldo. My experience with python
> programming is mostly related to using scipy, matplotlib and a little
> of sympy.
> If there are any pycircuit tasks/little projects I could handle, I
> would gladly do so in my spare time.
>
> Best regards,
> Arcadie Cracan
>
> --
> You received this message because you are subscribed to the Google Groups "pycircuit" group.
> To post to this group, send email to pyci...@googlegroups.com.
> To unsubscribe from this group, send email to pycircuit+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pycircuit?hl=en.
>
>
Arcadie Cracan
I think it would be a good idea to put all your suggestions on a wiki page.
This way we could better keep track of their development. I noticed "git" has
some wiki implementation. Would it be possible for me to have access to
editing those pages?
> Most of the code was written to do limited post-processing of
> simulation data from Eldo in PSF format. So just having other people
> using it with different simulators and setups and report/fix bugs
> would help alot.
I have access to the Mentor Graphics tools, I'll try pycircuit with them and
will post about results.
> Other areas that need more work are:
> * Setting up a workflow from netlisting to post-processing. The
> netlisting part is completely missing today and would probably need
> some Skill/TCL/Shell scripting code to be written.
One thing I was excited about was that pycircuit is written entirely in
python. It would be nice if the netlisting tools were written in python also.
> * Writing a graphical waveform viewer in Python
I think we could use matplotlib for this purpose. It is actively developed and
has an extensive API for embedding in custom applications.
> * More examples in the documentation
Actually, I think this is the first thing I'll start doing. I will start
looking into the code and document it, along with setting up more examples.
Cele bune (best wishes),
Arcadie
P.S. M-ai surprins plăcut :). Cum de înveţi româneşte?
Henrik Johansson
Hi Aracadie,
On Tuesday 14 December 2010 11:42:54 Arcadie Cracan wrote:
>
> I think it would be a good idea to put all your suggestions on a wiki page.
> This way we could better keep track of their development. I noticed "git"
> has some wiki implementation. Would it be possible for me to have access
> to editing those pages?
Absolutely, I have added you as a collaborator which should give you write access to the wiki.
> > Most of the code was written to do limited post-processing of
> > simulation data from Eldo in PSF format. So just having other people
> > using it with different simulators and setups and report/fix bugs
> > would help alot.
>
> I have access to the Mentor Graphics tools, I'll try pycircuit with them
> and will post about results.
> > Other areas that need more work are:
> > * Setting up a workflow from netlisting to post-processing. The
> > netlisting part is completely missing today and would probably need
> > some Skill/TCL/Shell scripting code to be written.
>
> One thing I was excited about was that pycircuit is written entirely in
> python. It would be nice if the netlisting tools were written in python
> also.
The problem is that normally you have a PDK that integrates with a proprietary cad tool. In that case the only practical solution is to write some interface code in Skill or Tcl depending on what vendor you are using.
If the schematic tool is free software like gschem from the geda suite it would be very nice to have a netlister in Python. Actually I have written a hierarchical netlister for gschem in Python that generates gnucap netlists. I will release it when it's more mature.
> > * Writing a graphical waveform viewer in Python
>
> I think we could use matplotlib for this purpose. It is actively developed
> and has an extensive API for embedding in custom applications.
or maybe chaco (http://code.enthought.com/chaco/).
Here is a project using matplotlib:
http://gitorious.org/analog-plotter/analog-plotter/trees/master
> > * More examples in the documentation
>
> Actually, I think this is the first thing I'll start doing. I will start
> looking into the code and document it, along with setting up more examples.
That's great
/Henrik
PS. Invăț româneşte pentru că soția mea este din România.