Migrate Anemoi Training, Model, and Graphs to a Mono-Repo structure here.

[JesperDramsch]

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

In a collaboration between @MeraX, @einrone, @frazane we were working to migrate the existing repository with tight coupling into a more developer friendly structure.

Describe the solution you'd like

Use Git subtrees to build a standalone migration of the individual repositories in this repository.

The beauty of subtrees is that we can use them to keep the repos in sync while we migrate and development is on-going. They maintain the history. But they do not add more metadata to the repo. After the initial transition phase, this repo can then function as a standalone repo.

Describe alternatives you've considered

Using merges and squashed histories, but it is important to maintain the history and authorship of this work.

Additional context

@MeraX has documented all the work and scripts from our meetings in https://github.com/MeraX/join_single_repos
This also provides utilities to migrate existing branches for individual pull requests.

Organisations

@DeutscherWetterdienst, @metno, @MeteoSwiss, @ecmwf

Current Work Plan Outline:

Migrate Code

• Migrate Training Code
• Migrate Models Code
• Migrate Graphs Code
• Remove .github folder in Training Code
• Remove .github folder in Models Code
• Remove .github folder in Graphs Code

Archival and Notice

• Create release on anemoi-training
• Create release on anemoi-models
• Create release on anemoi-graphs
• Add notice to Anemoi Training Readme linking here
• Add notice to Anemoi Models Readme linking here
• Add notice to Anemoi Graphs Readme linking here
• Archive anemoi-training
• Archive anemoi-models
• Archive anemoi-graphs
• Communicate across Anemoi users and MLPP and ATS

Issues

• Transfer all Issues of Anemoi Training
• Transfer all Issues of Anemoi Models
• Transfer all Issues of Anemoi Graphs

ReadTheDocs

• Redirect RTD here for Training
• Redirect RTD here for Models
• Redirect RTD here for Graphs

Pull Requests

• Provide scripts to transfer branches to developers
• Add better documentation for the transfer process
  Developers will re-open pull requests individually on this new repo.

.github Folder

We will hold off from creating the .github folder with all necessary files for Automation, CIs, Releases, owners and release on the initial release to sped up the migration. These will be created in individual PRs afterwards.

[JesperDramsch]

Monorepo Migration Notes

This repository was created by merging several independent repositories. The following additional changes were made:

1. Repository Structure

   • Removed duplicate .github folders from sub-projects
   • Reorganized Git tags to follow new monorepo structure (tags: 1.2.3 → component/1.2.3)

2. Build System

   • Restructured pyproject.toml for monorepo compatibility
   • Updated version management to work with subfolder projects

3. Development Setup

   • Moved .pre-commit-config.yaml to root
   • Configured isort to handle multi-project imports correctly
   • Set src_paths and known_first_party in .isort.cfg for proper import sorting

4. Documentation

   • Adjusted readthedocs configuration for subfolder projects
   • Updated sphinx config to handle new project structure
   • Modified doc paths to reflect new monorepo layout