Differences

This shows you the differences between two versions of the page.

Link to this comparison view

gnucap:about:plugins:interface [2020/02/15 05:20]
felixs created
gnucap:about:plugins:interface [2020/07/17 06:39] (current)
felixs typo, gnucsator
Line 7: Line 7:
 Unlike other simulators, Gnucap is composed of a small shared library with ([[gnucap:manual:tech:plugins]]). The "gnucap" main executable is a simplistic entry point that loads the library and the plugins. It implements batch processing and command based interactive analysis. From here, writing data into files or piping to other (plot/postprocessing) programs is straightforward. The default printed ascii data output format is supposed to be simplistic, gnuplot or gwave can read it, and it is not difficult to parse from your favourite scripting language. (arbitrary output, such as the usual binary formats or shared memory or anything else will be available soon, c.f. [[gnucap:manual:tech:plugins:output]]). Unlike other simulators, Gnucap is composed of a small shared library with ([[gnucap:manual:tech:plugins]]). The "gnucap" main executable is a simplistic entry point that loads the library and the plugins. It implements batch processing and command based interactive analysis. From here, writing data into files or piping to other (plot/postprocessing) programs is straightforward. The default printed ascii data output format is supposed to be simplistic, gnuplot or gwave can read it, and it is not difficult to parse from your favourite scripting language. (arbitrary output, such as the usual binary formats or shared memory or anything else will be available soon, c.f. [[gnucap:manual:tech:plugins:output]]).
  
-Applications may simply skip or replace the main executable, directly use the shared library, and obtain full control over the simulator. known existing exaples (partly work in progress) are [[gnucap:user:gnucap_Python]] and gnucap-custom (c.f. [[gnucap:projects]]). An interface to other software  may involve extensions that provide functionality required by other software. E.g. gnucap-qucs implements (some of) the components and simulation commands that QUCS provides controls for.+Applications may simply skip or replace the main executable, directly use the shared library, and obtain full control over the simulator. Known existing examples (partly work in progress) are [[gnucap:user:gnucap_Python]] and gnucap-custom (c.f. [[gnucap:projects]]). An interface to other software  may involve extensions that provide functionality required by other software. E.g. gnucsator implements (some of) the components, language support and simulation commands that QUCS provides controls for.
  
gnucap/about/plugins/interface.txt · Last modified: 2020/07/17 06:39 by felixs
 
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Run by Debian Driven by DokuWiki