You can subscribe to this list here.
| 2001 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
(83) |
Nov
(57) |
Dec
(111) |
| 2004 |
Jan
(38) |
Feb
(121) |
Mar
(107) |
Apr
(241) |
May
(102) |
Jun
(190) |
Jul
(239) |
Aug
(158) |
Sep
(184) |
Oct
(193) |
Nov
(47) |
Dec
(68) |
| 2005 |
Jan
(190) |
Feb
(105) |
Mar
(99) |
Apr
(65) |
May
(92) |
Jun
(250) |
Jul
(197) |
Aug
(128) |
Sep
(101) |
Oct
(183) |
Nov
(186) |
Dec
(42) |
| 2006 |
Jan
(102) |
Feb
(122) |
Mar
(154) |
Apr
(196) |
May
(181) |
Jun
(281) |
Jul
(310) |
Aug
(198) |
Sep
(145) |
Oct
(188) |
Nov
(134) |
Dec
(90) |
| 2007 |
Jan
(134) |
Feb
(181) |
Mar
(157) |
Apr
(57) |
May
(81) |
Jun
(204) |
Jul
(60) |
Aug
(37) |
Sep
(17) |
Oct
(90) |
Nov
(122) |
Dec
(72) |
| 2008 |
Jan
(130) |
Feb
(108) |
Mar
(160) |
Apr
(38) |
May
(83) |
Jun
(42) |
Jul
(75) |
Aug
(16) |
Sep
(71) |
Oct
(57) |
Nov
(59) |
Dec
(152) |
| 2009 |
Jan
(73) |
Feb
(213) |
Mar
(67) |
Apr
(40) |
May
(46) |
Jun
(82) |
Jul
(73) |
Aug
(57) |
Sep
(108) |
Oct
(36) |
Nov
(153) |
Dec
(77) |
| 2010 |
Jan
(42) |
Feb
(171) |
Mar
(150) |
Apr
(6) |
May
(22) |
Jun
(34) |
Jul
(31) |
Aug
(38) |
Sep
(32) |
Oct
(59) |
Nov
(13) |
Dec
(62) |
| 2011 |
Jan
(114) |
Feb
(139) |
Mar
(126) |
Apr
(51) |
May
(53) |
Jun
(29) |
Jul
(41) |
Aug
(29) |
Sep
(35) |
Oct
(87) |
Nov
(42) |
Dec
(20) |
| 2012 |
Jan
(111) |
Feb
(66) |
Mar
(35) |
Apr
(59) |
May
(71) |
Jun
(32) |
Jul
(11) |
Aug
(48) |
Sep
(60) |
Oct
(87) |
Nov
(16) |
Dec
(38) |
| 2013 |
Jan
(5) |
Feb
(19) |
Mar
(41) |
Apr
(47) |
May
(14) |
Jun
(32) |
Jul
(18) |
Aug
(68) |
Sep
(9) |
Oct
(42) |
Nov
(12) |
Dec
(10) |
| 2014 |
Jan
(14) |
Feb
(139) |
Mar
(137) |
Apr
(66) |
May
(72) |
Jun
(142) |
Jul
(70) |
Aug
(31) |
Sep
(39) |
Oct
(98) |
Nov
(133) |
Dec
(44) |
| 2015 |
Jan
(70) |
Feb
(27) |
Mar
(36) |
Apr
(11) |
May
(15) |
Jun
(70) |
Jul
(30) |
Aug
(63) |
Sep
(18) |
Oct
(15) |
Nov
(42) |
Dec
(29) |
| 2016 |
Jan
(37) |
Feb
(48) |
Mar
(59) |
Apr
(28) |
May
(30) |
Jun
(43) |
Jul
(47) |
Aug
(14) |
Sep
(21) |
Oct
(26) |
Nov
(10) |
Dec
(2) |
| 2017 |
Jan
(26) |
Feb
(27) |
Mar
(44) |
Apr
(11) |
May
(32) |
Jun
(28) |
Jul
(75) |
Aug
(45) |
Sep
(35) |
Oct
(285) |
Nov
(99) |
Dec
(16) |
| 2018 |
Jan
(8) |
Feb
(8) |
Mar
(42) |
Apr
(35) |
May
(23) |
Jun
(12) |
Jul
(16) |
Aug
(11) |
Sep
(8) |
Oct
(16) |
Nov
(5) |
Dec
(8) |
| 2019 |
Jan
(9) |
Feb
(28) |
Mar
(4) |
Apr
(10) |
May
(7) |
Jun
(4) |
Jul
(4) |
Aug
|
Sep
(4) |
Oct
|
Nov
(23) |
Dec
(3) |
| 2020 |
Jan
(19) |
Feb
(3) |
Mar
(22) |
Apr
(17) |
May
(10) |
Jun
(69) |
Jul
(18) |
Aug
(23) |
Sep
(25) |
Oct
(11) |
Nov
(20) |
Dec
(9) |
| 2021 |
Jan
(1) |
Feb
(7) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(8) |
Jul
(6) |
Aug
(8) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(23) |
| 2022 |
Jan
(23) |
Feb
(9) |
Mar
(9) |
Apr
|
May
(8) |
Jun
(1) |
Jul
(6) |
Aug
(8) |
Sep
(30) |
Oct
(5) |
Nov
(4) |
Dec
(6) |
| 2023 |
Jan
(2) |
Feb
(5) |
Mar
(7) |
Apr
(3) |
May
(8) |
Jun
(45) |
Jul
(8) |
Aug
|
Sep
(2) |
Oct
(14) |
Nov
(7) |
Dec
(2) |
| 2024 |
Jan
(4) |
Feb
(4) |
Mar
|
Apr
(7) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
(4) |
Dec
(14) |
| 2025 |
Jan
(22) |
Feb
(6) |
Mar
(5) |
Apr
(14) |
May
(6) |
Jun
(11) |
Jul
(19) |
Aug
|
Sep
(17) |
Oct
(1) |
Nov
(2) |
Dec
(18) |
| 2026 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Theo H. <th...@ph...> - 2007-07-19 13:58:57
|
j1n3l0 wrote: > I did solve my problem. I measured the distances for each margin and found > that there is a ratio system in place. My findings are summarised below: > > ========================================================================= > > coords [x, y] = [ (lmargin + (abs(xmin - x)/xrange * xlength)), (tmargin + > (abs(ymax - y)/yrange * ylength)) ] > > where: > > lmargin is the length in pixels of the left margin > > lmargin = 7 * gnuplot lmargin [...] > tmargin is the length in pixels of the top margin > > tmargin = 11 * gnuplot tmargin I'm glad your were able to solve your problem, but do note that your method will break if you use a different size default font. Margins are specified in terms of characters, and the font you're using happens to report a width of 7 and a height of 11. It'll likely break if you use a different terminal (probably because of a different default font), or if you add a title. Of course, good enough is often good enough :) THeo |
|
From: j1n3l0 <nel...@gm...> - 2007-07-19 10:54:22
|
I did solve my problem. I measured the distances for each margin and found
that there is a ratio system in place. My findings are summarised below:
=========================================================================
coords [x, y] = [ (lmargin + (abs(xmin - x)/xrange * xlength)), (tmargin +
(abs(ymax - y)/yrange * ylength)) ]
where:
lmargin is the length in pixels of the left margin
lmargin = 7 * gnuplot lmargin
xrange is the difference between the max and min x values
xrange = abs(xmax - xmin)
xlength is the length of the x axis in pixels
xlength = image_width - (lmargin + rmargin)
tmargin is the length in pixels of the top margin
tmargin = 11 * gnuplot tmargin
yrange is the difference between the max and min y values
yrange = abs(ymax - ymin)
ylength is the length of the y axis in pixels
ylength = image_height - (tmargin + bmargin)
=========================================================================
>From this I was able to construct a class which generates image maps of
Gnuplots on the fly.
Theo Hopman wrote:
>
> I'm not sure if it completely solves your problem, but new in 4.3 is a
> feature that allows margins to be specified in terms of fractions of the
> screen coordinate system. Since you presumably know the size of your
> terminal's "screen", you can easily find where the borders of the graph
> area are. This method will not work if you need (for whatever reason) to
> have automatically calculated margins.
>
This information will be useful in future. I can substitute my methods for
calculating the margins in pixels accordingly.
--
View this message in context: http://www.nabble.com/Is-there-a-way-of-converting-plot-coords-to-graph-coords--tf1832453.html#a11686342
Sent from the Gnuplot - Dev mailing list archive at Nabble.com.
|
|
From: ronnie_raj <kir...@ba...> - 2007-07-18 15:25:29
|
Hello, I have been developing a GTK application and I am now using GnuPlot to create some graphical output. I was hoping to embed the gnuplot x window results into my GTK application. So far I have been unable to do that can anyone give me any tips on how I would go about this? Thanks, Kiran -- View this message in context: http://www.nabble.com/embedding-gnuplot-x-window-into-gtk-app-tf4103801.html#a11670440 Sent from the Gnuplot - Dev mailing list archive at Nabble.com. |
|
From: MartinOShea <ap...@ds...> - 2007-07-18 10:06:37
|
Hello I have a set of sample data as follows: CEMI (x) ggbs(y) FLOW MM (z) 0.0 90.0 0 6.5 58.7 166 6.6 59.0 169 7.3 65.0 141 6.1 54.5 162 8.5 76.2 217 7.1 64.2 174 6.0 54.2 209 7.0 63.0 198 7.6 68.3 171 which produces a simple set of points on a 3D graph using splot. However, what I would like is to do is to interpolate between points to calculate the coordinates for a flow contour of, for example, 175 mm? Can anyone advise how I might do this? Thanks Martin O'Shea. -- View this message in context: http://www.nabble.com/Contouring-in-GnuPlot-tf4102311.html#a11665821 Sent from the Gnuplot - Dev mailing list archive at Nabble.com. |
|
From: Theo H. <th...@ph...> - 2007-07-17 13:08:15
|
Daantje wrote: > Isn't there any way to show labels for every point in the graph and not show > them on some command or some condition without plotting the entire graph > again??? No. Note that in your previous approach (turning the labels on with a hot key) you were `replot`ting anyway, so it seems to me it's not a big deal to `replot` to turn them off. > What's a smart way to solve this? If your plot is "big" -- by which I assume you mean there is lots of data -- pre-process the data to slim down the data set. Most often, if the (re)plotting is slow, it's because there's more data than is necessary for the resolution of the screen. THeo |
|
From: Daantje <d....@bn...> - 2007-07-17 07:07:16
|
Hans-Bernhard Br=C3=B6ker-2 wrote: >=20 > The only way to get rid of such an addition to the display is issue a=20 > new 'plot' command without it. >=20 Isn't there any way to show labels for every point in the graph and not sho= w them on some command or some condition without plotting the entire graph again??? What's a smart way to solve this? --=20 View this message in context: http://www.nabble.com/GNUPlot-undo-replot-tf4= 087368.html#a11644362 Sent from the Gnuplot - Dev mailing list archive at Nabble.com. |
|
From: <HBB...@t-...> - 2007-07-16 21:25:38
|
Daantje wrote: > I have been trying to figure out how to show and not show an extra graph in a > GNUPlot graph. You rather completely misunderstand the working and intention of 'replot'. > This works fine, the extra graph only shows after pressing the h. But now I > want to be able to get rid of the extra graph preferably by pressing the > same button. I don't want to plot the original graph again since it is > pretty big. Well, that's not going to work. You already plot the original graph again when you did 'replot'. That's what the command does: it REdoes the PLOT, optionally with some more datasets you specify as part of the replot command line. The only way to get rid of such an addition to the display is issue a new 'plot' command without it. |
|
From: Ethan M. <merritt@u.washington.edu> - 2007-07-16 20:54:17
|
On Saturday 14 July 2007 07:15, Hans-Bernhard Br=F6ker wrote:
> Martin Giersich wrote:
>=20
> > And i got rendering problems if i use data-clipping with lines and=20
> > linespoint render mode
> >=20
> > plot 'AGdata-test.dat' using 4:($3=3D=3D1?$5:1/0) with lines,\
> > 'AGdata-test.dat' using 8:($7=3D=3D1?$9:1/0) with lines,\
> > 'AGdata-test.dat' using 12:($11=3D=3D1?$13:1/0) with lines=20
>=20
> Guess you've just found out why 1/0 is not the recommended way of=20
> spelling out "no valid data", in gnuplot. 0/0, which is well and truly=20
> undefined instead of just being infinite, usually works better.
Since you're using the CVS version, you also have the option
of using the symbol NaN ("not a number") directly:
plot 'AGdata-test.dat' using 4:($3=3D=3D1 ? $5 : NaN) with lines
=2D-=20
Ethan A Merritt
|
|
From: Daantje <d....@bn...> - 2007-07-16 14:56:29
|
I have been trying to figure out how to show and not show an extra graph in a GNUPlot graph. So far the show part is working. I plotted the graph and replotted the extra graph with; bind h replot 'velocities.txt' using 2:8:16 with labels center offset 0,0.4 notitle This works fine, the extra graph only shows after pressing the h. But now I want to be able to get rid of the extra graph preferably by pressing the same button. I don't want to plot the original graph again since it is pretty big. I would just like to do an undo replot. The extra graph I want to plot is a graph extisting of a label for each point in the original graph. So all it really does is add labels to each point in the graph. Since the labels block the view to the graph a bit I only want them to display when you you either zoom in to a certain extent or when you press some key like displayed above. But I want them to disappear when you unzoom or press the button again. Does anyone have any ideas on how I could do this? Another way to get the same result would also be welcome. Thanx in advance, Danielle -- View this message in context: http://www.nabble.com/GNUPlot-undo-replot-tf4087368.html#a11617364 Sent from the Gnuplot - Dev mailing list archive at Nabble.com. |
|
From: Petr M. <mi...@ph...> - 2007-07-16 12:57:28
|
> shige 07/14 2007 > ---------------- > In docs/gnuplot.doc of current CVS version Thanks, applied. --- PM |
|
From: Imad_See <I....@se...> - 2007-07-16 10:27:36
|
Dear gunplot developers, I have a data set composed of one X column and 100 Y columns and would like to plot both linear X-Y plot of these data series as well as semilog and log-log. I wonder if that is possible with gunplot? Also, I would like to plot a 3D graph of a similar data series. Thanks for your help, Imad Ahmed .......................................................................................... Imad A. M. Ahmed BSc, MSc, AMRSC, PhD Institute of Geological Sciences (IGS), Environmental Biogeochemistry Research Group, Mailing Address: University of Leeds School of Earth and Environment, Environment Building (Chemistry Building - West Block) Leeds West Yorkshire LS2 9JT United Kingdom Office Phone: +44 (0)113 34 36766 Lab Phone: +44 (0)113 34 36727 Mobile: 07920 474 257 Fax : +44 (0)113 343 6716 E-mail: I....@se... School web page: http://www.see.leeds.ac.uk/people/i.ahmed Personal website: Under Construction |
|
From: Martin G. <mg...@in...> - 2007-07-16 07:46:47
|
On 14.07.2007, at 16:15, Hans-Bernhard Br=C3=B6ker wrote: > Martin Giersich wrote: > >> And i got rendering problems if i use data-clipping with lines and =20= >> linespoint render mode >> plot 'AGdata-test.dat' using 4:($3=3D=3D1?$5:1/0) with lines,\ >> 'AGdata-test.dat' using 8:($7=3D=3D1?$9:1/0) with lines,\ >> 'AGdata-test.dat' using 12:($11=3D=3D1?$13:1/0) with lines > > Guess you've just found out why 1/0 is not the recommended way of =20 > spelling out "no valid data", in gnuplot. 0/0, which is well and =20 > truly undefined instead of just being infinite, usually works better. No change using 0/0. Same broken line drawing. I attached a plot- =20 output of th above plot-command. This rendering problems appear using MacOSX 10.4.... and gnuplot 4.0, =20= 4.2, 4.3. Btw, the official gnuplot-documentation (Thomas Williams & Colin =20 Kelley, "gnuplot - An Interactive Plotting Program", 3 March 2007, =20 available at: http://www.gnuplot.info/docs/gnuplot.pdf) describes at =20 page 25 using "1/0" as a way that "may be used to generate an =20 "undefined" flag, which causes a point to ignored". No other method to do this is refered. If there is another method to do this - besides change of dat-file =20 format - i'd like to know... Regards, Martin ---------------------------------------------------- Dipl.-Inf. Martin Giersich Universit=C3=A4t Rostock IEF - IFI - MMIS www.informatik.uni-rostock.de/mmis Fon: +49-381-498-7514 Fax: +49-381-498-7522 mar...@in... ---------------------------------------------------- =EF=BF=BC |
|
From: <HBB...@t-...> - 2007-07-14 14:34:26
|
Gerald Cox wrote:
> set terminal png transparent xffffff x000000 x404040 x0000ff xa52a2a
> x00ffff x006400 x9400d3 xcd5d5c
> set size 1.5, 0.75
These lines are what causes this effect:
> For some reason only half of the xtic labels are appearing.
... wherein "half the labels" are those within the usual size 1.0 of the
terminal output. You're observing one of the inadvertant side effects
of enlarging an image file output by gnuplot using 'set size' instead of
the 'size' option of 'set terminal'. Replace the above by
set terminal png size 960,360 \
transparent xffffff x000000 x404040 x0000ff xa52a2a \
x00ffff x006400 x9400d3 xcd5d5c
set size 1.0, 1.0
and it'll work again.
|
|
From: <HBB...@t-...> - 2007-07-14 14:19:49
|
Johannes Mueller wrote: > It was mt first time to hack around in gnuplot code. I have to admit, that > I am a little disappointed by the terminal interface as I find it a bit too > lowlevel. But maybe I am just missing something. You're missing the reason why it's so simple: that's what allows to implement it on so many different output formats. Designing an API is an art dominated by trade-offs. It can be too narrow (so it can only be implemented in very few cases), or it can be too broad (making all information carried by it so general as to be meaningless). |
|
From: <HBB...@t-...> - 2007-07-14 14:14:51
|
Martin Giersich wrote: > And i got rendering problems if i use data-clipping with lines and > linespoint render mode > > plot 'AGdata-test.dat' using 4:($3==1?$5:1/0) with lines,\ > 'AGdata-test.dat' using 8:($7==1?$9:1/0) with lines,\ > 'AGdata-test.dat' using 12:($11==1?$13:1/0) with lines Guess you've just found out why 1/0 is not the recommended way of spelling out "no valid data", in gnuplot. 0/0, which is well and truly undefined instead of just being infinite, usually works better. |
|
From: Juergen W. <wie...@fr...> - 2007-07-14 14:08:40
|
Hi, > [TikZ] > > The problem now is, that the terminal is not told about all this stuff. It > is only told to draw lines, texts, points, polygons and stuff. > > What I like to have is access to some struct, which has the information on > the plot, e.g. what the labels are, how the ticks are to be plotted, the > titles of the plots, etc. > > Then I can output the TiKZ code to draw the plot skeleton, i.e. box, axes, > labels, ticks, tick marks, legends and so on. Then just the plots > themselfes should be plotted the way it is implemented now by telling the > terminal to draw simple lines. > > Is there any possibility to archive this? I have thought about this, too. TikZ can do placements much better than gnuplot ever could -- it just has to know about the context of a label. Some time ago, there were rumors about a sophisticated layer concept. Maybe this would even be enough information for TikZ: The next point belongs to a front label, to a plot line, to the border, ... I am not too deeply involved into this, though. Juergen |
|
From: Shigeharu T. <sh...@ie...> - 2007-07-14 09:06:40
|
shige 07/14 2007
----------------
In docs/gnuplot.doc of current CVS version
C RCS $Id: gnuplot.doc,v 1.439 2007/07/11 23:24:36 sfeam Exp $
I found some points that seems to be a misprint and spaces at the
end of some lines. I send the unified diff file for them.
----- From here -----
--- gnuplot.doc~ 2007-07-12 16:27:11.000000000 +0900
+++ gnuplot.doc 2007-07-14 17:58:08.000000000 +0900
@@ -1286,7 +1286,7 @@
#strftime("timeformat",t) & any & string result from applying gnuplot's time parser \\
%strftime("timeformat",t)@any@string result from applying gnuplot's time parser
`strftime("timeformat",t)` applies the timeformat specifiers to the time t
- given in seconds since the year 2000.
+ given in seconds since the year 2000.
See `time_specifiers` and `strptime`.
4 strptime
? expressions functions strptime
@@ -1948,10 +1948,10 @@
commands which will be executed when a certain key or key sequence is pressed
while the driver's window has the input focus. Note that `bind` is only
available if gnuplot was compiled with `mouse` support and it is used by all
- mouse-capable terminals. A user-specified binding supercedes any builtin
+ mouse-capable terminals. A user-specified binding supersedes any builtin
bindings, except that <space> and 'q' cannot normally be rebound. For an
exception, see `bind space`.
-
+
Mouse buttons cannot be rebound.
You get the list of all hotkeys by typing `bind` or by hitting 'h' in the
@@ -2017,7 +2017,7 @@
4 bind space
?commands bind space
?bind space
- By default, the <space> hotkey raises gnuplot's command window. On some
+ By default, the <space> hotkey raises gnuplot's command window. On some
terminals (e.g. x11, wx), 'q' closes the graph window. These defaults can
be changed to ctrl-space and ctrl-q by starting gnuplot as 'gnuplot -ctrlq',
see `x11 command-line-options`, or by the X Resource 'gnuplot*ctrlq'.
@@ -2431,12 +2431,12 @@
The `boxerrorbars` style is only relevant to 2D data plotting. It is a
combination of the `boxes` and `yerrorbars` styles. It uses 3, 4, or 5
columns of data:
-
+
3 columns: x y ydelta
4 columns: x y ydelta xdelta # boxwidth != -2
4 columns: x y ylow yhigh # boxwidth == -2
5 columns: x y ylow yhigh xdelta
-
+
The boxwidth will come from the fourth column if the y errors are given as
"ydelta" and the boxwidth was not previously set to -2.0 (`set boxwidth -2.0`)
or from the fifth column if the y errors are in the form of "ylow yhigh". The
@@ -2462,9 +2462,9 @@
about the given x coordinate that extends from the x axis (not from the graph
border) to the given y coordinate. It uses 2 or 3 columns of basic data.
Additional input columns may be used to provide information such as
- variable line or fill color (see `rgbcolor variable`).
-
- 2 columns: x y
+ variable line or fill color (see `rgbcolor variable`).
+
+ 2 columns: x y
3 columns: x y x_width
The width of the box is obtained in one of three ways. If the input data has a
@@ -2523,11 +2523,11 @@
to the `xyerrorbars` style except that it draws rectangular areas rather than
simple crosses. It uses either 4 or 6 basic columns of input data.
Additional input columns may be used to provide information such as
- variable line or fill color (see `rgbcolor variable`).
-
+ variable line or fill color (see `rgbcolor variable`).
+
4 columns: x y xdelta ydelta
6 columns: x y xlow xhigh ylow yhigh
-
+
The box width and height are determined from the x and y errors in the same
way as they are for the `xyerrorbars` style---either from xlow to xhigh and
from ylow to yhigh, or from x-xdelta to x+xdelta and from y-ydelta to
@@ -2549,9 +2549,9 @@
vertical line segment at the x coordinate extends up from the top of the
rectangle to the high price and another down to the low. The vertical line
will be unchanged if the low and high prices are interchanged.
-
+
Five columns of basic data are required:
-
+
financial data: date open low high close
whisker plot: x box_min whisker_min whisker_high box_high
@@ -2601,7 +2601,7 @@
1 column y # x is taken from row number
2 columns: x y
3 columns: x y z # 3D only (splot)
-
+
For some terminals (post, pdf) the size of the dot can be controlled by
changing the linewidth.
2 filledcurves
@@ -2673,7 +2673,7 @@
?financebars
The `financebars` style is only relevant for 2D data plotting of financial
data. It requires 1 x coordinate (usually a date) and 4 y values (prices).
-
+
5 columns: date open low high close
The symbol is a vertical line segment, located horizontally at the x
@@ -2872,7 +2872,7 @@
For example, to create stacked histograms of the data in columns 3 through 8
set style histogram columnstacked
- plot for [i=3:8] "datafile" using i title columnhead
+ plot for [i=3:8] "datafile" using i title columnhead
2 image
?commands set style image
?set style image
@@ -2889,10 +2889,10 @@
(gray value) for indexing in the current palette.
Each pixel (data point) of the input 2D image will become a rectangle or
- parallelipiped in theplot. The coordinate of each data point will determine
- the center of the parallelipiped. That is, an M x N set of data will form an
+ parallelepiped in the plot. The coordinate of each data point will determine
+ the center of the parallelepiped. That is, an M x N set of data will form an
image with M x N pixels. This is slightly different than pm3d elements where
- an M x N set of data will form a surface of (M-1) x (N-1) elements. The scanu
+ an M x N set of data will form a surface of (M-1) x (N-1) elements. The scan
directions for the image data grid can be any of eight possible combinations.
See also `rgbimage`.
@@ -2909,7 +2909,7 @@
This optimized code may be disabled by using the keyword `failsafe`. E.g.
plot 'data' with image failsafe
-
+
Here are some specific comments about particular terminal drivers:
x11 and wxt - Pixels are either repeated or decimated to fit the display
@@ -2943,7 +2943,7 @@
The `labels` style reads coordinates and text from a data file and places
the text string at the corresponding 2D or 3D position. 3 or 4 input columns
of basic data are required. Additional input columns may be used to provide
- information such as variable text color (see `rgbcolor variable`).
+ information such as variable text color (see `rgbcolor variable`).
3 columns: x y string # 2D version
4 columns: x y z string # 3D version
@@ -2971,7 +2971,7 @@
It may be used in either 2D or 3D plots. The basic form requires 1, 2, or 3
columns of input data.
Additional input columns may be used to provide information such as
- variable line color (see `rgbcolor variable`).
+ variable line color (see `rgbcolor variable`).
2D form
1 column: y # implicit x value from row number
@@ -3010,7 +3010,7 @@
pointsize` may be used to change the default size of the points.
1 or 2 columns of basic input data are required in 2D plots; 1 or 3 columns are
required if 3D plots. See `style lines`. Additional input columns may be used
- to provide information such as variable point size or line color.
+ to provide information such as variable point size or color.
2 steps
?commands set style steps
?set style steps
@@ -4351,7 +4351,7 @@
Sometimes the scanning directions in a binary datafile are not consistent with
that assumed by gnuplot. These keywords can flip the scanning direction along
dimensions x, y, z.
-6 origin
+6 origin
?binary general keywords origin
When gnuplot generates coordinates based upon transposition and flip, it
attempts to always position the lower left point in the array at the origin,
@@ -4686,8 +4686,8 @@
plot 'filename' using 1:2, '' using 1:3
- The special filename '+' is a mechanism to allow the full range of
- `using` specifiers and plot styles with in-line functions. Normally a
+ The special filename '+' is a mechanism to allow the full range of
+ `using` specifiers and plot styles with in-line functions. Normally a
function plot can only have a single y (or z) value associated with each
sampled point. The pseudo-file '+' treats the sampled points as columns
1 (plot) or 1 and 2 (splot), and allows additional column values to be
@@ -7348,7 +7348,7 @@
Justification of the plot titles within the key is controlled by `Left` or
`Right` (default). The text and sample can be reversed (`reverse`) and a
box can be drawn around the key (`box {...}`) in a specified `linetype`
- and `linewidth`, or a user-defined `linestyle`.
+ and `linewidth`, or a user-defined `linestyle`.
By default the first plot label is at the top of the key and successive labels
are entered below it. The `invert` option causes the first label to be placed
@@ -7498,7 +7498,7 @@
same color and fill properties as used in the plot itself. The font and
textcolor properties control the appearance of the individual plot titles
that appear in the key. Setting the textcolor to "rgb variable" causes
- the text for each key entry to be the same color as the line or fill
+ the text for each key entry to be the same color as the line or fill
color for that plot. This was the default in some earlier versions of
gnuplot.
@@ -10859,7 +10859,7 @@
x2 and y2 secondary axes provided by `plot`.
See `plot` for features common to the `plot` command; only differences are
- discussed in detail here.
+ discussed in detail here.
Syntax:
splot {<ranges>}
----- To here -----
+========================================================+
Shigeharu TAKENO NIigata Institute of Technology
kashiwazaki,Niigata 945-1195 JAPAN
sh...@ie... TEL(&FAX): +81-257-22-8161
+========================================================+
|
|
From: Theo H. <th...@ph...> - 2007-07-14 00:35:03
|
j1n3l0 wrote:
>
> Hans-Bernhard Bröker wrote:
>> Ethan Merritt wrote:
>>> Do we have a utility routine somewhere that would convert
>>> plot coordinates to graph or screen coordinates?
>> No. axis.h:AXIS_MAP() and AXIS_MAPBACK transform from data
>> ('first'/'second') coordinates to terminal coordinates and back.
>> Going from terminal to 'screen' is trivial (just divide by term->xmax).
>> Transforming to 'graph' from data coordinates is quite easy: it's a
>> direct linear transformation using the axis_array[].min and .max
>> values.
>>
>
> This thread is over a year old but I am in need of a solution. I am trying
> to get the screen coordinates from my graph coordinates so I can generate an
> image map of my plots.
>
> Is there a way to find out the values of {l|t|b|r}margins in pixels?
> Currently the best I can do is use the "show margin" command, which just
> tells me that the values are computed automatically, not what the values
> are. If I knew the absolute values of these (in pixels) I could find the
> coordinates of each point on my graph.
>
> I think this would go some way to helping me solve my problem.
I'm not sure if it completely solves your problem, but new in 4.3 is a
feature that allows margins to be specified in terms of fractions of the
screen coordinate system. Since you presumably know the size of your
terminal's "screen", you can easily find where the borders of the graph
area are. This method will not work if you need (for whatever reason) to
have automatically calculated margins.
THeo
|
|
From: Petr M. <mi...@ph...> - 2007-07-13 21:44:05
|
> I have three column data which I wish to plot. The first two columns refer to > the in plane grid positions and the third is the height. I wish to plot a > density map. I am unable to do this. I can plot a continulous function and > the density map, however I am unanble to get this working for the data file. > Any advice?? Now the three dimensional map works, but when I try pm3d map, I > get nothing. Is there any advice that you can suggest or some examples > scripts. My data is listed as follows: > > 0 0 1.5 > 0 1 1.6 > 0 2 1.9 > n m X There must be a separator. Add a blank line in between scans (where your "n" is changing). See also gnuplot FAQ "3.10 Pm3d splot from a datafile does not draw anything". --- PM |
|
From: Gerald C. <je...@av...> - 2007-07-13 15:36:49
|
My computer: Redhat 9 2.4.34 kernel Haven't updated any libraries, so the libraries are whatever version came with RedHat 9 *********************************************************************************************** Tiny example of data used: 20070712000004 2007-Jul-12 00:00:04 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000008 2007-Jul-12 00:00:08 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000011 2007-Jul-12 00:00:11 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000014 2007-Jul-12 00:00:14 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000017 2007-Jul-12 00:00:17 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000022 2007-Jul-12 00:00:22 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000028 2007-Jul-12 00:00:28 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000032 2007-Jul-12 00:00:32 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000035 2007-Jul-12 00:00:35 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000039 2007-Jul-12 00:00:39 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000042 2007-Jul-12 00:00:42 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000047 2007-Jul-12 00:00:47 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000053 2007-Jul-12 00:00:53 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000056 2007-Jul-12 00:00:56 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000103 2007-Jul-12 00:01:03 74.3 69.6 60.9 60 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000108 2007-Jul-12 00:01:08 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000112 2007-Jul-12 00:01:12 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000115 2007-Jul-12 00:01:15 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000125 2007-Jul-12 00:01:25 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000128 2007-Jul-12 00:01:28 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000133 2007-Jul-12 00:01:33 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy 20070712000135 2007-Jul-12 00:01:35 74.3 69.6 60.9 61 74 0.0 315.0 NW 69.6 0.05 0.05 0.72 Falling Cloudy *********************************************************************************************** gnuplot.dem file: set key outside horizontal left; set xdata time; set x2data time set timefmt "%Y%m%d%H%M%S"; set terminal png transparent xffffff x000000 x404040 x0000ff xa52a2a x00ffff x006400 x9400d3 xcd5d5c set size 1.5, 0.75 set output "temperature.png" set xlabel "Time" set ylabel "Degrees F & %RH" set xtics rotate set mxtics 5 plot "weather.TEMP" using 1:4 title "Inside Temp" with lines ,"weather.TEMP" using 1:5 title "Outside Temp" with lines, "weather.TEMP" using 1:12 title "Wind Chill" with lines, "weather.TEMP" using 1:7 title "Inside RH" with lines, "weather.TEMP" using 1:8 title "Outside RH" with lines, "weather.TEMP" using 1:6 title "Dew Point" with lines; set output "windspeed.png" set xlabel "Time" set ylabel "MPH" plot "weather.TEMP" using 1:9 title "Wind Speed" with lines reset *********************************************************************************************************** Attached is the image that I'm getting. For some reason only half of the xtic labels are appearing. Thanx guys!!! G |
|
From: Jeremy C. <jer...@gm...> - 2007-07-13 14:29:17
|
On 7/12/07, Ethan Merritt <merritt@u.washington.edu> wrote: > > On Thursday 12 July 2007 13:04, Thomas Treichl <Tho...@gm...> wrote: > > Dear Ethan, > > > > I don't know if I sent this email to the right mailing-list that's why I once > > again send this email directly to you as a Gnuplot maintainer... > > Thanks. I will forward your mail to the developers mailing list. > > There are several issues on which the octave and gnuplot projects should > coordinate better. I am neither an Octave nor a Mac user, so I may not > fully understand all the details, but here is how I understand it... > > 1) I am told that Octave now pipes in-line data to gnuplot, which has > broken the ability to zoom with the mouse and also some or all of the > normal hot-keys. There are 2 competing proposals for how we could fix > this, but it might help if we knew better what additional changes > might or might not be possible on the Octave end of the pipe. > And of course it would have been nice to have more advance warning > of this change, so that we might have had a fix all ready to go. > > 2) I have been relying on several developers with Mac experience to > provide an OSX binary package. As I understand it, this has been > held up by difficulties with creating a universal binary, and by > problems with mouse focus. I honestly do not understand your summary > of Mac issues which you have now solved. Are these the same? > Or maybe those only had to do with inclusion of the wxt terminal? > > 3) Aquaterm is somewhat of a separate issue. Basically it does not > implement the full feature set provided by other gnuplot interactive > terminals. I'm sure this could be fixed, but I don't think anyone is > currently working on it. I recently borrowed a Mac and a local OSX > fanatic to walk me through use of gnuplot under OSX, and my conclusion > was that use of aquaterm came in a poor second to using the x11 terminal. > So I would hope that your binary supports x11 also? > > Anyhow, I think we would be happy to place working Mac binaries on > the SourceForge site. But I'd like some of the Mac-based developers > to chime in with comments > > Ethan I'm not a Mac-based developer, but I use Gnuplot daily on my Mac. I use AquaTerm because I don't like how X11 looks/acts on my Mac; it isn't very Mac-like which is very important to Mac users. I don't use the mouse with Gnuplot (maybe I would if it worked in AquaTerm) so those extra features are not a big loss to me. If the features missing from AquaTerm were included/fixed, all the better. I would be happy to test any Gnuplot.app binary available. Unfortunately, I'm not don't program for the Mac so I couldn't fix the bugs. I would be happy to try it out. For general Mac users, I suspect a self contained Gnuplot.app is a wonderful idea. Being able to install/uninstall Gnuplot just like any other app is a welcome feature. Thanks for the great work. Jeremy Conlin |
|
From: Ethan M. <merritt@u.washington.edu> - 2007-07-12 20:49:15
|
On Thursday 12 July 2007 13:04, wrote: > Dear Ethan, > > I don't know if I sent this email to the right mailing-list that's why I once > again send this email directly to you as a Gnuplot maintainer... Thanks. I will forward your mail to the developers mailing list. There are several issues on which the octave and gnuplot projects should coordinate better. I am neither an Octave nor a Mac user, so I may not fully understand all the details, but here is how I understand it... 1) I am told that Octave now pipes in-line data to gnuplot, which has broken the ability to zoom with the mouse and also some or all of the normal hot-keys. There are 2 competing proposals for how we could fix this, but it might help if we knew better what additional changes might or might not be possible on the Octave end of the pipe. And of course it would have been nice to have more advance warning of this change, so that we might have had a fix all ready to go. 2) I have been relying on several developers with Mac experience to provide an OSX binary package. As I understand it, this has been held up by difficulties with creating a universal binary, and by problems with mouse focus. I honestly do not understand your summary of Mac issues which you have now solved. Are these the same? Or maybe those only had to do with inclusion of the wxt terminal? 3) Aquaterm is somewhat of a separate issue. Basically it does not implement the full feature set provided by other gnuplot interactive terminals. I'm sure this could be fixed, but I don't think anyone is currently working on it. I recently borrowed a Mac and a local OSX fanatic to walk me through use of gnuplot under OSX, and my conclusion was that use of aquaterm came in a poor second to using the x11 terminal. So I would hope that your binary supports x11 also? Anyhow, I think we would be happy to place working Mac binaries on the SourceForge site. But I'd like some of the Mac-based developers to chime in with comments > Also all other > emails that I send to > > mailto:lhe...@us... > mailto:sf...@us... > > returned to me with an "undisclosed recipients" message. Strange. I get other mail through that address, but I have not seen any mail from you. Could you please send a complaint to the SourceForge organization itself? It must be something broken in their mailing-list software. -- Ethan A Merritt |
|
From: Ethan M. <merritt@u.washington.edu> - 2007-07-12 20:49:11
|
On Thursday 12 July 2007 13:04, Thomas Treichl <Tho...@gm...> wrote: > Dear Ethan, > > I don't know if I sent this email to the right mailing-list that's why I once > again send this email directly to you as a Gnuplot maintainer... Thanks. I will forward your mail to the developers mailing list. There are several issues on which the octave and gnuplot projects should coordinate better. I am neither an Octave nor a Mac user, so I may not fully understand all the details, but here is how I understand it... 1) I am told that Octave now pipes in-line data to gnuplot, which has broken the ability to zoom with the mouse and also some or all of the normal hot-keys. There are 2 competing proposals for how we could fix this, but it might help if we knew better what additional changes might or might not be possible on the Octave end of the pipe. And of course it would have been nice to have more advance warning of this change, so that we might have had a fix all ready to go. 2) I have been relying on several developers with Mac experience to provide an OSX binary package. As I understand it, this has been held up by difficulties with creating a universal binary, and by problems with mouse focus. I honestly do not understand your summary of Mac issues which you have now solved. Are these the same? Or maybe those only had to do with inclusion of the wxt terminal? 3) Aquaterm is somewhat of a separate issue. Basically it does not implement the full feature set provided by other gnuplot interactive terminals. I'm sure this could be fixed, but I don't think anyone is currently working on it. I recently borrowed a Mac and a local OSX fanatic to walk me through use of gnuplot under OSX, and my conclusion was that use of aquaterm came in a poor second to using the x11 terminal. So I would hope that your binary supports x11 also? Anyhow, I think we would be happy to place working Mac binaries on the SourceForge site. But I'd like some of the Mac-based developers to chime in with comments Ethan On Thursday 12 July 2007 13:46, Ethan Merritt wrote: > Forwarding this from Thomas Treichl <Tho...@gm...> > > Dear Gnuplot maintainers, > > we have created Octave.app for PPC 10.3 and i386 10.4 Mac users that can be > downloaded at > http://sourceforge.net/project/showfiles.php?group_id=2888. One of the last > things that need to be done for Octave.app is to make a ready-to-run binary > release of gnuplot available that can then be taken as the background plotting > engine. That's why we quickly have decided to create another Mac application > that can be set up as easy as Octave.app but is not bundled with Octave.app and > that we call this time: Gnuplot.app. > > We nearly have finished building Gnuplot.app PPC and Gnuplot.app i386 with > gnuplot version 4.2 including most features like gdlib, jpg and png (but not > wxWindows because of a size-explosion of the *.dmg image and no pdf-support > because of a missing GPL-compatiple license). We didn't create a universal > binary Gnuplot.app because we don't see a real advantage of universal binaries > for Mac (we already have gone through this whole discussion about universal > binaries or two binaries of Octave.app at one of the mailing lists at octave.org > months ago). > > For building either the PPC version or i386 version of Gnuplot.app we have > created a single shell script - it's not very nice but very powerful if we have > a look at the Gnuplot.app result that comes out (and there are also some other > external files that are needed, eg. a 128x128bit gnuplot.icns file, the > .DS_Store file and the corresponding background image...). Some very important > Mac-features of Gnuplot.app (like the ones of Octave.app) are: > > - there is no easier way of installation (drag'n drop somewhere) > - and no easier way of deinstallation (drag'n drop into trash) > - it's bundled, no other dependency must be installed (AquaTerm inclusion) > - gnuplot can also be called from the command line of Terminal.app or xterm > > The inclusion of AquaTerm into Gnuplot.app has taken a while but we were able to > set it up very nice ;) The user must not install any AquaTerm.pkg anymore, the > necessary AquaTerm.framework is included into Gnuplot.app directly and it is > started automatically if the user plots something the first time to the AquaTerm > backend. There is one problem left ie. that we are not able to compile AquaTerm > "not universal", ie. whatever PPC *or* i386 is set in the projects preferences > in this XCode program of the AquaTerm.project it is not taken for compilation. > It always creates a universal binary (that's not good because SDK 10.4.9u then > must be taken and so we can't create a 10.3 PPC version like we did for > Octave.app PPC). The manual of XCode says: change compiler option ARCH and SDK > in the preferences dialog and you're done ;( If it would be that easy... > > Maybe my email hits you like a hammer (I don't hope so) but I wanted to get into > contact with you in a very early stage because you also might have a thousand > questions that need to be answered and I'm also interested in your further > requirements for an official release. And I'd also like to address our interests > that would be that the PPC and the i386 Gnuplot.app could be hosted on your side > of sourceforge.net (because octave.sourceforge.net would not be the right place) > and that somebody could continue working on this topic for future releases of a > Gnuplot.app that understands much more about gnuplot in general than we do. The > problem is that the one or the other might have a special gnuplot-depending > question and I don't know if we do have the knowledge and the time to answer > specific internals... > > The build scripts need some more clean-up but I think that I'm able to send it > in a few days (whom? or where?). I can also prepare a PPC *dmg and a i386 *.dmg > for very early alpha-tests (<5MB each *.dmg). Please also reply any comments and > questions directly because I'm not a subscriber to any of your lists. I think > hosting a Gnuplot.app would also be of your interest as there doesn't exist one > at your download site for 4.2 at the moment and so I hope that we can find > together soon... > > Thomas > > -- Ethan A Merritt Courier Deliveries: 1959 NE Pacific Dept of Biochemistry Health Sciences Building University of Washington - Seattle WA 98195-7742 |
|
From: Ethan M. <merritt@u.washington.edu> - 2007-07-12 20:46:32
|
Forwarding this from Thomas Treichl <Tho...@gm...> Dear Gnuplot maintainers, we have created Octave.app for PPC 10.3 and i386 10.4 Mac users that can be downloaded at http://sourceforge.net/project/showfiles.php?group_id=2888. One of the last things that need to be done for Octave.app is to make a ready-to-run binary release of gnuplot available that can then be taken as the background plotting engine. That's why we quickly have decided to create another Mac application that can be set up as easy as Octave.app but is not bundled with Octave.app and that we call this time: Gnuplot.app. We nearly have finished building Gnuplot.app PPC and Gnuplot.app i386 with gnuplot version 4.2 including most features like gdlib, jpg and png (but not wxWindows because of a size-explosion of the *.dmg image and no pdf-support because of a missing GPL-compatiple license). We didn't create a universal binary Gnuplot.app because we don't see a real advantage of universal binaries for Mac (we already have gone through this whole discussion about universal binaries or two binaries of Octave.app at one of the mailing lists at octave.org months ago). For building either the PPC version or i386 version of Gnuplot.app we have created a single shell script - it's not very nice but very powerful if we have a look at the Gnuplot.app result that comes out (and there are also some other external files that are needed, eg. a 128x128bit gnuplot.icns file, the .DS_Store file and the corresponding background image...). Some very important Mac-features of Gnuplot.app (like the ones of Octave.app) are: - there is no easier way of installation (drag'n drop somewhere) - and no easier way of deinstallation (drag'n drop into trash) - it's bundled, no other dependency must be installed (AquaTerm inclusion) - gnuplot can also be called from the command line of Terminal.app or xterm The inclusion of AquaTerm into Gnuplot.app has taken a while but we were able to set it up very nice ;) The user must not install any AquaTerm.pkg anymore, the necessary AquaTerm.framework is included into Gnuplot.app directly and it is started automatically if the user plots something the first time to the AquaTerm backend. There is one problem left ie. that we are not able to compile AquaTerm "not universal", ie. whatever PPC *or* i386 is set in the projects preferences in this XCode program of the AquaTerm.project it is not taken for compilation. It always creates a universal binary (that's not good because SDK 10.4.9u then must be taken and so we can't create a 10.3 PPC version like we did for Octave.app PPC). The manual of XCode says: change compiler option ARCH and SDK in the preferences dialog and you're done ;( If it would be that easy... Maybe my email hits you like a hammer (I don't hope so) but I wanted to get into contact with you in a very early stage because you also might have a thousand questions that need to be answered and I'm also interested in your further requirements for an official release. And I'd also like to address our interests that would be that the PPC and the i386 Gnuplot.app could be hosted on your side of sourceforge.net (because octave.sourceforge.net would not be the right place) and that somebody could continue working on this topic for future releases of a Gnuplot.app that understands much more about gnuplot in general than we do. The problem is that the one or the other might have a special gnuplot-depending question and I don't know if we do have the knowledge and the time to answer specific internals... The build scripts need some more clean-up but I think that I'm able to send it in a few days (whom? or where?). I can also prepare a PPC *dmg and a i386 *.dmg for very early alpha-tests (<5MB each *.dmg). Please also reply any comments and questions directly because I'm not a subscriber to any of your lists. I think hosting a Gnuplot.app would also be of your interest as there doesn't exist one at your download site for 4.2 at the moment and so I hope that we can find together soon... Thomas -- Ethan A Merritt |
|
From: disruptivetechnology <bre...@go...> - 2007-07-12 20:14:13
|
I have three column data which I wish to plot. The first two columns refer to the in plane grid positions and the third is the height. I wish to plot a density map. I am unable to do this. I can plot a continulous function and the density map, however I am unanble to get this working for the data file. Any advice?? Now the three dimensional map works, but when I try pm3d map, I get nothing. Is there any advice that you can suggest or some examples scripts. My data is listed as follows: 0 0 1.5 0 1 1.6 0 2 1.9 n m X Many thanks -- View this message in context: http://www.nabble.com/Plotting-Density-profile-from-datafile-tf4070525.html#a11567859 Sent from the Gnuplot - Dev mailing list archive at Nabble.com. |