You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @philipperemy, I found this library very interesting but have a question. The code currently sets a limit on the precision which is 100us, but from what I read, I don't think it is necessary to apply the same restriction on the data as well? It seems to me that the precision is only used for search through the lag range and the covariance is estiamted using data with nanoseconds timestamp as index anyway. So is that possible to let the input data as is? This would be particularly useful when you want to iterate a bigger step and data resolution is much finer, say in nanoseconds.
The text was updated successfully, but these errors were encountered:
Hi @philipperemy, I found this library very interesting but have a question. The code currently sets a limit on the precision which is 100us, but from what I read, I don't think it is necessary to apply the same restriction on the data as well? It seems to me that the precision is only used for search through the lag range and the covariance is estiamted using data with nanoseconds timestamp as index anyway. So is that possible to let the input data as is? This would be particularly useful when you want to iterate a bigger step and data resolution is much finer, say in nanoseconds.
The text was updated successfully, but these errors were encountered: