On Sun, 17 Apr 2005, Greg Lauer wrote:
> Steve,
>
> The fink gtk16-gtk package has been updated in CVS, so that
> whole dependeny issue has been resolved. I'm in the process
> of writing a fink package for gwave, and I get the following
> error when I try and compile (I was getting this outside of fink too):
>
> Making all in scheme
> ../utilities/guile-doc-snarf --lang scheme cmds.scm > cmds.doc
>
> ;;; WARNING (no code for module (ice-9 rdelim))
> ERROR: unrecognized defmodule argument (:export (doc-snarf))
> make[2]: *** [cmds.doc] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
I think the problem here is that doc-snarf (which I borrowed intact
from the guile source) does the same path-searching trick as
build-guile-gtk, and expects the first guile in $PATH to be the right
version.
> However, when I 'make install' after this, it seems to build
> the remaining starting from 'Making install in doc' just
> fine and gwave seem to run ok.
The doc directory is (supposed to be) shipped in the tarball with
everything pre-built, since the tools for reconstructing things are a bit
fragile, as you found out. So unless things got deleted, dates munged, or
you're modifying the code, the doc directory make shouldn't have to
rebuild much.
> As far as plotting db plots, the node I'm trying to plot
> shows in gwave, but no db option for the node, only plots voltage. I guess
> ngspice does not write db to raw format. Maybe someone on this
> list knows? Does anyone know how to write voltage magnitude (in db)
> and voltage phase data to raw format?
I built ngspice and played around with it a bit. I can't find any way to
get it to do that either, just the unhelpful
.print line ignored since rawfile was produced.
message.
The commercial spices and gnucap all use the .print or .probe lines to
control and/or suplement what goes into the datafile.
This deficiency in spice3/ngspice is almost anoying enough for me to dive
in and enhance it. Someday...
Gwave's philosophy so far is to plot what's in the datafile only,
although waveform calculations are on the wishlist. Gwave is lacking the
ability to display the imaginary component of complex variables.
I do see how to do a quick enhancement to add that.
> Finally, as far as plotting goes. With gnugraph I get an incomplete
> plot (no x and y labels etc). gnuplot with the patch is still finicky,
> sometime it works, sometimes it hangs, and sometime I get:
> gnuplot> plot
> ^
> "gwplot.dat.gnuplot", line 12: function to plot expected
>
> Maybe I didn't apply the patch correctly, I'll double check.
Urm, the patch was for gnu graph (from plotutils) not gnuplot. Yes,
those two program names are almost as confusing as gwave vs. gtkwave :-)
But maybe there's gnuplot version drift or (more likely) a gwave bug.
To debug plot-export troubles, check the "keep tempfiles" box, and
try examining and running the plot script from the command line.
If you can capture a small waveform file, ".gw" saved state, and a bad
plot script or plot settings that reliably cause a failing plot script
that you are able to email me, I'll try chase down the bugs.
> Thanks again for you help!
> Greg
Steve
