https://wiki.f-si.org/api.php?action=feedcontributions&user=Felix&feedformat=atomF-Si wiki - User contributions [en]2024-03-29T06:13:43ZUser contributionsMediaWiki 1.36.1https://wiki.f-si.org/index.php?title=Verilog-AMS_in_Gnucap&diff=2994Verilog-AMS in Gnucap2023-07-11T09:50:31Z<p>Felix: /* Downloads */</p>
<hr />
<div>* Speaker(s): Felix Salfelder<br />
* email: felix at salfelder dot o r g<br />
* other information:<br />
<br />
==Downloads==<br />
* [http://felix.salfelder.org/gnucap/fsic_gnucap23.pdf slides]<br />
<br />
==Abstract==<br />
As the need to replace proprietary CAD tools by free ones is growing, the Gnucap project has made<br />
unprecedented [http://gnucap.org/dokuwiki/doku.php/gnucap:projects:nlnet:verilogAMS progress]<br />
towards a sustainable Verilog-AMS implementation.<br />
<br />
In this presentation, we will introduce the new model generator and related simulator extensions. We will expand on future developments and their impact on modelling and simulation.<br />
<br />
==Software==<br />
===General information===<br />
* Repository: https://git.savannah.gnu.org/cgit/gnucap/<br />
* Main documentation website: http://gnucap.org<br />
* Wikipedia page if any: https://en.wikipedia.org/wiki/gnucap.<br />
* The software has been used in the following projects: gEDA, Qucs, KiCAD, ..<br />
<br />
===Roadmap===<br />
* The software wishes to interface with the following tools: PCB, Layout, GUI<br />
* The project seeks help on: Funding, data exchange, extensions, customization..<br />
<br />
==References==<br />
* https://nlnet.nl/project/Gnucap-VerilogAMS/</div>Felixhttps://wiki.f-si.org/index.php?title=Verilog-AMS_in_Gnucap&diff=2930Verilog-AMS in Gnucap2023-07-09T05:27:29Z<p>Felix: use template</p>
<hr />
<div>* Speaker(s): Felix Salfelder<br />
* email: felix at salfelder dot o r g<br />
* other information:<br />
<br />
==Downloads==<br />
* [[:File:gnucap_File_name.pdf|Slides]] (WIP)<br />
<br />
==Abstract==<br />
As the need to replace proprietary CAD tools by free ones is growing, the Gnucap project has made<br />
unprecedented [http://gnucap.org/dokuwiki/doku.php/gnucap:projects:nlnet:verilogAMS progress]<br />
towards a sustainable Verilog-AMS implementation.<br />
<br />
In this presentation, we will introduce the new model generator and related simulator extensions. We will expand on future developments and their impact on modelling and simulation.<br />
<br />
==Software==<br />
===General information===<br />
* Repository: https://git.savannah.gnu.org/cgit/gnucap/<br />
* Main documentation website: http://gnucap.org<br />
* Wikipedia page if any: https://en.wikipedia.org/wiki/gnucap.<br />
* The software has been used in the following projects: gEDA, Qucs, KiCAD, ..<br />
<br />
===Roadmap===<br />
* The software wishes to interface with the following tools: PCB, Layout, GUI<br />
* The project seeks help on: Funding, data exchange, extensions, customization..<br />
<br />
==References==<br />
* https://nlnet.nl/project/Gnucap-VerilogAMS/</div>Felixhttps://wiki.f-si.org/index.php?title=Verilog-AMS_in_Gnucap&diff=2788Verilog-AMS in Gnucap2023-05-31T10:08:47Z<p>Felix: initial stub</p>
<hr />
<div>As the need to replace proprietary CAD tools by free ones is growing, the Gnucap project has made<br />
unprecedented [http://gnucap.org/dokuwiki/doku.php/gnucap:projects:nlnet:verilogAMS progress]<br />
towards a sustainable Verilog-AMS implementation.<br />
<br />
In this presentation, we will introduce the new model generator and related simulator extensions. We will expand on future developments and their impact on modelling and simulation.</div>Felixhttps://wiki.f-si.org/index.php?title=Merging_Gnucap_and_Qucs_--_The_Why_and_How&diff=2647Merging Gnucap and Qucs -- The Why and How2022-07-08T13:58:18Z<p>Felix: add slides</p>
<hr />
<div>* Speaker: Felix Salfelder<br />
* email: felix@salfelder.org<br />
* other information: [http://felix.salfelder.org/gnucap/fsic_gqmerge.pdf slides]]<br />
<br />
==Abstract==<br />
<br />
Gnucap and Qucs are two complementary projects both created and distributed in the hope that they will be useful. In a nutshell, Gnucap lacks a graphical user interface that Qucs has, and Qucs lacks a developer friendly implementation and extensibility. In this talk I will highlight the individual strengths of these projects, and explain how they relate to other projects such as Ngspice. I will outline how the two prototype implementations, "Gnucsator" and "modular Qucs", target the interoperability between Gnucap, Qucs and beyond.<br />
<br />
Gnucsator provides a simulator emulating Qucsator, the simulator used from within Qucs. It consists of a collection of Gnucap plugins that have been either implemented from scratch or as a wrapper around (unmodified) Qucsator model code. With very little effort, Gnucsator plugins allow the translation of netlists between Qucs and, say, Verilog file formats. More interestingly, simulation of a circuit with models from Gnucap, Qucsator, Spice3f5, NGspice etc. is straightforward.<br />
<br />
The modular Qucs code base has evolved during refactoring Qucs, porting to Qt5, and turning inessential parts into plugins. During this process, the way to replaceable, alternative symbols, component models, simulators and file formats including data file formats has been paved. Some of these have been implemented and are workable, others are easy to add. As of now, the modular Qucs GUI, mainly the schematic editor, has too many bugs. Fortunately, the GUI is not essential for all tasks...<br />
<br />
Merging the Qucs and Gnucap projects is a promising step towards a feature-rich circuit design and simulation tool. This is not only because internally, Gnucap and modular Qucs are very similar, but also because a single project will be easier to maintain, and easier to identify for potential contributors. A project that interfaces with other tools on different levels, more than trying to catch up, will have the potential to bring people together, potentiating the efforts. Historically, contributions have fallen into the cracks between projects, e.g. when authors failed to maintain their version of a program. A modular architecture will allow even incomplete contributions to be interesting to others, without stalling the development.<br />
<br />
==Software==<br />
===General information===<br />
* Repositories: http://git.savannah.gnu.org/cgit/gnucap, https://github.com/Qucs, https://github.com/Qucs/qucs/tree/modular<br />
* Main documentation website: http://www.gnucap.org<br />
* Wikipedia page: https://en.wikipedia.org/wiki/gnucap<br />
* Crowd funding: https://liberapay.com/Gnucap_and_Qucs<br />
<br />
===Roadmap===<br />
* The software (Gnucap) wishes to interface with the following tools: gEDA, KiCAD, NGspice, Qucs (and forks), Xyce etc.<br />
* The project seeks help on: Finalising the merger. Building bridges to (and between) other projects. Establishing substantial funding for further development and VerilogAMS support.</div>Felixhttps://wiki.f-si.org/index.php?title=Merging_Gnucap_and_Qucs_--_The_Why_and_How&diff=2646Merging Gnucap and Qucs -- The Why and How2022-07-08T09:08:16Z<p>Felix: add liberapay</p>
<hr />
<div>* Speaker: Felix Salfelder<br />
* email: felix@salfelder.org<br />
* other information: n/a<br />
<br />
==Abstract==<br />
<br />
Gnucap and Qucs are two complementary projects both created and distributed in the hope that they will be useful. In a nutshell, Gnucap lacks a graphical user interface that Qucs has, and Qucs lacks a developer friendly implementation and extensibility. In this talk I will highlight the individual strengths of these projects, and explain how they relate to other projects such as Ngspice. I will outline how the two prototype implementations, "Gnucsator" and "modular Qucs", target the interoperability between Gnucap, Qucs and beyond.<br />
<br />
Gnucsator provides a simulator emulating Qucsator, the simulator used from within Qucs. It consists of a collection of Gnucap plugins that have been either implemented from scratch or as a wrapper around (unmodified) Qucsator model code. With very little effort, Gnucsator plugins allow the translation of netlists between Qucs and, say, Verilog file formats. More interestingly, simulation of a circuit with models from Gnucap, Qucsator, Spice3f5, NGspice etc. is straightforward.<br />
<br />
The modular Qucs code base has evolved during refactoring Qucs, porting to Qt5, and turning inessential parts into plugins. During this process, the way to replaceable, alternative symbols, component models, simulators and file formats including data file formats has been paved. Some of these have been implemented and are workable, others are easy to add. As of now, the modular Qucs GUI, mainly the schematic editor, has too many bugs. Fortunately, the GUI is not essential for all tasks...<br />
<br />
Merging the Qucs and Gnucap projects is a promising step towards a feature-rich circuit design and simulation tool. This is not only because internally, Gnucap and modular Qucs are very similar, but also because a single project will be easier to maintain, and easier to identify for potential contributors. A project that interfaces with other tools on different levels, more than trying to catch up, will have the potential to bring people together, potentiating the efforts. Historically, contributions have fallen into the cracks between projects, e.g. when authors failed to maintain their version of a program. A modular architecture will allow even incomplete contributions to be interesting to others, without stalling the development.<br />
<br />
==Software==<br />
===General information===<br />
* Repositories: http://git.savannah.gnu.org/cgit/gnucap, https://github.com/Qucs, https://github.com/Qucs/qucs/tree/modular<br />
* Main documentation website: http://www.gnucap.org<br />
* Wikipedia page: https://en.wikipedia.org/wiki/gnucap<br />
* Crowd funding: https://liberapay.com/Gnucap_and_Qucs<br />
<br />
===Roadmap===<br />
* The software (Gnucap) wishes to interface with the following tools: gEDA, KiCAD, NGspice, Qucs (and forks), Xyce etc.<br />
* The project seeks help on: Finalising the merger. Building bridges to (and between) other projects. Establishing substantial funding for further development and VerilogAMS support.</div>Felixhttps://wiki.f-si.org/index.php?title=Merging_Gnucap_and_Qucs_--_The_Why_and_How&diff=2645Merging Gnucap and Qucs -- The Why and How2022-07-08T08:25:04Z<p>Felix: VerilogAMS</p>
<hr />
<div>* Speaker: Felix Salfelder<br />
* email: felix@salfelder.org<br />
* other information: n/a<br />
<br />
==Abstract==<br />
<br />
Gnucap and Qucs are two complementary projects both created and distributed in the hope that they will be useful. In a nutshell, Gnucap lacks a graphical user interface that Qucs has, and Qucs lacks a developer friendly implementation and extensibility. In this talk I will highlight the individual strengths of these projects, and explain how they relate to other projects such as Ngspice. I will outline how the two prototype implementations, "Gnucsator" and "modular Qucs", target the interoperability between Gnucap, Qucs and beyond.<br />
<br />
Gnucsator provides a simulator emulating Qucsator, the simulator used from within Qucs. It consists of a collection of Gnucap plugins that have been either implemented from scratch or as a wrapper around (unmodified) Qucsator model code. With very little effort, Gnucsator plugins allow the translation of netlists between Qucs and, say, Verilog file formats. More interestingly, simulation of a circuit with models from Gnucap, Qucsator, Spice3f5, NGspice etc. is straightforward.<br />
<br />
The modular Qucs code base has evolved during refactoring Qucs, porting to Qt5, and turning inessential parts into plugins. During this process, the way to replaceable, alternative symbols, component models, simulators and file formats including data file formats has been paved. Some of these have been implemented and are workable, others are easy to add. As of now, the modular Qucs GUI, mainly the schematic editor, has too many bugs. Fortunately, the GUI is not essential for all tasks...<br />
<br />
Merging the Qucs and Gnucap projects is a promising step towards a feature-rich circuit design and simulation tool. This is not only because internally, Gnucap and modular Qucs are very similar, but also because a single project will be easier to maintain, and easier to identify for potential contributors. A project that interfaces with other tools on different levels, more than trying to catch up, will have the potential to bring people together, potentiating the efforts. Historically, contributions have fallen into the cracks between projects, e.g. when authors failed to maintain their version of a program. A modular architecture will allow even incomplete contributions to be interesting to others, without stalling the development.<br />
<br />
==Software==<br />
===General information===<br />
* Repositories: http://git.savannah.gnu.org/cgit/gnucap, https://github.com/Qucs, https://github.com/Qucs/qucs/tree/modular<br />
* Main documentation website: http://www.gnucap.org<br />
* Wikipedia page: https://en.wikipedia.org/wiki/gnucap<br />
<br />
===Roadmap===<br />
* The software (Gnucap) wishes to interface with the following tools: gEDA, KiCAD, NGspice, Qucs (and forks), Xyce etc.<br />
* The project seeks help on: Finalising the merger. Building bridges to (and between) other projects. Establishing substantial funding for further development and VerilogAMS support.</div>Felixhttps://wiki.f-si.org/index.php?title=Merging_Gnucap_and_Qucs_--_The_Why_and_How&diff=2621Merging Gnucap and Qucs -- The Why and How2022-07-06T09:06:28Z<p>Felix: add Software section</p>
<hr />
<div>* Speaker: Felix Salfelder<br />
* email: felix@salfelder.org<br />
* other information: n/a<br />
<br />
==Abstract==<br />
<br />
Gnucap and Qucs are two complementary projects both created and distributed in the hope that they will be useful. In a nutshell, Gnucap lacks a graphical user interface that Qucs has, and Qucs lacks a developer friendly implementation and extensibility. In this talk I will highlight the individual strengths of these projects, and explain how they relate to other projects such as Ngspice. I will outline how the two prototype implementations, "Gnucsator" and "modular Qucs", target the interoperability between Gnucap, Qucs and beyond.<br />
<br />
Gnucsator provides a simulator emulating Qucsator, the simulator used from within Qucs. It consists of a collection of Gnucap plugins that have been either implemented from scratch or as a wrapper around (unmodified) Qucsator model code. With very little effort, Gnucsator plugins allow the translation of netlists between Qucs and, say, Verilog file formats. More interestingly, simulation of a circuit with models from Gnucap, Qucsator, Spice3f5, NGspice etc. is straightforward.<br />
<br />
The modular Qucs code base has evolved during refactoring Qucs, porting to Qt5, and turning inessential parts into plugins. During this process, the way to replaceable, alternative symbols, component models, simulators and file formats including data file formats has been paved. Some of these have been implemented and are workable, others are easy to add. As of now, the modular Qucs GUI, mainly the schematic editor, has too many bugs. Fortunately, the GUI is not essential for all tasks...<br />
<br />
Merging the Qucs and Gnucap projects is a promising step towards a feature-rich circuit design and simulation tool. This is not only because internally, Gnucap and modular Qucs are very similar, but also because a single project will be easier to maintain, and easier to identify for potential contributors. A project that interfaces with other tools on different levels, more than trying to catch up, will have the potential to bring people together, potentiating the efforts. Historically, contributions have fallen into the cracks between projects, e.g. when authors failed to maintain their version of a program. A modular architecture will allow even incomplete contributions to be interesting to others, without stalling the development.<br />
<br />
==Software==<br />
===General information===<br />
* Repositories: http://git.savannah.gnu.org/cgit/gnucap, https://github.com/Qucs, https://github.com/Qucs/qucs/tree/modular<br />
* Main documentation website: http://www.gnucap.org<br />
* Wikipedia page: https://en.wikipedia.org/wiki/gnucap<br />
<br />
===Roadmap===<br />
* The software (Gnucap) wishes to interface with the following tools: gEDA, KiCAD, NGspice, Qucs (and forks), Xyce etc.<br />
* The project seeks help on: Finalising the merger. Building bridges to (and between) other projects. Establishing substantial funding for forther development.</div>Felixhttps://wiki.f-si.org/index.php?title=Merging_Gnucap_and_Qucs_--_The_Why_and_How&diff=2620Merging Gnucap and Qucs -- The Why and How2022-07-06T07:01:11Z<p>Felix: add abstract</p>
<hr />
<div>* Speaker: Felix Salfelder<br />
* email: felix@salfelder.org<br />
* other information: n/a<br />
<br />
==Abstract==<br />
<br />
Gnucap and Qucs are two complementary projects both created and distributed in the hope that they will be useful. In a nutshell, Gnucap lacks a graphical user interface that Qucs has, and Qucs lacks a developer friendly implementation and extensibility. In this talk I will highlight the individual strengths of these projects, and explain how they relate to other projects such as Ngspice. I will outline how the two prototype implementations, "Gnucsator" and "modular Qucs", target the interoperability between Gnucap, Qucs and beyond.<br />
<br />
Gnucsator provides a simulator emulating Qucsator, the simulator used from within Qucs. It consists of a collection of Gnucap plugins that have been either implemented from scratch or as a wrapper around (unmodified) Qucsator model code. With very little effort, Gnucsator plugins allow the translation of netlists between Qucs and, say, Verilog file formats. More interestingly, simulation of a circuit with models from Gnucap, Qucsator, Spice3f5, NGspice etc. is straightforward.<br />
<br />
The modular Qucs code base has evolved during refactoring Qucs, porting to Qt5, and turning inessential parts into plugins. During this process, the way to replaceable, alternative symbols, component models, simulators and file formats including data file formats has been paved. Some of these have been implemented and are workable, others are easy to add. As of now, the modular Qucs GUI, mainly the schematic editor, has too many bugs. Fortunately, the GUI is not essential for all tasks...<br />
<br />
Merging the Qucs and Gnucap projects is a promising step towards a feature-rich circuit design and simulation tool. This is not only because internally, Gnucap and modular Qucs are very similar, but also because a single project will be easier to maintain, and easier to identify for potential contributors. A project that interfaces with other tools on different levels, more than trying to catch up, will have the potential to bring people together, potentiating the efforts. Historically, contributions have fallen into the cracks between projects, e.g. when authors failed to maintain their version of a program. A modular architecture will allow even incomplete contributions to be interesting to others, without stalling the development.</div>Felixhttps://wiki.f-si.org/index.php?title=GnuCap:_Progress_and_Opportunities&diff=2008GnuCap: Progress and Opportunities2019-03-15T06:26:47Z<p>Felix: slides added</p>
<hr />
<div>* Speaker(s): Felix Salfelder<br />
* email: first name at last name dot org<br />
* other information: xxx<br />
<br />
==Slides==<br />
[[Media:felix_fsic19.pdf|felix_fsic19.pdf]]<br />
<br />
==Abstract==<br />
Gnucap Python bindings explained. some words about Gnucsator<br />
<br />
==Software==<br />
* more on www.gnucap.org<br />
<br />
===Roadmap===<br />
* The software wishes to interface with any other tools.</div>Felixhttps://wiki.f-si.org/index.php?title=File:Felix_fsic19.pdf&diff=2007File:Felix fsic19.pdf2019-03-15T06:24:44Z<p>Felix: gnucap slides, handout</p>
<hr />
<div>== Summary ==<br />
gnucap slides, handout</div>Felixhttps://wiki.f-si.org/index.php?title=GnuCap:_Progress_and_Opportunities&diff=1776GnuCap: Progress and Opportunities2019-03-02T14:42:13Z<p>Felix: boilerplate</p>
<hr />
<div>* Speaker(s): Felix Salfelder<br />
* email: first name at last name dot org<br />
* other information: xxx<br />
<br />
==Slides==<br />
[[Media:Dummy slide.pdf|Talk_title_name.pdf]] (to upload a file: go to Edit mode, then click on the fourth icon from the left "Embed file" and follow the instructions)<br />
<br />
==Abstract==<br />
Lorem Ipsum<ref>E. Miller, ''The history of Lorem Ipsum'', (New York: Academic Press, 2005), 23-5.</ref> is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.<ref>R. Smith, "Dummy text repositories", ''Scientific American'', 46 (April 1978): 44-6.</ref><br />
<br />
==Software==<br />
===General information===<br />
* Repository: https://xxxx.yyy<br />
* Main documentation website: https://xxxx.yyy<br />
* Wikipedia page: https://en.wikipedia.org/wiki/XXX-YYY-ZZZ (if a wikipedia page about the software, or a page mentioning it, does not exist yet, please consider creating one). If it gets reverted or deleted, please create a page on https://wiki.f-si.org<br />
* Wiki page on wiki.f-si.org: https://wiki.f-si.org/index.php/XXX-YYY-ZZZ<br />
* The software has been used in the following projects: XXX, YYY, ZZZ<br />
<br />
===Roadmap===<br />
* The software wishes to interface with the following tools: XXX, YYY<br />
* The project seeks help on: XXX, YYY</div>Felix