> The idea behind n_epochs is that it allows you to pass RtEpochs to
> functions that are not designed for real-time applications in mind , e.g.,
> spectral_connectivity, so they return after a certain number of epochs have
> been received and processed. Together with consume_epochs=False, one can
> implement "moving-average type" operations, e.g., one use n_epochs=10 and
> then compute connectivity, use remove_old_epochs to remove the oldest epoch
> and compute connectivity again. Like that the connectivity estimate will
> always be computed over 10 epochs and updated as soon as a new epoch has
> been received.
>
> Maybe this is too complicated, but I do think it is useful to be able to
> pass the RtEpochs to non real-time functions.

I agree with that but it's still unclear to me how this is going to fly.
When does RtEpochs know when to stop the iteration? When happens
after 5 ou 10 epochs? We recall the connectivity function on the same
instance?