Systems Frontend issueshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues2022-12-16T11:02:21+01:00https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1877Kinesphere display in Overlay/BoundingBox should use helper functions for col...2022-12-16T11:02:21+01:00Mittermeier, MaximilianKinesphere display in Overlay/BoundingBox should use helper functions for color/label texthelper functions usage:
1. `$helpers.parseKinesphereConfidence(confidence)`:
_arguments:_ `confidence` is the object found in the kinesphere analysis reply for a certain framerange like:
```JSON
{
"narrow": 94.56,
"middle": 5.44,
...helper functions usage:
1. `$helpers.parseKinesphereConfidence(confidence)`:
_arguments:_ `confidence` is the object found in the kinesphere analysis reply for a certain framerange like:
```JSON
{
"narrow": 94.56,
"middle": 5.44,
"wide": 0.0
}
```
_return:_ value representing the kinesphere label with the highest confidence for the range
2. `$helpers.getRGBAForKinesphereValue(value)`:
_arguments:_ `value` is an output of `$helpers.parseKinesphereConfidence()`
_return:_ array representing a rgba color in the form `[red(0..255), green(0..255), blue(0..255), alpha(0..255)]` like: `[64, 0, 123, 255]`
3. `$helpers.getLabelForKinesphereValue(value)`:
_arguments:_ `value` is an output of `$helpers.parseKinesphereConfidence()`
_return:_ string representation of the kinesphere value like: `"Narrow"`Milan GressMilan Gresshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1876visualize speed/acceleration2022-12-14T23:09:02+01:00Mittermeier, Maximilianvisualize speed/accelerationhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1875visualize quantity of motion2022-12-14T23:08:49+01:00Mittermeier, Maximilianvisualize quantity of motionhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1874visualize contraction index2022-12-16T10:38:53+01:00Mittermeier, Maximilianvisualize contraction indexhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1873add duration chip is dubble now2022-12-19T21:39:53+01:00Milan Gressadd duration chip is dubble nowbroken in: `milestone-feature-data-views`
I guess that's a merge conflict? It's fine in master branch but broken in our data views branch… like both changes are applied, so now the button is dubbed
![Bildschirmfoto_2022-12-14_um_16.15...broken in: `milestone-feature-data-views`
I guess that's a merge conflict? It's fine in master branch but broken in our data views branch… like both changes are applied, so now the button is dubbed
![Bildschirmfoto_2022-12-14_um_16.15.09](/uploads/9cc792cc3cc923b655ec65c7986f37ed/Bildschirmfoto_2022-12-14_um_16.15.09.png)Feature: Data ViewsMilan GressMilan Gresshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1872Fix some Comments not showing up2022-12-14T12:18:48+01:00Mittermeier, MaximilianFix some Comments not showing uphttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1871Fix new Comments only show up on reload2022-12-14T12:40:31+01:00Mittermeier, MaximilianFix new Comments only show up on reloadhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1870transcript feature seems to be broken2023-01-12T14:44:17+01:00Hansen, Christiantranscript feature seems to be broken1. Starting the transcript feature
2. Receiving the error message below, no dialog shows up
3. The transcription process shows up as completed in /files
<br />
![Bildschirmfoto_2022-12-13_um_17.18.36](/uploads/49fddb1ea788782b1e840944bc4...1. Starting the transcript feature
2. Receiving the error message below, no dialog shows up
3. The transcription process shows up as completed in /files
<br />
![Bildschirmfoto_2022-12-13_um_17.18.36](/uploads/49fddb1ea788782b1e840944bc4907b4/Bildschirmfoto_2022-12-13_um_17.18.36.png)
<br />
![Bildschirmfoto_2022-12-13_um_17.22.25](/uploads/c1e461c8a315f031371aa4c8079e15cf/Bildschirmfoto_2022-12-13_um_17.22.25.png)Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1869CommentThread.vue reloads all comments on adding a new comment2023-01-17T15:08:38+01:00Mittermeier, MaximilianCommentThread.vue reloads all comments on adding a new commentCurrently CommentThread.vue reloads all comments when a new comment is added.
Also the comment count reported does not change properly when comments are removed.
Using a find getter to retrieve the comments would require less redundan...Currently CommentThread.vue reloads all comments when a new comment is added.
Also the comment count reported does not change properly when comments are removed.
Using a find getter to retrieve the comments would require less redundant communication with the backend and allow easier synchronisation of the comment count.https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1868"People detection" triggers "People tracking" visibility icon2022-12-14T18:56:19+01:00Hansen, Christian"People detection" triggers "People tracking" visibility icon![Bildschirmaufnahme_2022-12-12_um_17.32.25](/uploads/ffedd78e2a06d9240946c993d8d80099/Bildschirmaufnahme_2022-12-12_um_17.32.25.mov)![Bildschirmaufnahme_2022-12-12_um_17.32.25](/uploads/ffedd78e2a06d9240946c993d8d80099/Bildschirmaufnahme_2022-12-12_um_17.32.25.mov)Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1867Missing comments and issue when adding new comments2023-01-10T13:54:14+01:00Rittershaus, DavidMissing comments and issue when adding new commentsThere seems to be a major issue with comments in the current production and working branches. First, comments that were added earlier are missing.
There are definitley comments to this annotation here (HZT version), but they don't show ...There seems to be a major issue with comments in the current production and working branches. First, comments that were added earlier are missing.
There are definitley comments to this annotation here (HZT version), but they don't show up no matter what I do:
![Bildschirmfoto_2022-12-12_um_16.34.49](/uploads/14cce43f5a678d79a15cfc9070ca4b61/Bildschirmfoto_2022-12-12_um_16.34.49.png)
Scott also reported that he can't see comments.
There is also some weird behaviour when you add new comments. They first don't show up if you submit them, they only do after reloading.
You can see it in this clip:
![Bildschirmaufnahme_2022-12-12_um_16.33.06](/uploads/af36b986df96e86e9472e800272603e7/Bildschirmaufnahme_2022-12-12_um_16.33.06.mov)
Maybe this is linked to the issues that occurred after the changes in the data model regarding multiple targets etc. (we already had comments to annotations showing up in the Timeline Viewer).
@maximilian.mittermei: is that something you could look at? It would be great if we can fix that rather soon than later since it has some impact on the ongoing use of the tool.Mittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1866Open "zoomed skeleton"-dialog after right click/long tap on bounding box?2024-01-09T15:04:55+01:00Hansen, ChristianOpen "zoomed skeleton"-dialog after right click/long tap on bounding box?When skeletons are available:
<br /><br />
![Bildschirmfoto_2022-12-09_um_18.00.35](/uploads/9df8f539ade16114a9e52c923b8c9330/Bildschirmfoto_2022-12-09_um_18.00.35.png)
<br />
leads to
<br />
![Bildschirmfoto_2022-12-09_um_18.02.51](/upl...When skeletons are available:
<br /><br />
![Bildschirmfoto_2022-12-09_um_18.00.35](/uploads/9df8f539ade16114a9e52c923b8c9330/Bildschirmfoto_2022-12-09_um_18.00.35.png)
<br />
leads to
<br />
![Bildschirmfoto_2022-12-09_um_18.02.51](/uploads/06e2eb6f05c219b39f7f759e1c0e979c/Bildschirmfoto_2022-12-09_um_18.02.51.png)
<br /><br />
Would reduce the amount of clicks to select a bodypart.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1865Show skeletons only on hover?2022-12-14T17:11:02+01:00Hansen, ChristianShow skeletons only on hover?This
<br /><br />
![Bildschirmfoto_2022-12-09_um_17.54.50](/uploads/ae33121368d7915e382ba27754286738/Bildschirmfoto_2022-12-09_um_17.54.50.png)
<br /><br />
could be more cleaned up and look like this:
<br /><br />
![Bildschirmfoto_2022-...This
<br /><br />
![Bildschirmfoto_2022-12-09_um_17.54.50](/uploads/ae33121368d7915e382ba27754286738/Bildschirmfoto_2022-12-09_um_17.54.50.png)
<br /><br />
could be more cleaned up and look like this:
<br /><br />
![Bildschirmfoto_2022-12-09_um_17.54.13](/uploads/a388b0942aa213394c98616c9a4d0221/Bildschirmfoto_2022-12-09_um_17.54.13.png)
<br /><br />
Bodyparts could stay visible when selected.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1864Redesign footer in annotation item2023-01-17T11:46:41+01:00Hansen, ChristianRedesign footer in annotation itemIn context with https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1778 the annotation item footer needs to be redesigned, also in preparation for upcoming chips.In context with https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1778 the annotation item footer needs to be redesigned, also in preparation for upcoming chips.https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1863People tracking can be started several times for one video (feedback problem)2023-01-12T15:13:00+01:00Rittershaus, DavidPeople tracking can be started several times for one video (feedback problem)Not sure if this is still work in progress but I trigger people tracking as often as I want. I recognised this specifically on beta.vortanz.ai since the feedback does not really work (no indication that I started the process). In the dat...Not sure if this is still work in progress but I trigger people tracking as often as I want. I recognised this specifically on beta.vortanz.ai since the feedback does not really work (no indication that I started the process). In the data views branch I get a spinning wheel that indicates that something is going on but I still was able to trigger it again and again.
Maybe thats solved with !734?
![Bildschirmfoto_2022-12-08_um_16.28.45](/uploads/de929af1594aec37ae1b873d69907dae/Bildschirmfoto_2022-12-08_um_16.28.45.png)Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1862Swimlane: include audio waveform2022-12-14T14:07:40+01:00Rittershaus, DavidSwimlane: include audio waveformFrom what I understood there is already an existing worker to generate waveforms. Not sure if this is already sufficient to handle zooming etc. However, we always discussed the option of a waveform lane and I don't want the idea to get l...From what I understood there is already an existing worker to generate waveforms. Not sure if this is already sufficient to handle zooming etc. However, we always discussed the option of a waveform lane and I don't want the idea to get lost since it may already be a helpful visualisation for some usecases.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1861Swimlane broken if toggled before annotations are loaded2022-12-15T10:44:32+01:00Rittershaus, DavidSwimlane broken if toggled before annotations are loadedIf I expand the siwmlane before all annotations are loaded, the time ticks and the needle of the playhead are missing (see screenshot below). Either this should be fixed on the swimlane side of things (probably better) or the swimlane sh...If I expand the siwmlane before all annotations are loaded, the time ticks and the needle of the playhead are missing (see screenshot below). Either this should be fixed on the swimlane side of things (probably better) or the swimlane should not be "available" befor all annotations are loaded.
![Bildschirmfoto_2022-12-08_um_16.07.13](/uploads/83867f13889a24e6c2c31e22064cfcdb/Bildschirmfoto_2022-12-08_um_16.07.13.png)Feature: Data ViewsMittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1860Post-annotator menus makeover (logic of filtering & displaying)2024-01-09T15:04:55+01:00Rittershaus, DavidPost-annotator menus makeover (logic of filtering & displaying)1. "Video Analysis" aka "Magic Menu": From my point of view it can (or even should) remain as simple as it is. The question here is more if it has some influence on the rest of the UI. If I toggle the bounding boxes or the pose recogitio...1. "Video Analysis" aka "Magic Menu": From my point of view it can (or even should) remain as simple as it is. The question here is more if it has some influence on the rest of the UI. If I toggle the bounding boxes or the pose recogition I can immediately see the video overlay but not the data visualisation in the swimlane. In the last system dev meeting we said that the siwmlane should autmatically show up with the corresponding data visualisation (for example: people detection --> bboxes are shown as overlays in the video + people count lane is shown as well).
2. Swimlane menu: I suppose that this menu should become simpler and we all agreed on that in the last system dev meeting.
First, in regard to the video analysis features I would suggest to use the same icons and also group lanes that you can toggle under each feature (e.g. Kinesphere --> 1. Follow selected person; 2. All IDs). These features could also be grouped under one main "data visualisation" menu item, which can also contain the annotation density lane. In the swimlane menu only those menu items should be visible that are already available. If kinesphere hasn't been processed yet it should not show up as an option in the swimlane menu.
Second, I would suggest to think about one menu item that is simply called "new custom lane" which opens an overlay where you can configure a new lane. This configuration could include the decision if the custom lane combines the annotations of all users or if it is split per user. It could also allow you to set a filter for this new lane.
But maybe @maximilian.mittermei can think of an even smarter solution based on the discussion in the last system dev meeting.
3. Filter menu: in general it could remain the same. The text filter should also have an effect for all lanes in the swim lane with annotations no matter if split by user or combined in one lane. If we allow people to create custom lanes with a text filter applied (see 2.), they should nevertheless be affected as well, so it's clear that the filter in the annotation list will always have an effect on all annotation lanes in the swimlane.
There is still an open question for me in regard to automatically generated annotations (at the moment transcript, but it might also include Kinesphere labels or others in the future). They always get a seperate lane by default but are always shown together with alll other annotations in the annotation list by default. So they are handled differently in the list and in the swimlane. But this is maybe another issue.
Here is screenshot with all 3 menus visible:
![Bildschirmfoto_2022-12-08_um_10.17.15](/uploads/d0bb1ca9deb5ddd50bff3e6323a34787/Bildschirmfoto_2022-12-08_um_10.17.15.png)Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1859Handling of Tracking Id in Bounding Boxes / Selected Person2023-01-11T14:32:14+01:00Mittermeier, MaximilianHandling of Tracking Id in Bounding Boxes / Selected PersonAnalysis endpoint returns bounding boxes that have no tracking id (see #1731) if tracking analysis has not run yet.
With the advent of the display of tracking-based information like kinesphere (see #1836 and #1740) the `.id` property of...Analysis endpoint returns bounding boxes that have no tracking id (see #1731) if tracking analysis has not run yet.
With the advent of the display of tracking-based information like kinesphere (see #1836 and #1740) the `.id` property of bounding boxes found in the `BoundingBoxes.vue.boundingBoxes` array needs some thought.
An easy solution would be to have `.id` be `undefined` if there is no tracking available and adapt `BoundingBoxes.vue.fetchBoundingBoxes()` to decide if a tracking id was returned and `BoundingBoxes.vue.onClick()` to omit `data-mb-tracking-id` if there is no tracking id.
Question is: is the `.id` property used elsewhere where `undefined` would break things?Mittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1858Change description for pose recognition2022-12-07T11:09:49+01:00Rittershaus, DavidChange description for pose recognitionSuggestion is: "Automatically recognizes basic segments of the human body and draws a coarse skeleton over the body. You can select body parts or single joints and assign annotations to them. Right click or a long tap opens a zoom window...Suggestion is: "Automatically recognizes basic segments of the human body and draws a coarse skeleton over the body. You can select body parts or single joints and assign annotations to them. Right click or a long tap opens a zoom window for a closer view and easier selection of joints and body parts."
@christian.hansenFeature: Data ViewsHansen, ChristianHansen, Christian