Systems Frontend issueshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues2023-01-27T14:10:29+01:00https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1001iPad: changing volume has no effect in post annotator2023-01-27T14:10:29+01:00Hansen, ChristianiPad: changing volume has no effect in post annotator3.0.0-beta Releasehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/695post annotator: add possibility to switch between desktop/mobile-layout manually2021-10-01T08:49:17+02:00Hansen, Christianpost annotator: add possibility to switch between desktop/mobile-layout manually![Bildschirmfoto_2021-08-19_um_07.30.27](/uploads/833f8349025e0494f1294af499bc8fda/Bildschirmfoto_2021-08-19_um_07.30.27.png)
![Bildschirmfoto_2021-08-19_um_07.30.52](/uploads/830f14eb619c4c1e0343a4bcdda47b42/Bildschirmfoto_2021-08-19_u...![Bildschirmfoto_2021-08-19_um_07.30.27](/uploads/833f8349025e0494f1294af499bc8fda/Bildschirmfoto_2021-08-19_um_07.30.27.png)
![Bildschirmfoto_2021-08-19_um_07.30.52](/uploads/830f14eb619c4c1e0343a4bcdda47b42/Bildschirmfoto_2021-08-19_um_07.30.52.png)3.0.0-beta Releasehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/678displaying annotations alternative (idea, low prio)2021-10-01T08:49:18+02:00Hansen, Christiandisplaying annotations alternative (idea, low prio)1. timestamp related annotations pushed from bottom, fade out after a few seconds (have a look at instagram livestreams)
2. annotation ranges: sticked/pinned annotations visible as long as the time range
![Bildschirmfoto_2021-08-13_um_...1. timestamp related annotations pushed from bottom, fade out after a few seconds (have a look at instagram livestreams)
2. annotation ranges: sticked/pinned annotations visible as long as the time range
![Bildschirmfoto_2021-08-13_um_11.00.38](/uploads/30003af88a92ab721307186986ad1326/Bildschirmfoto_2021-08-13_um_11.00.38.png)3.0.0-beta Releasehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1739moving playhead-handel in the swimlane produces sometimes buggy bounding boxes2022-10-31T13:47:29+01:00Milan Gressmoving playhead-handel in the swimlane produces sometimes buggy bounding boxesThe real bug (wrong BB at current frame) is mostly non-breaking and easily fixed by a quick play/pause
![Kapture_2022-10-29_at_11.57.15](/uploads/9b23dca81e8c162c542182b8910cd773/Kapture_2022-10-29_at_11.57.15.mp4)The real bug (wrong BB at current frame) is mostly non-breaking and easily fixed by a quick play/pause
![Kapture_2022-10-29_at_11.57.15](/uploads/9b23dca81e8c162c542182b8910cd773/Kapture_2022-10-29_at_11.57.15.mp4)Feature: Swimlanehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1720Swimlane performance needs to be optimized for mobile2022-10-25T13:23:31+02:00Mittermeier, MaximilianSwimlane performance needs to be optimized for mobileZooming and navigating the Swimlane is fairly low-fps on mobile, especially when zoomed in far enough for the framebased grid to be visible.
Profiling shows the following distribution of spent time for dragging the Swimlane:
- 72% - Ev...Zooming and navigating the Swimlane is fairly low-fps on mobile, especially when zoomed in far enough for the framebased grid to be visible.
Profiling shows the following distribution of spent time for dragging the Swimlane:
- 72% - EventHandler for the drag
- 13% - Painting
- 5,3% - Styles
- 3,5% - Reflow
Time within EventHandler is split between (% of total Time)
- 43% - Updating the Ruler Grid/Ticks
- 28% - Updating the AnnotationElements
Within Updating Ruler Grid (% of total Time)
- 23% - buildRulerGridSvgElement > toFormat() (creating the label-string for Ruler Ticks)
- 4,4% - Node.removeChild
Within Updating AnnotationElements
- 25% - buildAnnotationElements > mostly spent on fromISO() and toDuration()
- 3,5% - arrangeAnnotationElements > mostly spent on fromISO()
![Screenshot_2022-10-24_at_12.10.42](/uploads/61ab1239e12207ed444276e6e32b532f/Screenshot_2022-10-24_at_12.10.42.png)Feature: SwimlaneMittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1686Swimlane: Add handlers for zoom bar2022-10-19T14:48:12+02:00Rittershaus, DavidSwimlane: Add handlers for zoom bar@maximilian.mittermei: I would suggest to add the possibility to use the zoom with handlers to the left and right of the navigation bar (like in the previous version of the system):
![Bildschirmfoto_2022-10-17_um_09.42.01](/uploads/fca0...@maximilian.mittermei: I would suggest to add the possibility to use the zoom with handlers to the left and right of the navigation bar (like in the previous version of the system):
![Bildschirmfoto_2022-10-17_um_09.42.01](/uploads/fca018d8d155b977dd563e90636c3881/Bildschirmfoto_2022-10-17_um_09.42.01.png)
![Bildschirmfoto_2022-10-17_um_09.44.01](/uploads/d9b46563ee431157315c2c36df4ef850/Bildschirmfoto_2022-10-17_um_09.44.01.png)Feature: Swimlanehttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1676Swimlane: Lane Menu arrangement broken after switching between Light/Dark theme2022-11-10T18:58:48+01:00Mittermeier, MaximilianSwimlane: Lane Menu arrangement broken after switching between Light/Dark themeAfter switching between Light and Dark theme via main menu the Lane Menu buttons seem to be misaligned.
Misalignment does not appear on Lanes created after the theme switch.
![Screenshot_2022-10-10_at_12.48.02](/uploads/18c5623c59da1da...After switching between Light and Dark theme via main menu the Lane Menu buttons seem to be misaligned.
Misalignment does not appear on Lanes created after the theme switch.
![Screenshot_2022-10-10_at_12.48.02](/uploads/18c5623c59da1da12f9b2d64e0225c39/Screenshot_2022-10-10_at_12.48.02.png)Feature: SwimlaneMittermeier, MaximilianMittermeier, Maximilianhttps://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/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/1853Add data-mb-type="joint|bodypart|boundingbox" to svgSelector?2023-01-09T16:54:40+01:00Hansen, ChristianAdd data-mb-type="joint|bodypart|boundingbox" to svgSelector?Adding a `data-mb-type` to the svgSelector would be helpful to see what kind of `<svg>` (joint, bodypart or bounding box) is stored in the selector. At the moment we know that a joint uses `<circle>`, a bodypart uses `<line>`, and a boun...Adding a `data-mb-type` to the svgSelector would be helpful to see what kind of `<svg>` (joint, bodypart or bounding box) is stored in the selector. At the moment we know that a joint uses `<circle>`, a bodypart uses `<line>`, and a bounding box uses `<rect>`. But this could change in the future if `<circle>` and `<line>` for example are combined somewhere.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1845Notification about finished jobs doesent work2022-12-05T16:33:26+01:00Milan GressNotification about finished jobs doesent workCurrently, if a job "ends" with 0% progress it is counted as failed and if it finishes with 100% it counts a success. But for short running jobs (like the new `har` job… that finish with 0%) this does not work anymore
So, we probably ne...Currently, if a job "ends" with 0% progress it is counted as failed and if it finishes with 100% it counts a success. But for short running jobs (like the new `har` job… that finish with 0%) this does not work anymore
So, we probably need to do a deferred check if the job actually finished and only then show a success/fail notification
or switch to general job changed notification
Edit: this relates currently to the `data-views-branch`Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1839Video Analysis menu needs loading indicator2022-12-02T13:40:02+01:00Milan GressVideo Analysis menu needs loading indicatorOn a slower internet connection, the jobs take sometime longer to load, and the finished jobs show up later in the menu. There should be some feedback that the loading has not finishedOn a slower internet connection, the jobs take sometime longer to load, and the finished jobs show up later in the menu. There should be some feedback that the loading has not finishedFeature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1818Add opportunity to correct tracked persons whose ID switched during the peopl...2022-11-25T18:03:25+01:00Hansen, ChristianAdd opportunity to correct tracked persons whose ID switched during the people detectionIt is possible that bad light in a video, leaving the scenario and coming back etc. causes an ID change, "Person 1" could become "Person 15" after a while. The user should be able to say "Okay Person 1 is also Person 15".It is possible that bad light in a video, leaving the scenario and coming back etc. causes an ID change, "Person 1" could become "Person 15" after a while. The user should be able to say "Okay Person 1 is also Person 15".Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1813Add Stop/Exit-Button for the Video Analysis Tools?2022-11-28T16:04:17+01:00Stefanie HampelAdd Stop/Exit-Button for the Video Analysis Tools?Maybe it would be helpful to add a Stop/Exit-Button which is close to the Video-Analysis Tools so that the process can be stopped in case that it takes too long, must be restarted or something like that? As far as I can see, it is now on...Maybe it would be helpful to add a Stop/Exit-Button which is close to the Video-Analysis Tools so that the process can be stopped in case that it takes too long, must be restarted or something like that? As far as I can see, it is now only possible via Files->Edit->Video Analysis, which might be a bit hard to find?Feature: Data ViewsMilan GressMilan Gresshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1702Add loading indicator to bounding boxes2022-10-18T22:37:33+02:00Koch, AntonAdd loading indicator to bounding boxesThe `BoundingBox.vue` component has an `isLoading` property that can be used to show a spinner or some other indicator.The `BoundingBox.vue` component has an `isLoading` property that can be used to show a spinner or some other indicator.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1685Highlight related bounding box when hovering chip in annotation item2022-10-19T14:38:47+02:00Hansen, ChristianHighlight related bounding box when hovering chip in annotation item![Bildschirmfoto_2022-10-14_um_17.04.34](/uploads/169761b2049fbfff9dc4447f1a128997/Bildschirmfoto_2022-10-14_um_17.04.34.png)![Bildschirmfoto_2022-10-14_um_17.04.34](/uploads/169761b2049fbfff9dc4447f1a128997/Bildschirmfoto_2022-10-14_um_17.04.34.png)Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1673Bounding Boxes Feature: add colors/names2022-10-17T11:10:37+02:00Hansen, ChristianBounding Boxes Feature: add colors/namesWhen it is possible to assign one specific box to one specific person, then there should be a (context) menu to give the boxes names/titles and colors that are valid in the whole video.When it is possible to assign one specific box to one specific person, then there should be a (context) menu to give the boxes names/titles and colors that are valid in the whole video.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1517Filtering by type: comment doesn't give feedback when no comments are found2022-06-09T09:45:55+02:00Isabela DimarcoFiltering by type: comment doesn't give feedback when no comments are foundIf you filter by annotation type 'commenting' and you don't have any annotations that match this type, no annotations should get shown in the annotations drawer and a message like 'we couldn't find any annotations of this type in your ti...If you filter by annotation type 'commenting' and you don't have any annotations that match this type, no annotations should get shown in the annotations drawer and a message like 'we couldn't find any annotations of this type in your timeline' should appear.
update: okay apparently when the filters don't find a match it is already so that no annotations get shown. Only when filtering by type **commenting** there is no visual feedback. I still think the message is a good idea. : )Usability UX Improvementshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1516Searching for a word in the filter should highlight said word in the annotations2022-06-02T15:01:45+02:00Isabela DimarcoSearching for a word in the filter should highlight said word in the annotationsSearching for a word in the annotations and it not being highlighted was a little confusing specially on small screens because since the filter component sets a semi-transparent white background behind itself, users can't really tell if ...Searching for a word in the annotations and it not being highlighted was a little confusing specially on small screens because since the filter component sets a semi-transparent white background behind itself, users can't really tell if the annotations got filtered or not, specially because even when 'leaving' the filter view, the annotation that is left (the one that includes the searched word) doesn't appear to include said word, you first have to read it to see if it matches. And this supposing that there is only one annotation that matches the search word, in case you have more than one it's another story.
It would be much easier if the 'suchbegriff' users enter in the filter gets highlighted on search or after search in the annotations that include it, so that it's easy to find said annotation.Usability UX Improvementshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1515Filters in timeline viewer2022-06-02T14:53:38+02:00Isabela DimarcoFilters in timeline viewerBeing able to filter your annotation stream is a super useful feature. If the filter button is available on both 'tools' (post-annotator + timeline viewer) why doesn't it work the same on both?
Here are the findings that came up after ...Being able to filter your annotation stream is a super useful feature. If the filter button is available on both 'tools' (post-annotator + timeline viewer) why doesn't it work the same on both?
Here are the findings that came up after today's testing session:
- If the decision was to only make filters available in the post-annotator, then the button on the timeline viewer should only not include a filter icon but a search icon.
- If the filters are available in both places, let them work exactly the same → why am I allowed to filter on one place and not on the other?Usability UX Improvements