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}
(31) 
_{May}

_{Jun}

_{Jul}

_{Aug}

_{Sep}

_{Oct}

_{Nov}

_{Dec}

S  M  T  W  T  F  S 







1

2
(10) 
3
(9) 
4
(15) 
5
(12) 
6
(12) 
7
(9) 
8
(3) 
9
(4) 
10
(6) 
11
(15) 
12
(17) 
13
(15) 
14
(6) 
15
(4) 
16
(5) 
17
(4) 
18

19

20
(2) 
21
(4) 
22
(7) 
23
(6) 
24
(13) 
25
(1) 
26

27
(3) 
28

29

30
(1) 
31






From: Ethan A Merritt <merritt@u.washington.edu>  20051023 23:16:14

On Sunday 23 October 2005 03:00 pm, Harald Harders wrote: > float a = 0.0; > if (a == 0) ... > > always is true? I don't think so. IEEE standard guarantees this. Even in the case that an architecture can represent both +0 and 0, it is required that +0 == 0. Yes, I know that not all C compilers require IEEE floating point. But I am inclined to say that if your compiler is so broken that it fails to store 0 as 0, then using it to build gnuplot will reveal bigger problems than accurate text rotation :) >> The only place a rotation angle gets set is in parse_label_options(). > I find more: 3555, 4020 True. This may be telling us that these places ("set tics" and "set {xyz}tics") should call parse_label_options() rather than duplicating the code locally. > Sooner or later, this will also have to be added in line 3715 (by the > way, funny that there still are texts not rotatable by arbitrary > angles). You want to rotate the timestamp? That seems a little bit overboard. If you really want to write the data on a plot in a fancy font or rotated text, you can easily use some variant of set label "`date`". > Another thing could be thought of: > Terminals that can only set term horizontally or vertically should > switch from horizontal to vertical text when exceeding 45 degrees, not > when going from zero to one. What do you mean? I think that if someone really wants 45 degree text, they will be equally unhappy with either 0 or 90. > And we really should find out which terminals are capable of arbitrary > text angles but do not use it right now. Sure. I originally added it to all the terminal types I could test at the time. And there's a patch on SourceForge that adds it to metapost. But there remain other terminal types I cannot test, or I do not have documentation for their output device capabilities.  Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle 981957742 
From: Harald Harders <h.harders@tu...>  20051023 21:54:48

Ethan, I will also post this mail to the mailing list because at least parts of it can be interesting to the gnuplot community. On Sun, 23 Oct 2005, Ethan A Merritt wrote: > On Sunday 23 October 2005 01:50 pm, you wrote: > > I do not agree that (angle == 0) is sufficient. Many > > terminals switch from horizontal text to vertical text > > (angle 90) if the given angle is different from 0. If small > > rounding errors lead to vertical text instead of horizontal > > text, this is a severe bug. > > But where can these rounding errors occur? > Not internal to gnuplot, because gnuplot does not calculate > text rotation angle internally anywhere that I can think of. I don't trust C compilers that they will return exactly 0 when you set a variable to 0 in all cases. Does the ANSI C standard define that float a = 0.0; if (a == 0) ... always is true? I don't think so. May be, most architectures do so. But all? When learning programming I have always been told not to test against an exact value when using floating variables. > The only place a rotation angle gets set is in > parse_label_options(). > So it should be sufficient to check in that one place. > >  gnuplot/src/set.c 20051009 19:44:36.000000000 0700 > +++ gnuplotcvs/src/set.c 20051023 14:27:18.995207128 0700 > @@ 4741,7 +4788,9 @@ I find more: 3555, 4020 Sooner or later, this will also have to be added in line 3715 (by the way, funny that there still are texts not rotatable by arbitrary angles). With the approach in my patch, all newly introduced angles are covered automatically. And rounding errors of a bad C compiler implementation are eliminated. The number of calles to these functions is not too bad to slow down plots since normally, not too many texts are put into a plot (in comparison to lines, for instance). Another thing could be thought of: Terminals that can only set term horizontally or vertically should switch from horizontal to vertical text when exceeding 45 degrees, not when going from zero to one. What do you mean? But I think this could be a seperate patch after this one. And we really should find out which terminals are capable of arbitrary text angles but do not use it right now. I have found at least one of them. Best regards Harald  Harald Harders h.harders@... http://www.haraldharders.de 
From: Ethan A Merritt <merritt@u.washington.edu>  20051023 19:58:01

