michaelforney
NINJA_STATUS %o, %c
Are there any limitations preventing the implementation of %c, %o rate info in NINJA_STATUS, or ware they drop intentionally.
I don't think there is any limitation preventing their implementation. Maybe @E5ten can comment about why those were excluded.
Any patches are welcome.
How would %c be implemented in particular? Keeping track of the number of edges finished over the last second? That is a whole number rather than a float, but Ninja seems to use a float for %c.
We might also keep track of the time between the last two finished edges. Then 1/(time between last two, i.e. 0.2 sec) = rate (e.g. 5 edges/sec), or average over the times between the last 3, 4 finished etc. Can't fully understand what the ninja manual says.
