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
Hi there!
Problem: when we are running the anipose steps in the newest environment (test_3), it will perfectly do almost all steps. However, anipose will create videos with 'white' markers in the video-labeled folder. The constrains seems good to me, but the labels I set behind scheme in the config.toml file, are not color-coded. Besides the fact that it doesn't look beautiful, I was wondering if it does not effect the movements? which error is behind this occurence? Does it have effect on the output? If I run the analyze step in the environment anipose081, the labels will be color-coded, however we do not prefer this one.
I hope others are familair with this appearance, or anyone knows where the issue might come from.
The text was updated successfully, but these errors were encountered:
Sorry for the confusement, but I am working with an interdisciplinairy team, and I thought that there are excisting anipose environment which you can download straight-away. However, my colleague did create those test_3 and anipose081 environments. The anipose081 is not giving satisfying results, however test_3 fulfills all needs except for the above described issue. Hope someone can still answer the question
Hi there!
Problem: when we are running the anipose steps in the newest environment (test_3), it will perfectly do almost all steps. However, anipose will create videos with 'white' markers in the video-labeled folder. The constrains seems good to me, but the labels I set behind scheme in the config.toml file, are not color-coded. Besides the fact that it doesn't look beautiful, I was wondering if it does not effect the movements? which error is behind this occurence? Does it have effect on the output? If I run the analyze step in the environment anipose081, the labels will be color-coded, however we do not prefer this one.
I hope others are familair with this appearance, or anyone knows where the issue might come from.
The text was updated successfully, but these errors were encountered: