Tbx11k

@ogueler, @guelero: we need to merge this branch as there is some clean-up work stacked up in merge-request !4 (merged) that will eventually affect the merge-ability of this work.

@dcarron will try to adapt changes to the latest updates in !4 (merged) to speed-up this convergence.

I am assuming the dist is failing because of the new changes that are already made in the dev-profile?

If that is the case, then I am also assuming this would be fixed if !4 (merged) is also merged afterwards.

How should we proceed?

Hello Özgür, I can make the necessary changes to merge the branch. From what I can see you added a new dataset and there is no change in the models and engine so it shouldn't be a problem.

I'll merge it on the move-to-lightning branch so it does not cause issues later.

The issue happened because the pytorch-lightning package was renamed to lightning. The branch has been merged on !4 (merged) and the CI passes.

added 7 commits

• a6ff407d - added RS datasets for tbx11k
• 37b723ca - completed documentation for tbx11k
• 78010d30 - added complete tbx11k dataset to project .toml
• 727dfa94 - added tests for all tbx11k configs
• 47647a7c - fixed formatting in tests
• 5f644c0a - fixed wrong paranthesis
• 9b297231 - removed unusable tbx11k custom split 3

Compare with previous version

added 1 commit

• 2271683d - fixed small bugs in documentation

Compare with previous version

added 1 commit

• f9a3e2d0 - more doc bug fixes

Compare with previous version

added 1 commit

• 2577fb3c - more doc bug fixes

Compare with previous version

changed target branch from main to move-to-lightning

approved this merge request

marked this merge request as ready

mentioned in commit f87e433e

merged