Systems Frontend issueshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues2023-01-17T10:40:14+01:00https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1897image upload via url instead of downloading an image first and uploading it a...2023-01-17T10:40:14+01:00Hansen, Christianimage upload via url instead of downloading an image first and uploading it afterwardsAs seen on google for example:
<br /><br />
![Bildschirmfoto_2023-01-12_um_15.47.12](/uploads/cf04606f42ea372993f8f792582c5802/Bildschirmfoto_2023-01-12_um_15.47.12.png)As seen on google for example:
<br /><br />
![Bildschirmfoto_2023-01-12_um_15.47.12](/uploads/cf04606f42ea372993f8f792582c5802/Bildschirmfoto_2023-01-12_um_15.47.12.png)https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1883Auto logout network tab and console log2022-12-22T15:12:54+01:00Rittershaus, DavidAuto logout network tab and console logIt's quite hard to trace but today I had the network tab open when the issue (automatic/unintended logout) occurred:
![Bildschirmfoto_2022-12-22_um_15.10.09](/uploads/04cb7ea8d228c49ce4198c91df57c667/Bildschirmfoto_2022-12-22_um_15.10.0...It's quite hard to trace but today I had the network tab open when the issue (automatic/unintended logout) occurred:
![Bildschirmfoto_2022-12-22_um_15.10.09](/uploads/04cb7ea8d228c49ce4198c91df57c667/Bildschirmfoto_2022-12-22_um_15.10.09.png)
![Bildschirmfoto_2022-12-22_um_15.07.16](/uploads/b93e1b6f40c58d268cb8211c3a20b4c6/Bildschirmfoto_2022-12-22_um_15.07.16.png)
@anton.koch: anything you can recognise in the logs?https://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1881redo the polling of jobs and batchjobs2024-01-09T15:02:01+01:00Milan Gressredo the polling of jobs and batchjobsMultiple problems:
currently, if there is a significant pause between the jobs, (but a batch job is still running) the polling stops because it thinks everything is done
There are two implementations of the polling (magic menu and file...Multiple problems:
currently, if there is a significant pause between the jobs, (but a batch job is still running) the polling stops because it thinks everything is done
There are two implementations of the polling (magic menu and files) which I find annoying, so probably it should move to the store? Or at the very least abstracted away into a general function.
Currently, it is implemented as a recursive function (seemed sensible at the time) but in fact if it is called from multiple sources then obviously multiple polling call stacks are created so likely a `setInterval()` with a clean start/stop interface makes more sense.
Oh and there should probably a very slow default polling mode for even if it thinks nothing happens/runs to avoid getting stuck in dysfunctional state.Feature: Data Viewshttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1880unify button styling in video control bar on desktop and mobile2022-12-15T16:07:08+01:00Hansen, Christianunify button styling in video control bar on desktop and mobileDesktop now:
<br /><br />
![Bildschirmfoto_2022-12-15_um_16.02.06](/uploads/f56e65baa0dea0f567f29b2a3f213ae3/Bildschirmfoto_2022-12-15_um_16.02.06.png)
<br />
![Bildschirmfoto_2022-12-15_um_16.04.27](/uploads/7b8e40ba1aa2ca7c3b73e6d4a6b1...Desktop now:
<br /><br />
![Bildschirmfoto_2022-12-15_um_16.02.06](/uploads/f56e65baa0dea0f567f29b2a3f213ae3/Bildschirmfoto_2022-12-15_um_16.02.06.png)
<br />
![Bildschirmfoto_2022-12-15_um_16.04.27](/uploads/7b8e40ba1aa2ca7c3b73e6d4a6b11a4a/Bildschirmfoto_2022-12-15_um_16.04.27.png)
<br /><br />
Mobile now:
<br /><br />
![Bildschirmfoto_2022-12-15_um_16.02.26](/uploads/8b9a620c99cdfb532edb46d61ee785ff/Bildschirmfoto_2022-12-15_um_16.02.26.png)https://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/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/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/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/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/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/1850Option to download "raw" vortanz container data2023-08-31T16:48:38+02:00Rittershaus, DavidOption to download "raw" vortanz container dataJust because timeline export came up again, I was reminded of something I had in mind for some time already and I'll just add it to the list without high priority: it would be great if users can export/download the raw data that is provi...Just because timeline export came up again, I was reminded of something I had in mind for some time already and I'll just add it to the list without high priority: it would be great if users can export/download the raw data that is provided by the vortanz containers, e.g. the pose data or the transcription. Maybe there could be an option in context menu of files (files page).
![Bildschirmfoto_2022-12-06_um_12.58.38](/uploads/fcf9b0abf1aaa5a789933bfb46411c43/Bildschirmfoto_2022-12-06_um_12.58.38.png)
This is not really relevant for the students during the vortanz project but could be of interest for researchers who want to work with the data.Mittermeier, MaximilianMittermeier, Maximilianhttps://gitlab.rlp.net/motionbank/applications/systems-frontend/-/issues/1849Import/export timeline2023-07-31T15:47:14+02:00Koch, AntonImport/export timelineIn the old version, this was done by having a service package a bunch of JSON files into a ZIP archive.
Would be nice if this could now work in the browser.
The importer must be able to import the legacy format (no selector arrays).In the old version, this was done by having a service package a bunch of JSON files into a ZIP archive.
Would be nice if this could now work in the browser.
The importer must be able to import the legacy format (no selector arrays).Feature: Data ViewsMittermeier, MaximilianMittermeier, Maximilianhttps://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 Views