On Sunday 23 October 2005 12:23 am, Petr Mikulik wrote: > > It would be nice to organize that > plot 'a.dat' matrix > is equivalent to > plot 'a.dat' matrix using 1:3 OK. That part is now in cvs. I'm still amazed that this works. Who knew that you could plot data rows? I'm still confused by the documentation, and will try to clarify it. For example, you suggest > The zvalues are read in a row at a time, i. e., > z11 z12 z13 z14 ... > z21 z22 z23 z24 ... > z31 z32 z33 z34 ... > X and yindices of the matrix correspond to column and row index of the But this is not really correct, as the use of "plot <foo> matrix" demonstrates. "Column 3" may or may not be a Z value, depending on what kind of graph you are describing. My current best effort at writing a description is: Matrix values are read in a row at a time, i. e., M11 M12 M13 M14 ... (i=1) M21 M22 M23 M24 ... (i=2) M31 M32 M33 M34 ... (i=3) ... ... ... ... Mij The interpretation of columns in the "using" specification for matrix data is different from the usual case. "$1" refers to the matrix row index i, "$2" refers to the matrix column index j, and "$3" refers to the matrix entry Mij. Example: set view map splot <foo> matrix using ($1 * 5.):2:(sqrt($3)) This example will plot the value sqrt(Mij) at the coordinates x=5i, y=j for each entry i,j represented in the matrix. Does this description seem OK to you? > *** > > Proposal for 'help matrix', please modify: > > Datafile can be in an ascii or binary matrix format. The `matrix` flag > indicates that the file is ascii, the `binary` or `matrix binary` stands > for a binary format. For details, see `matrix ascii` or `matrix binary`. > > Basic usage in `splot`: > splot 'a.dat' matrix > splot 'a.gpbin' {matrix} binary > Advanced usage in `splot`: > splot 'a.dat' matrix using 1:2:3 > splot 'a.gpbin' {matrix} binary using 1:2:3 > allows to manipulate the axes coordinates and the zdata. > > Usage in `plot`: > plot `a.dat` matrix using 1:3 > plot 'a.gpbin' {matrix} binary using 1:3 > will plot rows of the matrix, while using 2:3 will plot matrix columns, > and 1:2 point coordinates. Applying the `every` option you can specify > explicit rows and columns. > > Example  rescale axes for an ascii matrix: > splot `a.dat` matrix using (1+$1):(1+$2*10):3 > > Example  plot the 3rd row of an ascii matrix: > plot 'a.dat' matrix using 1:3 every 1:999:1:2 > (rows are enumerated from 0, thus 2 instead of 3). > > *** > > Proposal for 'help matrix ascii', please modify: > > The `matrix` flag in > {s}plot 'a.dat' matrix > indicates that the ASCII data are stored in matrix format. > > The zvalues are read in a row at a time, i. e., > z11 z12 z13 z14 ... > z21 z22 z23 z24 ... > z31 z32 z33 z34 ... > and so forth. > > X and yindices of the matrix correspond to column and row index of the > matrix, starting from 0. You can rescale or transform the axes as usual > for a data file with three columns (x=$1, y=$2, z=$3), for example > splot 'a.dat' matrix using (1+$1/100):(1+$2*10):3 > > A blank line or comment line ends the matrix, and starts a new > surface mesh. You can select among the meshes inside a file by the > `index` option to the `splot` command, as usual. > > >  > PM  Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle 981957742 
From: Juergen Wieferink <wieferink@fr...>  20051023 08:46:48

