Liezl Maree

Hi @Lauraschwarz, I see in both cases this has appeared when using a `TopDownMultiClassInferenceModel` - I unfortunately do not have any multi-class models in my own inventory. If I am...

Hi @Lauraschwarz, I am still working on recreating the bug during training; however, from the above updates (namely UPDATE 3), I have found that inference alone does not like to...

Hi @YiLin-Zhou, I have been looking into the problem (which seems to be a follow-up error to #1287) and am working on a solution. Thanks for submitting the issue! Liezl

Hi @hemanyaradadia, We have run into this before, and the issue seems to stem from the `skeleton.json` file format containing ```json "py/state": {"name": "nose", "weight": 1.0} ``` when it should...

## TLDR The change in `attrs` version used by `jsonpickle` to write/read the skeleton.json is causing problems, namely, `attrs >=22.2.0` returns the object state as a dictionary instead of a...

Hi @hemanyaradadia, This is a file format compatibility issue that will be officially addressed in our future release (by constraining the version of `attr` used and/or moving away from `jsonpickle`...

> Hi @roomrys, > > Thanks for the reply. The skeleton file I am using was created on the mentioned Windows 10 computer. I had installed SLEAP using conda from...

We have released SLEAP 1.3.4 (off [#1927](https://github.com/talmolab/sleap/pull/1927)) which adds additional dependency constraints to prevent this from happening, but we are also switching to manually handling the `Skeleton` (de)serialization #1934 (including...

Long awaited, but finally integrated. We've switched to manual skeleton (de)serialization in SLEAP 1.4.1.

## Analysis After taking a look at the code it seems that we use the `save_visualizations` not to save visualizations post-training, but to save visualizations during training so that the...