You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+20-5Lines changed: 20 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,23 @@
1
1
# Changelog
2
2
3
-
Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and
3
+
Observes [Semantic Versioning](https://semver.org/spec/v2.0.0.html) standard and
4
4
[Keep a Changelog](https://keepachangelog.com/en/1.0.0/) convention.
5
5
6
+
7
+
## [0.3.0] - 2025-06-07
8
+
9
+
+ Feat - Created new `SelectedFullFit` table to register selected trained models for downstream inference
10
+
+ Feat - Updated pipeline architecture by inverting dependency direction:`moseq_infer.PoseEstimationMethod` is moved from `moseq_infer` to `moseq_train` and now the new table `SelectedFullFit` is a nullable foreign key in `moseq_infer.Model`.
11
+
+ Fix - Updated imports and foreign key references across schemas to match new structure.
12
+
+ Fix - `pre-commit` hooks to exclude removal of used dependencies into the table definitions (`F401`).
13
+
+ Add - Refactored `setup.py` to organize dependencies more cleanly and into optional dependencies.
14
+
+ Add - Refactored schema activation logic.
15
+
+ Add - Adjusted `tutorial_pipeline.py` to reflect the new hierarchy
16
+
+ Add - Aligned schema design with DataJoint Element conventions to support modular reuse and testing
17
+
+ Add - Update `images` according to these changes
18
+
+ Add - Update `tutorial.ipynb` to reflect these changes.
1. We recommend you start by navigating to the `notebooks` directory on the left panel and go through the `tutorial.ipynb` Jupyter notebook. Execute the cells in the notebook to begin your walkthrough of the tutorial.
74
74
75
-
2. Once you are done, see the options available to you in the menu in the bottom-left corner. For example, in Codespace you will have an option to `Stop Current Codespace` but when running Dev Container on your own machine the equivalent option is `Reopen folder locally`. By default, GitHub will also automatically stop the Codespace after 30 minutes of inactivity. Once the Codespace is no longer being used, we recommend deleting the Codespace.
75
+
2. Once you are done, see the options available to you in the menu in the bottom-left corner. For example, in Codespace you will have an option to `Stop Current Codespace` but when running Dev Container on your own machine the equivalent option is `Reopen folder locally`. By default, GitHub will also automatically stop the Codespace after 30 minutes of inactivity. Once the Codespace is no longer being used, we recommend deleting the Codespace.
0 commit comments