Activity for Justin Sales
-
Justin Sales posted a comment on ticket #2716
gnuplot 5.4 patchlevel 8 An Interactive Plotting Program Thomas Williams & Colin Kelley Version 5 organized by Ethan A Merritt and others This manual was originally prepared by Dick Crawford
-
error in gnuplot help regarding cntrparam levels incremental
-
error in gnuplot help regarding cntrparam levels incremental
-
error in gnuplot help regarding cntrparam levels incremental
-
Alright. I've tried big numbers (but not huge) like set term wxt size 14400, 7200 and what I obtain is the plot occupying the full window, not more (so no scroll bars); then I've added a zero to both values so as to have 144000 and 72000 instead and I've obtained exactly the same plot. When trying with win terminal, I get the same, except for 144000 and 72000 that crashes.
-
set term win size 1,1 makes gnuplot crash. set term wxt size 1,1 makes the plot disappear (I assume 1,1 is the scale, not the maximum value of x and y, which in my case are much bigger)
-
I understand. keyentry makes the trick, just as label does; for the case of modifying the thickness of the legends while keeping thin graphs, it would be plot for [i=1:5] sin(x/i) with lines lt i **lw 1** notitle, \ for [i=1:5] keyentry with lines lt i **lw i** title "i = ".i which works just fine; I just wondered whether to allow set key lw <n°> would simplify things.
-
I understand. keyentry makes the trick, just as label does; for the case of modifying the thickness of the legends while keeping thin graphs, it would be plot for [i=1:5] sin(x/i) with lines lt i **lw 1** notitle, \ for [i=1:5] keyentry with lines lt i **lw i** title "i = ".i which works just fine; I just wondered whether to allow set key lw <n°> would simplify things.
-
I understand. keyentry makes the trick, just as label does; for the case of modifying the thickness of the legends while keeping thin graphs, it would be plot for [i=1:5] sin(x/i) with lines lt i **lw 1** notitle, \ for [i=1:5] keyentry with lines lt i **lw i** title "i = ".i which works just fine; I just wondered whether to allow set key lw <n°> would simplify things.
-
I understand. keyentry makes the trick, just as label does; for the case of modifying the thickness of the legends while keeping thin graphs, it would be plot for [i=1:5] sin(x/i) with lines lt i **lw 1** notitle, \ for [i=1:5] keyentry with lines lt i **lw i** title "i = ".i which works just fine; I just wondered whether to allow set key lw <n°> would simplify things.
-
For plots that are too dense to fit in the screen, it's useful to make set size (>1),1 then plot (for example, daily temperatures along a century); I don't know for Unix, but for Windows (terminal type set to wxt or win) I would expect then to see the typical horizontal scroll bar but instead there is nothing: you just see the beginning of the graph, nothing else. Try this simple example: set size 10,1; plot sin(x)
-
linewidth of the legends. If I write (for example) set key lw 3 (so as to have thick legends while keeping thin plot lines) it does not recognize it. In fact, when reading the manual, linewidth is not allowed for the key command (other than for the box option, but that concerns only the thickness of the box, not of the legends themselves)
-
To allow scrolling for big graphs in screen/interactive terminals
-
To enable linewidth when setting key
-
Thank you Ethan ! Cannot verify it by now but I'm sure it will work as it always does. Have a good and blessed summer ! ifffam De: feature-requests@gnuplot.p.re.sourceforge.net feature-requests@gnuplot.p.re.sourceforge.net en nombre de Ethan Merritt sfeam@users.sourceforge.net Enviado: lunes, 31 de julio de 2023 18:34 Para: [gnuplot:feature-requests] 557@feature-requests.gnuplot.p.re.sourceforge.net Asunto: [gnuplot:feature-requests] #557 'set arrow' coordinates referred to x1y2 axis, plus coordinate...
-
'set arrow' coordinates referred to x1y2 axis, plus coordinate scaling
-
It thus depend on the terminal and on the O/S (for some reason, your gnuplot plots integer values for y... maybe with set decimalsign ',' above (instead of set decimalsign locale you should get it right; but anyway, that's irrelevant for the mouse reading). Then I guess it is indeed a bug: as you see, the ylabel is well displayed: °C/h; it's only the mouse reading that does not display it well.
-
It thus depend on the terminal and on the O/S (for some reason, your gnuplot plots integer values for y... maybe with set decimalsign ',' you should get it right; but anyway, that's irrelevant for the mouse reading). Then I guess it is indeed a bug: as you see, the ylabel is well displayed: °C/h; it's only the mouse reading that does not display it well.
-
It thus depend on the terminal and on the O/S (for some reason, your gnuplot plots integer values for y, but never mind, fortunately that's irrelevant for the mouse reading). Then I guess it is indeed a bug: as you see, the ylabel is well displayed: °C/h; it's only the mouse reading that does not display it well.
-
term is set to "unknown" just at the beginning, in order to check out min and max values of y data; eventually it is set to wxt '01 nov' doesn't show up in the x-axis for a reason that is beyond me, but that's another issue... reset session set encoding utf8 set term unknown set decimalsign locale set locale "spanish" unset mxtics a = 11 # ath COLUMN OF THE FILE a2= 10 # a2th COLUMN OF THE FILE c = 1 # PLOT EVERY c POINTS año = '2022' v = 12 # N° OF TICS OF X-AXIS giu = 0.02; su = 0.04 # MARGIN [IN...
-
term is set to "unknown" just at the beginning, in order to check out min and max values of y data; eventually it is set to wxt '01 nov' doesn't show up in the x-axis for a reason that is beyond me, but that's another issue... reset session set encoding utf8 set term unknown set decimalsign locale set locale "spanish" unset mxtics a = 11 # ath COLUMN OF THE FILE a2= 10 # a2th COLUMN OF THE FILE c = 1 # PLOT EVERY c POINTS año = '2022' v = 12 # N° OF TICS OF X-AXIS giu = 0.02; su = 0.04 # MARGIN [IN...
-
Just replace bgiu by b * giu and bsu by b * su (at the end of that same line) ... it looks like the editor replaced the original * by the italica writing of what followed.
-
term is set to "unknown" just at the beginning, in order to check out min and max values of y data; eventually it is set to wxt '01 nov' doesn't show up in the x-axis for a reason that is beyond me, but that's another issue... reset session set encoding utf8 set term unknown set decimalsign locale set locale "spanish" unset mxtics a = 11 # ath COLUMN OF THE FILE a2= 10 # a2th COLUMN OF THE FILE c = 1 # PLOT EVERY c POINTS año = '2022' v = 12 # N° OF TICS OF X-AXIS giu = 0.02; su = 0.04 # MARGIN [IN...
-
term is set to "unknown" just at the beginning, in order to check out min and max values of y data; eventually it is set to wxt '01 nov' doesn't show up in the x-axis for a reason that is beyond me, but that's another issue... reset session set encoding utf8 set term unknown set decimalsign locale set locale "spanish" unset mxtics a = 11 # ath COLUMN OF THE FILE a2= 10 # a2th COLUMN OF THE FILE c = 1 # PLOT EVERY c POINTS año = '2022' v = 12 # N° OF TICS OF X-AXIS giu = 0.02; su = 0.04 # MARGIN [IN...
-
O/S is windows and terminal type, wxt
-
To extend set mouse mouseformat function string_valued_function(x, y) to a 2nd y axis
-
That's true, my time/date data are of Apr 2022. Trying with just the day (from day 2 to 29) works just fine. Still... maybe gnuplot could automatically subtract the first x value to make the fit work ? (that would simplify things a lot). My data are of the kind 02/04/2022 -3,3 03/04/2022 4,7 04/04/2022 2,5 05/04/2022 -1,2 06/04/2022 1,0 etc ; here is the result for the fitting function f(x) = r*x + z: iter chisq delta/lim lambda r z 0 7.8958946412e+19 0.00e+00 1.17e+09 1.000000e+00 1.000000e+00 1...
-
That's true, my time/date data are of Apr 2022. Trying with just the day (from day 2 to 29) works just fine. Still... maybe gnuplot could automatically subtract the first x value to make the fit work ? (that would simplify things a lot). My data are of the kind 02/04/2022 -3,3 03/04/2022 4,7 04/04/2022 2,5 05/04/2022 -1,2 06/04/2022 1,0 etc and this is the result for the fitting function f(x) = r*x + z: iter chisq delta/lim lambda r z 0 7.8958946412e+19 0.00e+00 1.17e+09 1.000000e+00 1.000000e+00...
1
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.
Try Free →