You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(2) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(3) |
Feb
(1) |
Mar
(2) |
Apr
(22) |
May
(52) |
Jun
(43) |
Jul
(36) |
Aug
(59) |
Sep
(37) |
Oct
(55) |
Nov
(39) |
Dec
(36) |
| 2005 |
Jan
(64) |
Feb
(40) |
Mar
(62) |
Apr
(58) |
May
(256) |
Jun
(77) |
Jul
(80) |
Aug
(39) |
Sep
(56) |
Oct
(36) |
Nov
(113) |
Dec
(68) |
| 2006 |
Jan
(43) |
Feb
(64) |
Mar
(69) |
Apr
(60) |
May
(71) |
Jun
(53) |
Jul
(63) |
Aug
(63) |
Sep
(76) |
Oct
(85) |
Nov
(82) |
Dec
(73) |
| 2007 |
Jan
(75) |
Feb
(82) |
Mar
(84) |
Apr
(104) |
May
(67) |
Jun
(101) |
Jul
(107) |
Aug
(138) |
Sep
(128) |
Oct
(106) |
Nov
(112) |
Dec
(112) |
| 2008 |
Jan
(94) |
Feb
(87) |
Mar
(146) |
Apr
(169) |
May
(75) |
Jun
(26) |
Jul
(26) |
Aug
(7) |
Sep
(18) |
Oct
(53) |
Nov
(42) |
Dec
(19) |
| 2009 |
Jan
(43) |
Feb
(39) |
Mar
(18) |
Apr
(45) |
May
(66) |
Jun
(87) |
Jul
(56) |
Aug
(41) |
Sep
(56) |
Oct
(139) |
Nov
(98) |
Dec
(88) |
| 2010 |
Jan
(81) |
Feb
(79) |
Mar
(83) |
Apr
(97) |
May
(124) |
Jun
(84) |
Jul
(53) |
Aug
(85) |
Sep
(89) |
Oct
(50) |
Nov
(98) |
Dec
(78) |
| 2011 |
Jan
(97) |
Feb
(74) |
Mar
(68) |
Apr
(54) |
May
(63) |
Jun
(59) |
Jul
(65) |
Aug
(58) |
Sep
(37) |
Oct
(40) |
Nov
(59) |
Dec
(35) |
| 2012 |
Jan
(16) |
Feb
(56) |
Mar
(63) |
Apr
(25) |
May
(48) |
Jun
(58) |
Jul
(20) |
Aug
(13) |
Sep
(43) |
Oct
(35) |
Nov
(20) |
Dec
(17) |
| 2013 |
Jan
(22) |
Feb
(11) |
Mar
(51) |
Apr
(34) |
May
(57) |
Jun
(27) |
Jul
(70) |
Aug
(30) |
Sep
(38) |
Oct
(53) |
Nov
(40) |
Dec
(25) |
| 2014 |
Jan
(26) |
Feb
(35) |
Mar
(60) |
Apr
(12) |
May
(17) |
Jun
(15) |
Jul
(9) |
Aug
(18) |
Sep
(46) |
Oct
(18) |
Nov
(19) |
Dec
(15) |
| 2015 |
Jan
(17) |
Feb
(28) |
Mar
(21) |
Apr
(54) |
May
(36) |
Jun
(8) |
Jul
(30) |
Aug
(13) |
Sep
(3) |
Oct
(28) |
Nov
(3) |
Dec
(3) |
| 2016 |
Jan
(11) |
Feb
(9) |
Mar
(29) |
Apr
(10) |
May
(8) |
Jun
(5) |
Jul
(50) |
Aug
(57) |
Sep
(13) |
Oct
(5) |
Nov
(17) |
Dec
(11) |
| 2017 |
Jan
(3) |
Feb
(23) |
Mar
(16) |
Apr
(7) |
May
(15) |
Jun
(12) |
Jul
(48) |
Aug
(15) |
Sep
(3) |
Oct
(20) |
Nov
(28) |
Dec
(21) |
| 2018 |
Jan
(13) |
Feb
(21) |
Mar
(21) |
Apr
(7) |
May
(3) |
Jun
(7) |
Jul
(27) |
Aug
(38) |
Sep
(4) |
Oct
(30) |
Nov
(22) |
Dec
|
| 2019 |
Jan
(5) |
Feb
(16) |
Mar
(1) |
Apr
(9) |
May
(7) |
Jun
(20) |
Jul
(13) |
Aug
(3) |
Sep
(2) |
Oct
(2) |
Nov
(2) |
Dec
(4) |
| 2020 |
Jan
(6) |
Feb
(11) |
Mar
(1) |
Apr
(18) |
May
(4) |
Jun
(5) |
Jul
(12) |
Aug
(1) |
Sep
(3) |
Oct
(7) |
Nov
(1) |
Dec
(17) |
| 2021 |
Jan
(1) |
Feb
(11) |
Mar
(16) |
Apr
(6) |
May
(5) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(8) |
Oct
(10) |
Nov
(4) |
Dec
(4) |
| 2022 |
Jan
(9) |
Feb
(35) |
Mar
(4) |
Apr
|
May
(3) |
Jun
(49) |
Jul
(11) |
Aug
|
Sep
(5) |
Oct
(2) |
Nov
(16) |
Dec
(13) |
| 2023 |
Jan
|
Feb
(8) |
Mar
(3) |
Apr
|
May
(8) |
Jun
|
Jul
(5) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(2) |
| 2024 |
Jan
(6) |
Feb
(9) |
Mar
|
Apr
(26) |
May
(24) |
Jun
|
Jul
(4) |
Aug
(2) |
Sep
(1) |
Oct
(10) |
Nov
(9) |
Dec
|
| 2025 |
Jan
|
Feb
(22) |
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(4) |
| 2026 |
Jan
|
Feb
(24) |
Mar
(20) |
Apr
(18) |
May
(2) |
Jun
(2) |
Jul
(2) |
Aug
(3) |
Sep
(6) |
Oct
(3) |
Nov
(2) |
Dec
|
|
From: Alan C. <ala...@gm...> - 2016-07-30 03:07:36
|
On 7/29/16, Ethan Merritt <eam...@gm...> wrote: > Use the "stats" command. If you only need to know the y value range, that > would be > > stats "outvals.tab" using 2 Thank you, that's close. What it gets though are the min/max of the data rather than the limits of the plot. For example 17.6 - 31.9 rather than 16 - 32. I imagine there's a relatively simple formula that sets the plot limits to round numbers? I think those are what I should put through the * 1.8 + 32 conversion. I probably can't access the plot limits but I can derive them over again from the data limits if I know the formula. -- Credit is the root of all evil. - AB1JX |
|
From: Ethan M. <eam...@gm...> - 2016-07-29 21:29:05
|
Use the "stats" command. If you only need to know the y value range, that
would be
stats "outvals.tab" using 2
On Fri, Jul 29, 2016 at 12:59 PM, Alan Corey <ala...@gm...> wrote:
> My data is data points contained in an input file. What I'd like to
> do is something like:
>
> set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32]
>
> But GPVAL_Y_MIN and GPVAL_Y_MAX apparently aren't defined until the
> read is complete, and putting things like y2range or y2ticks after the
> read seems to have no effect. I tried refresh and replot after the y2
> stuff, even a 2nd plot line.
>
> Is there a way to do a dummy read that just sets up the min/max stuff?
>
> reset
> set terminal gif size 1200,800
> set output "2labc.gif"
> set xdata time
> set timefmt x "%s"
> set format x "%H:%M\n%D"
> set style data lines
> set xtics auto
> # GPVAL_Y_MIN etc aren't defined yet
> #set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32]
> set y2label "Fahrenheit"
> plot "outvals.tab" using ($1-(4*3600)):2 notitle
> # These have no effect:
> #set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32]
> #set y2tics auto
> #refresh
>
>
> --
> Credit is the root of all evil. - AB1JX
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> gnuplot-info mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-info
>
|
|
From: Alan C. <ala...@gm...> - 2016-07-29 19:59:38
|
My data is data points contained in an input file. What I'd like to do is something like: set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32] But GPVAL_Y_MIN and GPVAL_Y_MAX apparently aren't defined until the read is complete, and putting things like y2range or y2ticks after the read seems to have no effect. I tried refresh and replot after the y2 stuff, even a 2nd plot line. Is there a way to do a dummy read that just sets up the min/max stuff? reset set terminal gif size 1200,800 set output "2labc.gif" set xdata time set timefmt x "%s" set format x "%H:%M\n%D" set style data lines set xtics auto # GPVAL_Y_MIN etc aren't defined yet #set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32] set y2label "Fahrenheit" plot "outvals.tab" using ($1-(4*3600)):2 notitle # These have no effect: #set y2range [(1.8*GPVAL_Y_MIN)+32:(1.8*GPVAL_Y_MAX)+32] #set y2tics auto #refresh -- Credit is the root of all evil. - AB1JX |
|
From: Ethan M. <eam...@gm...> - 2016-07-29 18:52:19
|
1) version 5.0:
set mxtics 10 # see "help set mxtics"
set mytics 10
version 5.1
currently a bug. thanks for the report
2) set sample 10000
Or else define the functions as parametric so that the sample is
independent of the x/y precision.
But increasing the number of samples is easier.
On Fri, Jul 29, 2016 at 11:28 AM, D <dcm...@we...> wrote:
> Hi, using:
>
> set terminal pngcairo truecolor enhanced font "arial,11" fontscale 1.0
> size 1000,1000
> set output "test.png"
>
> set log xy
> #set logscale xy
>
> set xrange [100:1e7]
> set yrange [100:1e7]
>
> set grid xtics ytics mxtics mytics lt 0 lw 1 lc rgb "#000000"
>
> f(x) = x/ (1-0.0001*x)
> fi(x) = x/(1/(1-0.0001*x))
> g(x) = x/ (1-0.0000001*x)
> gi(x) = x/(1/(1-0.0000001*x))
> id(x) = x
>
> plot f(x) lt 2 lc rgb "#ff0000" lw 1 , \
> fi(x) lt 2 lc rgb "#ff0000" lw 1 , \
> g(x) lt 2 lc rgb "#ff0000" lw 1 , \
> gi(x) lt 2 lc rgb "#ff0000" lw 1 , \
> id(x) dashtype 2 lc rgb "#000000" lw 1
>
> 1) the grid tick lines look either incorrect or at least not to what
> they look up to [100:1e6]. How can I make them work with [100:1e7] ?
> 2) the plot of the lines does neither go to the bottom (fi,gi), nor to
> the top (f,g), as expected. How to fix?
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> gnuplot-info mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-info
>
|
|
From: D <dcm...@we...> - 2016-07-29 18:28:45
|
Hi, using:
set terminal pngcairo truecolor enhanced font "arial,11" fontscale 1.0
size 1000,1000
set output "test.png"
set log xy
#set logscale xy
set xrange [100:1e7]
set yrange [100:1e7]
set grid xtics ytics mxtics mytics lt 0 lw 1 lc rgb "#000000"
f(x) = x/ (1-0.0001*x)
fi(x) = x/(1/(1-0.0001*x))
g(x) = x/ (1-0.0000001*x)
gi(x) = x/(1/(1-0.0000001*x))
id(x) = x
plot f(x) lt 2 lc rgb "#ff0000" lw 1 , \
fi(x) lt 2 lc rgb "#ff0000" lw 1 , \
g(x) lt 2 lc rgb "#ff0000" lw 1 , \
gi(x) lt 2 lc rgb "#ff0000" lw 1 , \
id(x) dashtype 2 lc rgb "#000000" lw 1
1) the grid tick lines look either incorrect or at least not to what
they look up to [100:1e6]. How can I make them work with [100:1e7] ?
2) the plot of the lines does neither go to the bottom (fi,gi), nor to
the top (f,g), as expected. How to fix?
|
|
From: zowie <def...@bo...> - 2016-07-29 16:21:33
|
Documentation in general is hard, and presenting information in a way that end-users can read is a skill that is quite different from presenting it in a way that works for experts. My favorite example of the pitfalls was the three-line instruction manual that used to appear on emacs’ front page by default, back in the 1990s. It read something like this: The expression “C-“ means to hold down control while pressing the key. To load a file, type “C-X F”. For a self-help tutorial, type “C-H T”. To quit, type “C-X C-C”. I encountered that text as a graduate student in the Physics Dept. at Stanford University in 1990. For the next few years, I would tell new students in my research group to “just fire up emacs, and follow the directions to the tutorial”. Out of about 8-10 people to whom I told that (remember, these were pretty smart people) zero of them actually found the self-help tutorial the first try, without being told to read EVERY WORD of what was on the screen. It turns out that it’s very hard for people to find text in the middle of other text — we’re not natural greppers. The gnuplot documentation suffers from the same sort of fallacy, in spades. As an expert I still have trouble finding items in it. For example, I recently had trouble with single vs. double quotes in our Perl front-end module (PDL::Graphics::Gnuplot), because despite multiple reads it was not obvious to me from the documentation that those two types of quote are interchangeable and behave slightly differently within gnuplot. That’s not to chastise the team — Ethan and Hans-Bernhard and everyone else have created (and continue to maintain) something phenomenally useful and flexible. Just to acknowledge that many of the support issues on this list (and tons of “invisible” ones that never get mailed here) reflect a need to improve the documentation, rather than a failure of the user base or holes in the code itself. Cheers, Craig > On Jul 29, 2016, at 7:30 AM, Alan Corey <ala...@gm...> wrote: > >> It took me quite some time to figure out a few things. This might keep >> some people away from using gnuplot. > > Who takes time to read documentation? I mean, I have, but my best > resource for looking up how to do something is to look at how I did it > a year ago. That's true not only for Gnuplot. > > One thing that might help is to somewhere on a web page have tiny > (320x200 or so) thumbnails of different plot types that are linked to > maybe example plot scripts and/or into the documentation where it > talks about using some feature. I thought Gnuplot had a "concept > index", something I use does, in addition to a normal index. > > But that's part of my point, if you use a few dozen different programs > and each one has hundreds of pages of documentation there isn't time > in a lifetime to read it all. It's good that the documentation > exists, but having maybe a few different ways of finding what you're > looking for in it is good too. And this seems to be more of a problem > in things written by committees or multiple people or at different > times. Lazarus for example is potentially a great program with > thousands of pages of documentation spanning a couple decades but you > can't find anything in it. > > So I look up how I did it last time. I use the PDFs and online > documentation too. > > ------------------------------------------------------------------------------ > _______________________________________________ > gnuplot-info mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-info > |
|
From: sfeam <sf...@us...> - 2016-07-29 15:24:27
|
On Friday, 29 July 2016 09:30:30 AM Alan Corey wrote:
> > It took me quite some time to figure out a few things. This might keep
> > some people away from using gnuplot.
>
> Who takes time to read documentation? I mean, I have, but my best
> resource for looking up how to do something is to look at how I did it
> a year ago. That's true not only for Gnuplot.
>
> One thing that might help is to somewhere on a web page have tiny
> (320x200 or so) thumbnails of different plot types that are linked to
> maybe example plot scripts and/or into the documentation where it
> talks about using some feature. I thought Gnuplot had a "concept
> index", something I use does, in addition to a normal index.
http://gnuplot.sourceforge.net/demo/
>
> But that's part of my point, if you use a few dozen different programs
> and each one has hundreds of pages of documentation there isn't time
> in a lifetime to read it all. It's good that the documentation
> exists, but having maybe a few different ways of finding what you're
> looking for in it is good too. And this seems to be more of a problem
> in things written by committees or multiple people or at different
> times. Lazarus for example is potentially a great program with
> thousands of pages of documentation spanning a couple decades but you
> can't find anything in it.
>
> So I look up how I did it last time. I use the PDFs and online
> documentation too.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> gnuplot-info mailing list
> gnu...@li...
> Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-info
|
|
From: Alan C. <ala...@gm...> - 2016-07-29 13:30:37
|
> It took me quite some time to figure out a few things. This might keep > some people away from using gnuplot. Who takes time to read documentation? I mean, I have, but my best resource for looking up how to do something is to look at how I did it a year ago. That's true not only for Gnuplot. One thing that might help is to somewhere on a web page have tiny (320x200 or so) thumbnails of different plot types that are linked to maybe example plot scripts and/or into the documentation where it talks about using some feature. I thought Gnuplot had a "concept index", something I use does, in addition to a normal index. But that's part of my point, if you use a few dozen different programs and each one has hundreds of pages of documentation there isn't time in a lifetime to read it all. It's good that the documentation exists, but having maybe a few different ways of finding what you're looking for in it is good too. And this seems to be more of a problem in things written by committees or multiple people or at different times. Lazarus for example is potentially a great program with thousands of pages of documentation spanning a couple decades but you can't find anything in it. So I look up how I did it last time. I use the PDFs and online documentation too. |
|
From: theozh <th...@gm...> - 2016-07-29 13:11:19
|
Is there a way in gnuplot to interactively enter a few values, i.e. numbers and strings? The idea is to enable users which are not familiar with gnuplot and do not want to (are not able to or should not) edit a gnuplot script to generate plots which require a few custom values which are then stored in user variables for further use in the script. The command "pause" allows some very limited user input pause mouse keypress "Type a letter" # Returning the ASCII value of the key pressed in MOUSE_KEY or pause -1 "Hit a key to continue" But I am looking for a simple popup window, e.g. like: +------------------+ | Sample: ....... | | Start: ....... | | Stop: ....... | | | | OK Cancel | +------------------+ Any ways to achieve this? |
|
From: theozh <th...@gm...> - 2016-07-29 12:21:14
|
well, certainly almost all the information you need is somewhere in documentation, manual and demos. However, as a beginner, if you stumble across the command "multiplot" you may believe that this could do the job, although for most cases "plot" is sufficient. When I started with gnuplot I was missing comprehensive tutorials (let me know if I missed one). A tutorial is not the same as a manual. Although, there are a lot of introductory tutorials around, most of them were too basic and soon not sufficient or satisfying anymore. If you have reached a certain level, you mostly get along with the manual. More explicit, I missed e.g. - an overview plot illustrating and explaining the nomenclature of the axis, labels, tics, coordinates, margins; as well as names and concepts e.g. for frame, border, margin, canvas, etc. If you do not now how an object, setting or parameter is named, it is difficult to search for it. - many tips and tricks... and "how to's"... (which of course is the intention of the demos). - updated tips and tricks based on the questions which are asked and answered e.g. in this newsgroup - known limits and difficulties what can be done with gnuplot and what not (and workarounds if there is one). It took me quite some time to figure out a few things. This might keep some people away from using gnuplot. I am wondering whether it is generally possible to write a tutorial which makes it unnecessary to search the web or to ask (FA)Qs in forums or newsgroups. Assuming of course that people are reading and following the tutorial ;-). This might be a task to linguists to funnel and direct all possible terms and questions to the right information and instruction in the tutorial/manual. I can imagine that is a lot of work to compile the manual. Thanks to all who have been involved! A comprehensive and understandable step by step tutorial might be a project on its own. |
|
From: Dave H. <da...@ho...> - 2016-07-29 02:30:37
|
On Thu, 28 Jul 2016, Hans-Bernhard Bröker wrote: > I keep wondering how so many people arrive at the belief that they > should be using multiplot for so many jobs it's the completely wrong > tool for. Is the concept of > > plot 'file1', 'file2' > > really that hard to pick up from the documentation and demos? Could it be that there is something wrong with the documentation? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." |
|
From: BBands <bb...@gm...> - 2016-07-28 21:07:26
|
A one word change should clear that up.
"The command set multiplot places gnuplot in the multiplot mode, in
which several
_independent_ plots are placed on the same page, window, or screen."
John
On Thu, Jul 28, 2016 at 11:35 AM, Kevin Oberman <rko...@gm...> wrote:
> On Thu, Jul 28, 2016 at 10:38 AM, Hans-Bernhard Bröker <
> HBB...@t-...> wrote:
>
> > Am 28.07.2016 um 11:03 schrieb Robert von Knobloch:
> >
> > > Using multiplot, I would like to be able to align the temperature with
> > > the date/time of the data, so that the correlation between temp and
> data
> > > can be easily viewed.
> >
> > You really should _not_ be using multiplot for that. Just plot both
> > data sets in a single 'plot' command, and you'll be done with it.
> >
> > I keep wondering how so many people arrive at the belief that they
> > should be using multiplot for so many jobs it's the completely wrong
> > tool for. Is the concept of
> >
> > plot 'file1', 'file2'
> >
> > really that hard to pick up from the documentation and demos?
> >
> >
> >
> ------------------------------------------------------------------------------
> >
>
> In a word, yes!
>
> "set multiplot" just looks like the right thing when you want multiple
> plots to one screen or file. The manual makes it look like that is the
> answer:
> "The command set multiplot places gnuplot in the multiplot mode, in which
> several plots are placed on
> the same page, window, or screen."
>
> I was lucky enough to read the manual for "plot" and wee that it took
> multiple files, each with the standard options for style and it just
> worked. But, if you search the manual for "multi", you find "multiplot over
> and over along with the repeated (and correct) statement:
> "Remember to close the output file before next plot unless in multiplot
> mode." makes it sound like multiplot is the intended tool for placing
> multiple data sets onto a single plot when it is actually intended for a
> similar, but different purpose.
>
> I wish the "set multiplot" section had something near that top pointing out
> that 'plot "file1", "file2", ..." is another, possibly more appropriate
> approach.
>
|
|
From: Kevin O. <rko...@gm...> - 2016-07-28 18:35:12
|
On Thu, Jul 28, 2016 at 10:38 AM, Hans-Bernhard Bröker < HBB...@t-...> wrote: > Am 28.07.2016 um 11:03 schrieb Robert von Knobloch: > > > Using multiplot, I would like to be able to align the temperature with > > the date/time of the data, so that the correlation between temp and data > > can be easily viewed. > > You really should _not_ be using multiplot for that. Just plot both > data sets in a single 'plot' command, and you'll be done with it. > > I keep wondering how so many people arrive at the belief that they > should be using multiplot for so many jobs it's the completely wrong > tool for. Is the concept of > > plot 'file1', 'file2' > > really that hard to pick up from the documentation and demos? > > > ------------------------------------------------------------------------------ > In a word, yes! "set multiplot" just looks like the right thing when you want multiple plots to one screen or file. The manual makes it look like that is the answer: "The command set multiplot places gnuplot in the multiplot mode, in which several plots are placed on the same page, window, or screen." I was lucky enough to read the manual for "plot" and wee that it took multiple files, each with the standard options for style and it just worked. But, if you search the manual for "multi", you find "multiplot over and over along with the repeated (and correct) statement: "Remember to close the output file before next plot unless in multiplot mode." makes it sound like multiplot is the intended tool for placing multiple data sets onto a single plot when it is actually intended for a similar, but different purpose. I wish the "set multiplot" section had something near that top pointing out that 'plot "file1", "file2", ..." is another, possibly more appropriate approach. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rko...@gm... PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 |
|
From: Craig D. <def...@bo...> - 2016-07-28 18:03:19
|
(Mobile) > On Jul 28, 2016, at 11:38 AM, Hans-Bernhard Bröker <HBB...@t-...> wrote: > > I keep wondering how so many people arrive at the belief that they > should be using multiplot for so many jobs it's the completely wrong > tool for. Is the concept of > > plot 'file1', 'file2' > > really that hard to pick up from the documentation and demos? > Actually, yes, I think it is. Gnuplot uses a different paradigm than most other plotting package: in essence, one is specifying a plot object (axes, frame, etc.) at a time. Most other plotting packages instead approach the problem from a procedural standpoint: conceptually, one is issuing instructions for how to manipulate a plot object, until it gets to the final desired state. That paradigmatic difference between gnuplot and, say, matplotlib could probably do with some introductory material inthegeneral overview at the top of the documentation... > ------------------------------------------------------------------------------ > _______________________________________________ > gnuplot-info mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-info > |
|
From: Hans-Bernhard B. <HBB...@t-...> - 2016-07-28 17:39:05
|
Am 28.07.2016 um 11:03 schrieb Robert von Knobloch: > Using multiplot, I would like to be able to align the temperature with > the date/time of the data, so that the correlation between temp and data > can be easily viewed. You really should _not_ be using multiplot for that. Just plot both data sets in a single 'plot' command, and you'll be done with it. I keep wondering how so many people arrive at the belief that they should be using multiplot for so many jobs it's the completely wrong tool for. Is the concept of plot 'file1', 'file2' really that hard to pick up from the documentation and demos? |
|
From: Robert v. K. <bo...@en...> - 2016-07-28 09:06:26
|
Hallo, I am logging certain industrial processes, with the data in a single file. Noticing some temperature effects, I have added a temperature sensor, but this logs, asynchronously, to a second file. Both files (data and temperature) have timestamps in known fields. Using multiplot, I would like to be able to align the temperature with the date/time of the data, so that the correlation between temp and data can be easily viewed. The temperature has a different start date and period times. Is this possible? Many thanks, Bob von Knobloch |
|
From: Ethan M. <eam...@gm...> - 2016-07-27 18:59:30
|
Use the "set link" command (version 5 only)
gnuplot> set link y2 via (y-32)*5./9. inv (y*9./5.)+32
gnuplot> set ytics format "%.0f °F"
gnuplot> set y2tics format "%.0f °C"
gnuplot> set xrange [0:150]
gnuplot> plot x
Imperfect ascii plot using "set term dumb":
+-------+-------+-------+------+-------+-------+-------+--**
140 °F + *** +60 °C
| ***** |
| **** |
120 °F + **** +50 °C
| **** |
100 °F + **** +40 °C
| **** |
| *** +30 °C
80 °F + *** +
| *** +20 °C
60 °F + *** +
| **** |
| **** +10 °C
40 °F + **** +
| **** +0 °C
20 °F + **** +
| **** +-10 °C
| *** |
0 °F **------+-------+-------+------+-------+-------+-------+---+
0 20 40 60 80 100 120 140
On Wed, Jul 27, 2016 at 9:59 AM, Alan Corey <ala...@gm...> wrote:
> I can't find an example of where these are being set on the fly, and
> for outdoor temperatures this is necessary since the ranges won't be
> the same year-round. After years of wishing I had a way to do this,
> I've now got an Oregon Scientific temperature sensor outdoors with the
> data being received by radio with an rtlsdr dongle, decoded by rtl_433
> and formatted into something Gnuplot can plot by some C I wrote. See
>
> https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=154451&p=1015069#p1015069
>
> The thermometer setup gives me data in Celsius which I can plot fine,
> but I'd like to add a Fahrenheit scale as Y2 at the right side. Best
> would be to have Y2 with its own tickmarks based on (Y1 * 1.8) + 32,
> but it would be acceptable to have the same tickmarks with different
> labels. I can see how I could manually generate all the tickmarks and
> labels within a program, but is there a way to do this in Gnuplot?
> I'm aiming at having all this run by a cron job and generate a daily
> plot.
>
> I think normally I'd want to set y2range based on what yrange gets set
> to automatically. Or read the Y values at the tickmarks and calculate
> new ones for Y2. I don't want to plot more data, I just want to
> calculate another set of tickmarks. And it needs to change every day.
>
>
> Alan Corey
> --
> Credit is the root of all evil. - AB1JX
>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and
> traffic
> patterns at an interface-level. Reveals which users, apps, and protocols
> are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity
> planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> gnuplot-info mailing list
> gnu...@li...
> Membership management via:
> https://lists.sourceforge.net/lists/listinfo/gnuplot-info
>
|
|
From: Alan C. <ala...@gm...> - 2016-07-27 16:59:34
|
I can't find an example of where these are being set on the fly, and for outdoor temperatures this is necessary since the ranges won't be the same year-round. After years of wishing I had a way to do this, I've now got an Oregon Scientific temperature sensor outdoors with the data being received by radio with an rtlsdr dongle, decoded by rtl_433 and formatted into something Gnuplot can plot by some C I wrote. See https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=154451&p=1015069#p1015069 The thermometer setup gives me data in Celsius which I can plot fine, but I'd like to add a Fahrenheit scale as Y2 at the right side. Best would be to have Y2 with its own tickmarks based on (Y1 * 1.8) + 32, but it would be acceptable to have the same tickmarks with different labels. I can see how I could manually generate all the tickmarks and labels within a program, but is there a way to do this in Gnuplot? I'm aiming at having all this run by a cron job and generate a daily plot. I think normally I'd want to set y2range based on what yrange gets set to automatically. Or read the Y values at the tickmarks and calculate new ones for Y2. I don't want to plot more data, I just want to calculate another set of tickmarks. And it needs to change every day. Alan Corey -- Credit is the root of all evil. - AB1JX |
|
From: theozh <th...@gm...> - 2016-07-15 14:12:55
|
Horizontal bar graphs seem to be a recurrent question.
In contrast to vertical bar graphs and histograms, as far as I know
there is no direct command in gnuplot for creating horizontal ones. I do
not know why. It really would be convenient.
A somewhat cumbersome workaround does it with boxxyerrorbars.
If your file "Test.dat", e.g. looks like the following:
# Col1 Col2 Col3 Legend
5 7 12 ItemA
8 8 14 ItemB
12 24 2 ItemC
3 2 7 ItemD
Make sure that in the following code there is no newline, except after '\'.
The first plot is in absolute values, the second plot in percentage
values. The legend is written as axis tics.
#### horizontal histogram
reset
set multiplot layout 2,1
plot 'Test.dat' \
u (0):($0):(0):($1):($0-0.4):($0+0.4):ytic(4) axes x1y1 with
boxxyerrorbars fs solid lc rgb "red" notitle,\
'' u (0):($0):($1):($1+$2):($0-0.4):($0+0.4):ytic(4) axes x1y1 with
boxxyerrorbars fs solid lc rgb "green" notitle,\
'' u (0):($0):($1+$2):($1+$2+$3):($0-0.4):($0+0.4):ytic(4) axes x1y1
with boxxyerrorbars fs solid lc rgb "blue" notitle,\
plot 'Test.dat' \
u (0):($0):(0):(($1)/($1+$2+$3)):($0-0.4):($0+0.4):ytic(4) axes x1y1
with boxxyerrorbars fs solid lc rgb "red" notitle,\
'' u
(0):($0):(($1)/($1+$2+$3)):(($1+$2)/($1+$2+$3)):($0-0.4):($0+0.4):ytic(4)
axes x1y1 with boxxyerrorbars fs solid lc rgb "green" notitle,\
'' u
(0):($0):(($1+$2)/($1+$2+$3)):(($1+$2+$3)/($1+$2+$3)):($0-0.4):($0+0.4):ytic(4)
axes x1y1 with boxxyerrorbars fs solid lc rgb "blue" notitle,\
unset multiplot
|
|
From: theozh <th...@gm...> - 2016-07-14 19:18:15
|
if your terminal is wxt with ID 0 and you type the following in the
gnuplot command line
if (1) { plot sin(x); pause 5; set term wxt 0 close }
it plots sin(x), waits for 5 seconds and then closes the plot window.
Is this what you are looking for?
|
|
From: Priyadarshi P. <dav...@gm...> - 2016-07-14 15:54:35
|
How to close the plot window automatically after some time period set by me? |
|
From: Robert v. K. <bo...@en...> - 2016-07-14 12:37:43
|
On 14/07/16 14:24, Marek W. Gutowski wrote: > set format y "% 6.0f" Many thanks Marek, I would not have though of this approach, it works pefectly. Bob von Knobloch |
|
From: Robert v. K. <bo...@en...> - 2016-07-14 11:01:35
|
Hello, I am plotting 2 graphs, above each other, using multiplot with a common xrange. Plotting is good but, as the Yaxes have different scales (top plot 0-10 and lower plot 0-1100) the plots are of different widths (due to the different text lengths of the Yics for upper and lower plots. Is there a way to align the xscales? The xscale is date and time. Many thanks, Bob von Knobloch. |
|
From: zowie <def...@bo...> - 2016-07-14 00:19:42
|
It looks correctly plotted to me. Looking at your .dat file: you’re missing a point on 17-April-2016, then you’ve got two points 18-April-2016 and 19-April-2016, both with systolic of 146 (correctly plotted on the Y axis which goes to 160). Those are correctly rendered as a short horizontal line segment between the two data. After that you’ve got a stay in hospital. So it looks like your “glitch” isn’t you running home from hospital, it’s you being sick for a day and breaking the progression. The gap before 18-April may appear larger because the missing point on 17-April loses you *two* line segments: 16-17 and 17-18. You might like to plot this chart with histeps or linespoints rather than with lines: line plots like this are not as useful for understanding point-by-point progressions of missing or error-prone data. For that type of analysis, “histeps” is a better choice: you still get the eye-pleasing connectivity of “lines”, but a more rigorous and less counterintuitive treatment of sampled and missing intervals. Note that the above does not describe a problem with gnuplot, but rather with the practice of drawing plots of noisy (and potentially missing) data by connecting sampled points with straight lines. > On Jul 13, 2016, at 5:15 PM, Dave Horsfall <da...@ho...> wrote: > > Am I the only one with these (allegedly minor) problems? > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." > > ---------- Forwarded message ---------- > Date: Wed, 1 Jun 2016 10:08:29 +1000 (EST) > From: Dave Horsfall <da...@ho...> > To: Gnuplot Mailing List <gnu...@li...> > Subject: Anomalies in Gnuplot > > Gnuplot 5.0 pl 3, on MacOS 10.11.5 > > I'm seeing a couple of glitches in Gnuplot, and I cannot see where I > stuffed up. > > Browse over to www.horsfall.org/gptest and view the files therein; they > are a cut-down version of a script I use to plot my BP etc (note that my > dates use the format d/m/y, as I am not American; later graphs use the > more conventional yy/mm/dd, which actually sorts). > > The gap towards the end of April is where I spent a week in hospital, but > note the sole dot in the middle; there is no datum for it, and anyway I > don't recall dashing home midway through my unintended confinement :-) > > What would be causing it? It's driving me nuts. > > The other glitch is the datum for 18/4/16 (146), which did not go off the > scale but should have (at the time my scale was 0:140, since a BP of over > 140 means Trouble), but that's not so important. > > Help, anyone? > > -- > Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity planning > reports.http://sdm.link/zohodev2dev > _______________________________________________ > gnuplot-info mailing list > gnu...@li... > Membership management via: https://lists.sourceforge.net/lists/listinfo/gnuplot-info > |
|
From: Dave H. <da...@ho...> - 2016-07-13 23:37:41
|
Am I the only one with these (allegedly minor) problems? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." ---------- Forwarded message ---------- Date: Wed, 1 Jun 2016 10:08:29 +1000 (EST) From: Dave Horsfall <da...@ho...> To: Gnuplot Mailing List <gnu...@li...> Subject: Anomalies in Gnuplot Gnuplot 5.0 pl 3, on MacOS 10.11.5 I'm seeing a couple of glitches in Gnuplot, and I cannot see where I stuffed up. Browse over to www.horsfall.org/gptest and view the files therein; they are a cut-down version of a script I use to plot my BP etc (note that my dates use the format d/m/y, as I am not American; later graphs use the more conventional yy/mm/dd, which actually sorts). The gap towards the end of April is where I spent a week in hospital, but note the sole dot in the middle; there is no datum for it, and anyway I don't recall dashing home midway through my unintended confinement :-) What would be causing it? It's driving me nuts. The other glitch is the datum for 18/4/16 (146), which did not go off the scale but should have (at the time my scale was 0:140, since a BP of over 140 means Trouble), but that's not so important. Help, anyone? -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer." |