3 ms·

Supporting different y-axis ranges is something we can add, and I was already thinking of adding a 1ms range for visualizing low-level CPU cycle activities (whi

Supporting different y-axis ranges is something we can add, and I was already thinking of adding a 1ms range for visualizing low-level CPU cycle activities (which span nano and microseconds). I like the idea of 16ms for 60fps analysis, where every column is one frame. Could help game development. :)

saulrh 9y ago
Actually, seeing the diagonal stripes in the examples [1], maybe it'd be useful to have a mode that lets you rescale the axes to line the stripes up? If you're using this to inspect patterns, it seems to me that the most useful time scale would not be a nice round human number, it'd be one that matches well with the patterns you're trying to inspect - one period, not one second. Way out in the distance, maybe even a variable-interval mode, where you can click-select blocks and each one is given its own column, so you can directly compare them without the dead space in the middle and starting from the same baseline? [1] Particularly striking: https://cdn-images-1.medium.com/max/2000/1*EypUnkPtayeKr9bJuvgNEg.png https://cdn-images-1.medium.com/max/2000/1*EypUnkPtayeKr9bJu...
- Scaevolus 9y ago
  You could autoscale the y axis to whatever makes the columns have the most similarity (minimize squared differences).
  - simsla 9y ago
    Rather than lsq, you could use autocorrelation within rows to line them up.
    - rakoo 9y ago
      This thing is extremely periodic. You should do an FFT, there should be a peak that's more obvious than the others. That's your frequency and thus your period.