Define qucs dataset9/5/2023 ![]() This is definitely not what we would have intended, and it has been added to the list of bugs in the output system in general, and in the file= handling in particular. It is currently outputting two headers, neither of which actually describes the contents of the file correctly, and is concatenating time-domain and frequency-domain output on every line. print line is not anything like the output we intended, and will certainly be changing as soon as possible. You are using ".print hb file=", an option we have apparently not been testing well. We did not notice this bug until looking at your example, in fact. Your Xyce example is cool, but when I ran it I discovered that your method of processing HB netlists in Xyce is counting on a bug in Xyce output. And the default command line as you have it now could then be Which Qucs could then substitute the number of processors for %p. usr/local/mpi/openmpi/bin/mpirun -np %p /usr/local/Xyce_Parallel/bin/Xyce It does not appear possible to set the Simulate with Spice option to use a command line of that form.Īn improvement to the dialog might be to allow a more flexible way of specifying how to run Xyce in parallel, perhaps allowing a pattern that could be substituted into, e.g.: "/path/to/mpirun -np 2 /path/to/Xyce netlist". In a source-built install, this script (which is admittedly a kludge that we'd like to do away with at some point) is not installed and generally unnecessary, and the user is expected to construct their own mpirun command line, e.g. But xmpirun is generally only present in binary distributions of Xyce, where the xmpirun script is designed to set environment variables to get distributed shared libraries from the Intel compiler suite loaded. The one thing I noticed, however, is the way the "Simulate with Spice" settings work for running Xyce in parallel - they appear to assume that the "xmpirun" script exists for parallel Xyce, and appears simply to tack on "-np # netlist" to that, using the spin box value for number of processors. I haven't had much time to look at it yet, but have cloned the git repo, checked out the rebase_spice4qucs branch, and gotten the thing built on my system. Ngspice variables have ngspice/ prefix, Xyce User needs to select appropriate dataset fromĬhooseSimulator drop-down list. Now three datasets could be createdĭuring simulations scheamtic_name.dat - defaultĭataset from Qucsator schematic_ -įor Ngspice and schematic_ - for Xyce.ĭataset selection list in DiagramDialog shows only theīase name of dataset. ![]() Implemented new datasets naming system (more user-friendly) toĪvoid dataset names conflicts. User error message is shown and further simulation isģ. Transmission lines, etc.), then such schematic cannot be simulated Simulator log redirected to system log.txt. Working directory for temporary simulation data saving could set Added warning label in the top of dialog with There was the following changes (not reflected in the documentation) during last months:ġ. Spice4qucs contains over 280 commits mainly from me and Mike Brinson.Įxamples could be found at examples/ngspice and examples/xyce All contributions inĭocumentation are welcome. Draft documentationĭocumentations is a bit outdated now. Qucs can serve as GUI for Xyce.īuild this branch to look at spice4qucs closer. Spice4qucs allows you to simulate Qucs schematic with Xyce or Ngspice backends. I would like to inform you that Spice4qucs patchset is prepared for merge in upstream Qucs ( ) code after 8 months of development.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |