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
Merge pull request #224 from dattalab/dev (Keypoint-MoSeq 0.6.0)
- Brand new calibration widget that relies on fewer dependencies and is therefore more stable.
- Added functions for manually merging similar syllables after modeling.
- Fixed bug where the mice would not be properly aligned in side-view when generating grid movies of 3D keypoints.
- More detailed memory requirements in documentation [here](https://keypoint-moseq.readthedocs.io/en/latest/FAQs.html#out-of-memory)
- 'pre' and 'post' parameters for syllable visualization functions are now defined in seconds rather than frames. FPS for a dataset is now defined in the config file.
- Batch size automatically determined for input data rather than being hard-coded to maximize memory efficiency by minimizing unnecessary zero-padding.
- Noise added to data during preprocessing is now deterministic for easier debugging.
- Only open a file handle to one video at a time when generating grid movies to avoid max open file handle errors.
Copy file name to clipboardExpand all lines: docs/source/FAQs.rst
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,6 +393,12 @@ Users occasionally find that the trajectory plot and grid movie for a given syll
393
393
Density sampling is a way of selecting syllable instances that are most representative relative to the full dataset. Specifically, for each syllable, a syllable-specific density function is computed in trajectory space and compared to the overall density across all syllables. An exemplar instance that maximizes the ratio between these densities is chosen for each syllable, and its nearest neighbors are randomly sampled. When the distribution of trajectories for a syllable is multimodal (i.e., it represents a mixture of distinct behaviors), the examplar syllable may not capture the full range of behaviors, or it may jump from one mode to another when an existing model is applied to new data. In these cases, it may be better to sample syllable instances uniformly by setting turning off density sampling as shown above.
394
394
395
395
396
+
Two different syllables look very similar. Is there a way to consider them as one syllable?
Yes, see the :ref:`Merging similar syllables <merging-syllables>` section in the Advanced Usage guide for instructions on how to combine syllables that represent the same behavior.
In some cases it may be convenient to combine syllables that represent similar behaviors. Keypoint-moseq provides convenience functions for merging syllables into user-defined groups. These groups could be based on inspection of trajecotry plots, grid movies, or syllable dendrograms.
351
355
356
+
.. code-block:: python
357
+
358
+
# Define the syllables to merge as a list of lists. All syllables within
359
+
# a given inner list will be merged into a single syllable.
360
+
# In this case, we're merging syllables 1 and 3 into a single syllable,
361
+
# and merging syllables 4 and 5 into a single syllable.
362
+
syllables_to_merge = [
363
+
[1, 3],
364
+
[4, 5]
365
+
]
366
+
367
+
# Load the results you wish to merge (change path as needed)
0 commit comments