On Saturday 22 October 2005 20:42 Ethan A Merritt wrote: > How about if we could plot Petr's example: > splot 'matrix.dat' matrix using (1+$1/100):(1+$2*10):3 > as > f(x) = 1 + x/100 > g(y) = 1 + y*10 > splot 'matrix.dat' matrix xticlabels(f(x)):yticlabels(g(y)) > > Would that be more natural? With this, I would expect one label for each row and each column. I think it would be more natural to introduce some set format x function f(x) where f(x) is a string valued expression with a dummy variable "x". But in the case of matrix, I prefer Petr's example. Juergen 
From: Petr Mikulik <mikulik@ph...>  20051023 07:23:14

> You don't find it confusing that in 2D plots you need to say > plot 'data' matrix using ($1):($3) > > Why ($3)? I never know I can use plot ... matrix I'm still learning gnuplot :)) It would be nice to organize that plot 'a.dat' matrix is equivalent to plot 'a.dat' matrix using 1:3 *** Proposal for 'help matrix', please modify: Datafile can be in an ascii or binary matrix format. The `matrix` flag indicates that the file is ascii, the `binary` or `matrix binary` stands for a binary format. For details, see `matrix ascii` or `matrix binary`. Basic usage in `splot`: splot 'a.dat' matrix splot 'a.gpbin' {matrix} binary Advanced usage in `splot`: splot 'a.dat' matrix using 1:2:3 splot 'a.gpbin' {matrix} binary using 1:2:3 allows to manipulate the axes coordinates and the zdata. Usage in `plot`: plot `a.dat` matrix using 1:3 plot 'a.gpbin' {matrix} binary using 1:3 will plot rows of the matrix, while using 2:3 will plot matrix columns, and 1:2 point coordinates. Applying the `every` option you can specify explicit rows and columns. Example  rescale axes for an ascii matrix: splot `a.dat` matrix using (1+$1):(1+$2*10):3 Example  plot the 3rd row of an ascii matrix: plot 'a.dat' matrix using 1:3 every 1:999:1:2 (rows are enumerated from 0, thus 2 instead of 3). *** Proposal for 'help matrix ascii', please modify: The `matrix` flag in {s}plot 'a.dat' matrix indicates that the ASCII data are stored in matrix format. The zvalues are read in a row at a time, i. e., z11 z12 z13 z14 ... z21 z22 z23 z24 ... z31 z32 z33 z34 ... and so forth. X and yindices of the matrix correspond to column and row index of the matrix, starting from 0. You can rescale or transform the axes as usual for a data file with three columns (x=$1, y=$2, z=$3), for example splot 'a.dat' matrix using (1+$1/100):(1+$2*10):3 A blank line or comment line ends the matrix, and starts a new surface mesh. You can select among the meshes inside a file by the `index` option to the `splot` command, as usual.  PM 
From: Ethan A Merritt <merritt@u.washington.edu>  20051023 04:27:05

On Saturday 22 October 2005 03:02 pm, Petr Mikulik wrote: > I think I've tracked the bug down Found it. Bleah. It really has been there since forever. It's in df_tokenise(), and it is specific to ascii matrix data. Here is the fix:  gnuplot/src/datafile.c 20051021 22:50:13.000000000 0700 +++ gnuplotcvs/src/datafile.c 20051022 21:10:08.276728128 0700 @@ 1145,6 +1146,7 @@ if (df_matrix) { duplication=TRUE; break; } df_matrix = TRUE; #endif + fast_columns = 0; continue; } Corey Satten's monster optimization test skips all columns past the first three unless some test has previously cleared the fast_columns flag. Examples of things that clear the flag are parentheses in the using spec and the presence of the "binary" flag. The optimization test is also skipped if there are no using specs at all. Ascii matrix data is not covered by any of these exceptions, so df_tokenise() only parses the first 3 columns. Amazing that no one has complained in all the time since 3.7 came out.  Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle 981957742 