Timestamp range in gnuplot

June 20th, 2011
gnuplot, tech
In gnuplot, you might have some data you'd like to graph that has timestamps:
     1308369601 0.15
     1308369661 0.05
     1308369721 0.43
     1308369781 0.41
     ...
  
You can see many places that to tell gnuplot your xaxis is in seconds since the epoch you use:
     set xdata time
     set timefmt "%s"
     set format x "%H:%M"     # or anything else
     set xlabel "time"
  
If you want to limit the range, you might think you could do something like:
     set xrange [1308369932:1308373241]
  
If you try this, you'll get an error like:
     "plot.gnp", line 16: all points y value undefined!
  
To fix this, you need to subtract 946684800 from the start and end of your xrange:
     set xrange [1308369932-946684800:1308373241-946684800]
  
What is going on here? It turns out that unlike everything sensible in the unix world, gnuplot calculates time in seconds since the beginning of the year 2000 instead of the year 1970. So it interprets [1308369932:1308373241] as early morning 2041-06-17 instead of early morning 2011-06-18. The magic number, 946684800, is the number of seconds between 2000-01-01 and 1970-01-01.

I understand gnuplot was trying to be platform independent, but it's pretty annoying now that the 1970 epoch has become dominant.

Comment via: substack

Recent posts on blogs I like:

On AI writing in 2026

I use AI to write a little bit: I ask it for high level feedback on blog post drafts, make mechanical edits, and sometimes use it to brainstorm options for wording at a paragraph level. It’s unusual that I accept its wording or changes without modificatio…

via Home April 16, 2026

Some considerations on whether my job is evil

I. On an average weekend, only 1 in 20 Americans go to a party.

via Thing of Things April 14, 2026

Microfictions

A few microfictions, very much inspired by Quiet Pine Trees. I hope to add more over time. No LLMs.

via Evan Fields March 27, 2026

more     (via openring)