|
From: Ethan M. <eam...@gm...> - 2022-06-24 18:10:04
|
On Friday, 24 June 2022 01:30:25 PDT Emanuel Berg wrote:
>
> But how will one get infamation on the x-axis?
>
> It should start either at 2022-01-10 and then +7 days for
> every xtick, or it can start with 148 also with +7 days
> per step.
>
> In the shell (shell-mode) it works using
> 'date +"%Y-%m-%d"' or 'date +"%j"' if that helps ...
>
> It would be better to automate it than hard code it but
> actually hard-code would also be an improvement at this stage.
I draw your attention to these possibly relevant changes to gnuplot
from last year. These are in the development code but not in the
current version 5.4 release. Is there interest in having these changes
back-ported to 5.4?
commit a8a8a88d77a77f3af047f5b4d0444737a6837c67
Author: Ethan A Merritt <merritt@u.washington.edu>
Date: Mon Jun 14 15:03:25 2021 -0700
"set mxtics time <N> <units"
Allow explicit choice of minitic placement along time axis.
For example
set mxtics time 1 month
places a minitic exactly on the 1st day of Feb/Mar/Apr even
though this does not correspond to equal intervals measured in days.
commit 529062ae873901010d138e68897d8f6d057a8e7a
Author: Ethan A Merritt <merritt@u.washington.edu>
Date: Tue Jun 15 22:19:08 2021 -0700
Revise auto-placement of tics for time data
For timescales of days or longer, if a ticmark is generated for
some date then place it at the start of that same day (0 AM).
The spacing between "day" tics is always exactly N days.
It used to be that the date was rounded up if time > 22:00 but
hours/minutes/seconds were left unchanged. This meant that the
tic positions were not exactly on a day boundary and might not
even be on the same day. Thus the spacing between "dates" was not
an integral number of days.
This discrepancy was particularly obvious when using the new
option "set minitics time N days", since the evenly spaced
minitics did not align with the major tics.
|