<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 2864: logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/" rel="alternate"/><link href="https://sourceforge.net/p/gnuplot/bugs/2864/feed.atom" rel="self"/><id>https://sourceforge.net/p/gnuplot/bugs/2864/</id><updated>2026-03-25T17:18:21.813000Z</updated><subtitle>Recent changes to 2864: logscale issue in tics</subtitle><entry><title>#2864 logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/?limit=25#6641/3996" rel="alternate"/><published>2026-03-25T17:18:21.813000Z</published><updated>2026-03-25T17:18:21.813000Z</updated><author><name>Ethan Merritt</name><uri>https://sourceforge.net/u/sfeam/</uri></author><id>https://sourceforge.netd60c6b5e3ffda8c977615401a6f101bb977519f3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, the behavior has changed since version 5.  User feedback (a.k.a. "bug reports") suggested revisions to the empirical rules for log tic placement.  See in particular the discussion attached to Bug #2717&lt;br/&gt;
&lt;a href="https://sourceforge.net/p/gnuplot/bugs/2717/"&gt;https://sourceforge.net/p/gnuplot/bugs/2717/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Some users feel strongly that there must be at least three major (i.e. labeled) tic marks in order to make it immediately apparent that the axis is log-scaled.  The output from 5.4 on plot #2 has only two labeled tic marks. In this particular case close inspection of the unlabeled minor tic marks does help with visual recognition of log scaling.  In other cases the minor tics were less helpful or even incorrect.&lt;/p&gt;
&lt;p&gt;Other possibly relevant bug reports that resulted in code revisions&lt;br/&gt;
&lt;a href="https://sourceforge.net/p/gnuplot/bugs/2372"&gt;https://sourceforge.net/p/gnuplot/bugs/2372&lt;/a&gt;&lt;br/&gt;
&lt;a href="https://sourceforge.net/p/gnuplot/bugs/2856/"&gt;https://sourceforge.net/p/gnuplot/bugs/2856/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;There is always room for improvement, and retaining or at least allowing backwards compatibility with earlier gnuplot versions is a priority,  So perhaps we could add or tweak something to allow the user to force the old version 5 logscale tic placement.  I'll think about it. For example &lt;code&gt;set ytics nolog&lt;/code&gt; forces linear placement (increment is additive rather than multiplicative) but &lt;code&gt;set ytics log&lt;/code&gt; is not forcing; it is interpreted as meaning "use the default log tic placement" and allows the program to in fact revert to linear placement in accordance with the default empirical rules.   Probably these command would better have been &lt;code&gt;set ytics {no}linear&lt;/code&gt; but it's too late for that.    &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#2864 logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/?limit=25#b577" rel="alternate"/><published>2026-03-25T15:21:21.973000Z</published><updated>2026-03-25T15:21:21.973000Z</updated><author><name>zcy</name><uri>https://sourceforge.net/u/zcycat/</uri></author><id>https://sourceforge.net614a731cd8393e5484049370bb2351a6a3075262</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Group&lt;/strong&gt;:  --&amp;gt; &lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Priority&lt;/strong&gt;:  --&amp;gt; &lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#2864 logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/?limit=25#6641" rel="alternate"/><published>2026-03-25T14:44:20.044000Z</published><updated>2026-03-25T14:44:20.044000Z</updated><author><name>zcy</name><uri>https://sourceforge.net/u/zcycat/</uri></author><id>https://sourceforge.net1979d88cb06def2a661d65442976c3fb6d9a2706</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This behavior is different from that in the previous version (at least v5.4 as I used before, see the right panel of the figure attached).&lt;/p&gt;
&lt;p&gt;"ytics" ignored the "logscale" parameter - the tic interval was supposed to be interpreted as a multiplicative factor rather than a constant.&lt;/p&gt;
&lt;p&gt;Would like to clarify if this is a new feature or a bug? Thanks!&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;gnuplot&amp;gt; set log y
gnuplot&amp;gt; set yrange [5:1e2]
gnuplot&amp;gt; set ytics 10,10,1e3 logscale
gnuplot&amp;gt; set mytics 10
gnuplot&amp;gt; p x
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;</summary></entry><entry><title>#2864 logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/?limit=25#8259" rel="alternate"/><published>2026-03-25T00:16:38.210000Z</published><updated>2026-03-25T00:16:38.210000Z</updated><author><name>Ethan Merritt</name><uri>https://sourceforge.net/u/sfeam/</uri></author><id>https://sourceforge.net8256d13179170a8a4ef00aacfbaec710c604f745</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Both plots show log scaling on y.  The difference you notice is probably the choice of where to place major tics (labeled) vs minor tics (unlabeled). &lt;/p&gt;
&lt;p&gt;The program tries to choose a reasonable set of major and minor axis tics based on the total range.  When placing log scaled major tics it currently uses heuristics like "there must be at least 3 but preferably not more than 10 major tics; do not place more than 10 minor tics between major tics;  if the range would hold only 1 major tic promote the minor tics to major (labeled) status".   Your pair of ranges demonstrates hitting one or another of these limiting cases. &lt;/p&gt;
&lt;p&gt;People have different, conflicting, opinions on the best choice of tic placement and labels.  The program tries to pick something reasonable but it can't match everyone's preference.  By the same token, I am not sure what you were expecting for the second plot.   If you add a command &lt;br/&gt;
&lt;code&gt;set ytics 10,10,100&lt;/code&gt;&lt;br/&gt;
it would force the same choice of major tics as used in the first plot, but for this total range they would all be crammed into the upper half of the figure.   Maybe you prefer that. In extreme cases you can specify a full set of labeled tics explicitly&lt;br/&gt;
&lt;code&gt;set ytics (1,2,5,10,20,50,100)&lt;/code&gt; &lt;br/&gt;
or whatever your preference is.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/" rel="alternate"/><published>2026-03-24T22:05:01.041000Z</published><updated>2026-03-24T22:05:01.041000Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net208915664864a9ead16ce5f7e2e00298d3f41c79</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Using version 6.0.2, logscale is not recognized for tics when the axis range limits are not exact powers of 10.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;code&gt;gnuplot&amp;gt; set log y
gnuplot&amp;gt; set yrange [5:100]
gnuplot&amp;gt; p x
gnuplot&amp;gt; set yrange [1:100]
gnuplot&amp;gt; p x
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;</summary></entry><entry><title>logscale issue in tics</title><link href="https://sourceforge.net/p/gnuplot/bugs/2864/" rel="alternate"/><published>2026-03-24T22:05:01.041000Z</published><updated>2026-03-24T22:05:01.041000Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netceae3310dc44e9d9a99e339c375bfd501f1210ed</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 2864 has been modified: logscale issue in tics&lt;br/&gt;
Edited By: zcy (zcycat)&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>