With the current logging implementation, once a log is started, it will continue until one of two events:
The log gets full (100k samples)
The user calls stop
We should add a third option where the user can specify a logging duration and the code will automatically stop recording samples after this happens. This will be more accurate than timing it in Python.
This would be a nice feature and the Python API wouldn't have to change at all. The API already has a logger.log(duration = 1) sort of function. You would just have to change the internals of the function.
With the current logging implementation, once a log is started, it will continue until one of two events:
We should add a third option where the user can specify a logging duration and the code will automatically stop recording samples after this happens. This will be more accurate than timing it in Python.