#1180 Time range setting still not right (with quotes even)

5.0
closed-works-for-me
nobody
None
5
2013-04-08
2012-10-09
Craig DeForest
No

(I switched from dumb to png for clarity...)

Setting a time range in date plotting mode yields a plotting range that is not the one requested (it is smaller). Here, I request a plot from the epoch to my wedding date. It works fine with autoscaling, but if I request the same instant with range specification it only goes to 1-Jan-2003.

There is an ancillary problem, which is that dates are frequently cut off on the first plot in date format (visible in "norange.png").

Script below; output attached.

[dhcp-10-72:~] zowie% gnuplot

G N U P L O T
Version 4.6 patchlevel 0 last modified 2012-03-04
Build System: Darwin x86_64

Copyright (C) 1986-1993, 1998, 2004, 2007-2012
Thomas Williams, Colin Kelley and many others

gnuplot home: http://www.gnuplot.info
faq, bugs, etc: type "help FAQ"
immediate help: type "help" (plot window: hit 'h')

Terminal type set to 'aqua'
gnuplot> set terminal png
Terminal type set to 'png'
Options are 'nocrop font "Arial,12" fontscale 1.0 size 640,480 '
gnuplot> set output "norange.png"
gnuplot> set timefmt "%s"
gnuplot> set xdata time
gnuplot> set xtics scale default format "%m/%Y" rotate by -90
gnuplot> set title "No range (autoscale): 1-Jan-1970 -- 31-May-2003"
gnuplot> plot "-" using 1:2 notitle with lines
input data ('e' ends) > 0 0
input data ('e' ends) > 1054404000 1
input data ('e' ends) > e
gnuplot> set output "range.png"
gnuplot> set title "Range (same as data): 1-Jan-1970 -- 31-May-2003"
gnuplot> plot ["0":"1054404000"] "-" using 1:2 notitle with lines
input data ('e' ends) > 0 0
input data ('e' ends) > 1054404000 1
input data ('e' ends) > e

Discussion

  • Craig DeForest
    Craig DeForest
    2012-10-09

    Two plots showing the bug in time ranging

     
    Attachments
  • Ethan Merritt
    Ethan Merritt
    2013-04-08

    • status: open --> closed-works-for-me
    • milestone: --> 5.0
     
  • Ethan Merritt
    Ethan Merritt
    2013-04-08

    I can't reproduce this error.
    Tested 4.6.0 (as shown in the bug report), 4.6.1, 4.6.2 and current cvs.

    In any event, the time handling has been changed in the cvs version so I'd want a bug report specifically against the modified code before trying to pursue it.