sktime/sktime

[ENH] Migrate mvts_transformer classifier from old `_pytorch.py` to new `_base_torch.py` interface

Open

#9,324 opened on Feb 5, 2026

View on GitHub
 (4 comments) (0 reactions) (1 assignee)Python (1,192 forks)batch import
enhancementgood first issuemodule:classificationmodule:deep-learning&networks

Repository metrics

Stars
 (7,162 stars)
PR merge metrics
 (Avg merge 26d 10h) (86 merged PRs in 30d)

Description

Is your feature request related to a problem? Please describe.

This is a sub-issue of #8699 Migrate the mvts_transformer classifier (implemented in sktime/sktime/classification/deep_learning/) from the old _pytorch.py to new _base_torch.py interface.

Describe the solution you'd like

Currently MVTSTransformerClassifier class inherits from BaseDeepClassifierPytorch class implemented in sktime.classification.deep_learning._pytorch.

Change the inheritance to BaseDeepClassifierPytorch class implemented in sktime.classification.deep_learning.base and ensure non-breakage of current behaviour. If there is a breakage, investigate and implement the fix for a successful migration.

Expectations of the task:

  • Compare the _pytorch.py with _base_torch.py and share your observations on places where there are differences and possible chances of breakage when migrating the mvtc_transformer classifier.
  • Thoughts/ideas on addressing those differences/breakages.
  • Corresponding implementation for the successful migration.

Contributor guide

Research direction
Compare the old ` pytorch.py` base class with the new ` base torch.py` base class to identify differences in method signatures, forward logic, and training loops. Note any breaking changes in the parent class that affect the `MVTSTransformerClassifier`. Then implement the migration by updating inheritance and ensuring all methods are compatible, running existing tests to verify no breakage.
Tech stack
pythonpytorch
Domain
machine learning
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonPyTorch
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60