Databases
StackOverflow2013
Postsdbo
POR Plot Specify number of time tickmarks - time/date equivalent to pretty
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
    primarykey
    data
    text
    <p>I was wondering how I could plot more tick marks when plotting time on the x-axis.</p> <p>Basically, a time equivalent to pretty. Pretty obviously doesn't work so well with times, as it uses factors of 1,2,5 and 10. For time one probably wants e.g. hours, half hours, ...</p> <pre><code>plot(as.POSIXct(x,origin="1960-01-01"),y,type="l",xlab="Time") </code></pre> <p>gives really too few and widely spaced tickmarks.</p> <pre><code>zoox&lt;-zoo(y,as.POSIXct(stats$Time,origin="1960-01-01")) plot(zoox) </code></pre> <p>gives the same.</p> <p>Thanks</p> <p>EDIT:</p> <p>Just to clarify (so far answers don't address my issue): What I am looking for is a function like pretty for dates, e.g. a function, that takes a start date, an end date, a number of ticks, and outputs the location of the ticks. That is, I am well aware it is possible to plot hours, to plot minutes, and what else, but pretty automates the tick distance for numbers, and a resulting function for dates should decide by itself whether to use days, hours, minutes, second, milliseconds, microseconds, 30 minutes, 500 micros, 5 seconds, etc. intervals. That is what pretty does for numbers, anyway.</p> <p>EDIT2:</p> <p>This is the function I currently use to decide the format for the time axis (note that this doesn't work for dates):</p> <pre><code>mydiff &lt;- end-start if(mydiff&gt;1800) { axis.POSIXct(1,xrange,format="%H:%M") } else if(mydiff&gt;30) { axis.POSIXct(1,xrange,format="%H:%M:%S") } else if(mydiff&gt;0.5) { axis.POSIXct(1,xrange,format="%H:%M:%OS3") } else axis.POSIXct(1,xrange,format="%H:%M:%OS6") } </code></pre> <p>I don't have a function that increase tick marks, so I use the default number of tick marks</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USInfinite Recursion
    1. USCookie
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. This table or related slice is empty.
      1. VTUpMod
    1. COR's internal functions will not consider time units lower than the second. The `POSIXct` class can deal with decimal seconds, but the helper functions around this class generally only work at the second level. So the microsecond interval will really be in decimal seconds **and** have to be handled by hand.
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. USGavin Simpson
    2. CO@GavinSimpson: Untrue, at least on my system micros work perfectly. Use `axis.POSIXct(1,xrange,format="%H:%M:%OS6")` to display them in the chart. Let me make another edit with an appropriate function. While the unit is seconds, it is a double value, and has quite high precision.
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. USCookie
    3. CODoes `library(xts); ?axTicksByTime`, or `quantmod:::axTicksByTime2` do what you want?
      singulars
      1. POR Plot Specify number of time tickmarks - time/date equivalent to pretty
      1. USGSee
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload