DynamicsAndNeuralSystems / DynamicsAndNeuralSystems/pyhctsa
is range_evolve a good measure for stationarity?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 151
- Forks
- 13
- Avg merge
- 1m
- Merged PRs (30d)
- 21
Description
I used your package to extract features from a timeseries. I managed to reduce the classification to just 10 features. Among them was the SY_RangeEvolve totnuq feature. After visually checking validation data after classification I noticed the strange behavior of this feature.
Suppose I have two signals
Signal (y): [10, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
Reversed Signal (y rev ): [10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, 10]
The reversed signal is the normal signal but just reversed.
The totnuq of the first signal is 2 and the totnuq of the reversed signal is 11. It seems strange to me that a measure for stationarity depends so much on this.
Can't you add an option to do range_evolve once on a normal segment and then on a reversed segment. And then select the maximum of the two?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the SY_RangeEvolve feature and reproduce the reported totnuq values for the normal and reversed signals. Determine how the proposed normal-and-reversed calculation should be exposed, then verify that the selected result matches the requested behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100