Currently find_optimal_lag evaluates all user-specified lags and returns the one with the best p-value. This is correct but can be costly for many lags. A few other approaches from the literature:
Adding an alternative strategy behind a lag_selection parameter would be a larger change, but would open up new usage groups.
If you are interested it, please react here or add a comment with suggestions.
Currently
find_optimal_lagevaluates all user-specified lags and returns the one with the best p-value. This is correct but can be costly for many lags. A few other approaches from the literature:Adding an alternative strategy behind a
lag_selectionparameter would be a larger change, but would open up new usage groups.If you are interested it, please react here or add a comment with suggestions.