Closed juanCantz closed 1 month ago
Sorry, this kind of got lost during time busy bits. @hadifawaz1999 is this related to the saving and loading issues we were having?
Sorry, this kind of got lost during time busy bits. @hadifawaz1999 is this related to the saving and loading issues we were having?
no it isnt its just about always adding the modelcheckpoint callback by default, forgot to work on that, can take care of it
is this a bug or a feature request?
is this a bug or a feature request?
it is a bug yes, i should fix it but still havent done it yet
but a bug in very specific case
that can be simply avoided by passing the modelcheckpoint manually by the user, just should have it by default always internal
Describe the bug
Hello all, using the available classifiers (like the InceptionTimeClassifier), I want to keep track of the loss during training and I am having issues doing that. The objective is to track loss like in the picture:![Figure 8](https://github.com/aeon-toolkit/aeon/assets/90686979/150eab9a-cf61-42d9-a6c0-7f425f003688)
I am trying to use keras callbacks but it throws an error, and I can not access history since there is no history available according to docs https://www.aeon-toolkit.org/en/latest/api_reference/auto_generated/aeon.classification.deep_learning.InceptionTimeClassifier.html#aeon.classification.deep_learning.InceptionTimeClassifier
The error and code are shared below.
(The question of accessing the training history was solved by Ali El Hadi Ismail Fawaz and Tony Bagnall in the aeon slack (thanks for that), just putting up the issue as asked to fix the OSError exception)
The answer to the question was: So to access the history of each Individual Inception trained models. You will have to do the following, for instance to get the history of the first inception model trained in your ensemble.
Steps/Code to reproduce the bug
Expected results
Successful training with application of the described callback function.
Actual results
Versions