Kristian Agasøster Haaga
Kristian Agasøster Haaga
There's been quite some discussion around this paper, and a number of interesting complexity measures that we haven't yet implemented are mentioned in the critiques of the paper. We should...
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
This would not be breaking, so should be fine. Either alternative is good with me.
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
Are you on it, or should I do it, @Datseris ?
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
Note that we also need to change `BubbleSortSwapsEncoding`, because it uses the same syntax.
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
Actually, the syntax `OrdinalPatternEncoding(m=3)` already works - we did that for backwards compatibility when releasing 3.0. We just need to update the docstring.
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
For `BubbleSortSwapsEncoding`, we _do_, however, need another constructor
Syntax with type parameter `{m}` in `OrdinalPatterns` is not harmonious with the rest of the library
Decision to be made: should `m`, `tau`, etc be keywords or positional arguments? Currently we have ```julia Dispersion(; c = 5, m = 2, τ = 1, check_unique = true)...
> Note that this is only a problem if there are duplicate datapoints in the timeseries. The problem occurs if there are tied values inside any state vector, since it...
Further info: `AbstractDataset`/`Dataset` is found in the StateSpaceSets.jl package. However, these types are going to change names in the StateSpaceSets.jl, so whoever implements need to use the correct name for...
> The type PowerLawSpectrum can either has as input the input timeseries, in which case it deduces beta by doing a linear fit to the power spectrum, or it could...