Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aeon v1.0.0 Checklist #1518

Open
15 of 25 tasks
MatthewMiddlehurst opened this issue May 12, 2024 · 3 comments
Open
15 of 25 tasks

aeon v1.0.0 Checklist #1518

MatthewMiddlehurst opened this issue May 12, 2024 · 3 comments
Labels
release Release related

Comments

@MatthewMiddlehurst
Copy link
Member

MatthewMiddlehurst commented May 12, 2024

Describe the issue

A checklist of large-scale changes to be made for an eventual version v1.0.0

Must Have

  • Remove current forecasting and BaseTransformer functionality
  • Remove the datatypes module
  • Merge BaseEstimator and BaseObject
    • consider deprecation for a few of the currently available methods
  • Replace current fixture/scenario based testing with a simplified testing suite.
    • Remove experimental tag for testing
    • Remove currently excluded tests where possible
  • Consider removing experimental tag for other modules
  • Complete any outstanding deprecation acts
    • CNN Regressor
    • CNN Classifier
    • CNN Network
    • Kmeans
    • K-shapes
    • AEFCN
    • BaseDeepClusterer
    • WeightedEnsembleClassifier
  • Check through docs for incorrect statements, links etc
  • Refactor distances module
  • Make numpy 2.0 compliant [ENH] Numpy 2 compatibility #2218

Could have

@MatthewMiddlehurst MatthewMiddlehurst added the release Release related label May 12, 2024
@TonyBagnall
Copy link
Contributor

we can do these things before going to 1.0.0. Personally I think 1.0.0 should come at the end of the grant

@MatthewMiddlehurst
Copy link
Member Author

I think deprecating a whole module is a big enough of a change to warrant it. I don't know what would be if not. I think it's best just to get these big ones out at the same time.

@chrisholder
Copy link
Contributor

chrisholder commented Oct 1, 2024

I think before 1.0 we should add I better directory structure to the distance module. Currently it's just one flat directory.

Currently I was thinking we should have something like:

-> Elastic
-> Cross-Correlation
-> Lp (or a better name to describe non time series distances like Euclidean)
-> then either one or multiple directories for distances like dtt_sfa, sax and mpdist which I don't know how/where they would fall into

Will post in the distance channel

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Release related
Projects
None yet
Development

No branches or pull requests

3 participants