From: roucaries b. <rou...@gm...> - 2013-07-07 21:30:25
|
On Sat, Jul 6, 2013 at 8:31 PM, Guilherme Brondani Torri <gui...@gm...> wrote: > On 06/07/13 18:05, Richard Crozier wrote: >> >> >> Guilherme Brondani Torri <gui...@gm...> wrote: >> >> On 05/07/13 10:23, Richard Crozier wrote: >> >> On 05/07/2013 08:10, Raghunandan Mudadla wrote: >> >> Hello I am Raghunandan. I am working on a Qucs plugin for >> gnucap I am presently looking at the .sch files uploaded >> at the website but al told me that Qucs uses another >> format to drive the simulator can u please tell me the >> details. Thank You. >> >> Hi Raghunandan, You should CC the qucs and gnucap developers >> mailing lists (you will need to sign up for the mailing list >> here: https://lists.sourceforge.net/lists/listinfo/qucs-devel >> ) so you don't depend on just me to answer any questions. Yes, >> the .sch files which are edited by the GUI are converted to >> Qucs netlists. The simulation backend, called qucsator, takes >> these netlists as input. You can find some examples of the >> Qucs netlist format in the pdf here: >> http://qucs.sourceforge.net/docs/spicetoqucs.pdf The following >> may also have some useful information: >> http://qucs.sourceforge.net/docs/equations.pdf Someone also >> wrote a python program to convert .sch to the netlist format, >> but I haven't tried it see: >> https://sourceforge.net/p/qucs/feature-requests/21/ and >> possibly this (I don't know if it is the same thing) >> https://github.com/zonca/python-qucs Unfortunately there is >> not at present an easy way to convert a schematic into a >> netlist for viewing. The only way to do this currently is to >> run a simulation, then view the last netlist created. I am >> currently working on an option to do this, but will take a >> while. Regards, Richard >> >> >> Hello, >> >> I pushed a new branch 'command-line'. >> It adds to Qucs a very simple command line parser that implements the >> desired schematic to netlist conversion. >> >> You can use it from the command line as follows: >> $qucs --netlist --i=input_schematic.sch --o=output_netlist.txt >> >> I tested on a handful of schematics I had around. It generates exactly >> the same netlist created prior to simulation. >> I haven't tested it extensively th! >> ou. I >> don't have any schematic >> involving Spice for instance. >> The GUI also seems to not be affected by any new bugs. >> >> This is just a proof of concept, ideas about a proper parser, argument >> handling, and actual implementation are all open to discussion... >> >> Please have a look at it and I'm looking forward to hear you ideas. >> >> Best regards, >> Guilherme >> >> >> Hi Guilherme, >> >> This looks good, the approach i was taking was to reuse the logic for >> running a simulation, just allowing the user to choose the file name, >> and stopping after the netlist was generated. I was adding a function >> to simmessage to do this. Is it still worth doing this? >> >> Richard >> > Hi Richard, > > I first thought of adding a menu option to 'create netlist only', which > I think is still worth to do. Currently you can only open the last > netlist after running/failing the simulation. Another point, I believe > the netlist and the log files should belong to the project directory, > not to the ~/.qucs working directory as it is now. > > Instead I went for the command line. I tried to keep changes to a > minimum. I also reused the relevant methods and tried to skip things > that are only relevant for the GUI. If you think about automated testing > or some sort of model optimization, it makes sense to have the schematic > to netlist conversion from the command line. Down the line it could be > used on a tool to benchmark or sign off releases and changes to the core. > > Perhaps we could even pull the 'netlister' out of the GUI. Anyways, the > concept of accessing the GUI from the command line would still be nice > in some cases. For instance one could think or dumping the schematic as > a pdf, png, or even dumping particular diagrams to pdf with the updated > data from simulation. All from the command line. Is that worth the > trouble? Maybe, one could think of report generation out of a list of > schematics. That sounds appealing to me. Some time ago I have written an attempt to do this by the gui saving in true xml file and transform to netlist using xslt. It is quite easy and push the burden of parsing/optimizing to external library. The only thing that is laking is documentation of qucs-core input, and onverting output of qucs gui to true xml > > I hope to hear what others have to say on this regard. > Best, > Guilherme > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > Qucs-devel mailing list > Quc...@li... > https://lists.sourceforge.net/lists/listinfo/qucs-devel |