On 7/10/2023 12:03 PM, Miroslav Lichvar wrote:
> On Mon, Jul 10, 2023 at 11:18:36AM +0200, Maciek Machnikowski wrote:
>> Do you mean the one in clock.c? If so, the clock_stats_display resets
>> them, so there's no way of printing the stats from a whole run -
>> especially if we want to add some
On Mon, Jul 10, 2023 at 11:18:36AM +0200, Maciek Machnikowski wrote:
> Do you mean the one in clock.c? If so, the clock_stats_display resets
> them, so there's no way of printing the stats from a whole run -
> especially if we want to add some periodic read of these stats.
The logged stats can be
On 7/10/2023 10:33 AM, Miroslav Lichvar wrote:
> On Mon, Jul 03, 2023 at 04:18:57PM +0200, Maciek Machnikowski wrote:
>> Currently running servo reports current offsets in numerous tools, but lacks
>> statistical data. Having the basic statistical data makes it easier to
>> monitor
>> running s
On Mon, Jul 03, 2023 at 04:18:57PM +0200, Maciek Machnikowski wrote:
> Currently running servo reports current offsets in numerous tools, but lacks
> statistical data. Having the basic statistical data makes it easier to monitor
> running servo (especially on long runs) and determine servo performa
