beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2018-10-31T08:21:40Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/473Add/merge userspace documentation for reports app changes2018-10-31T08:21:40ZJaden DIEFENBAUGHAdd/merge userspace documentation for reports app changesThe userspace documentation changes for the updates to the reports app didn't make it to staging...hopefully I have a stash/branch somewhere, but I'll probably need to rewrite it all.The userspace documentation changes for the updates to the reports app didn't make it to staging...hopefully I have a stash/branch somewhere, but I'll probably need to rewrite it all.Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/488Perf issue with Angular's 2-way binding makes complex reports unusable2018-03-20T08:37:24ZJaden DIEFENBAUGHPerf issue with Angular's 2-way binding makes complex reports unusableThe default two-way binding is too slow right now. Somehow this wasn't caught in testing, even though large reports were tested. It might have to do with the complexity of experiments - if Angular is binding entire experiment/toolchain o...The default two-way binding is too slow right now. Somehow this wasn't caught in testing, even though large reports were tested. It might have to do with the complexity of experiments - if Angular is binding entire experiment/toolchain objects, the perf hit could've slipped through testing.Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/367[backend] Wipe cache and cancel experiment actions are not working2016-06-24T10:27:57ZAndré Anjos[backend] Wipe cache and cancel experiment actions are not workingCurrently, both result in a time out. Needs to test if the backend is working properly.Currently, both result in a time out. Needs to test if the backend is working properly.Open-source ReleaseAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/341[ui] Replace on the frontpage the example toolchain by the public activity feed2016-03-16T12:01:27ZSébastien MARCEL[ui] Replace on the frontpage the example toolchain by the public activity feedhttp://beatweb-staginghttp://beatweb-stagingOpen-source Releasehttps://gitlab.idiap.ch/beat/beat.web/-/issues/315[reports] Float-point precision does not apply to "special" columns which are...2016-02-16T17:04:28ZAndré Anjos[reports] Float-point precision does not apply to "special" columns which are not analyzer outputsCan this be easily fixed?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/f757c27dee559662a71491d076f904f2/image.png)
Can this be easily fixed?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/f757c27dee559662a71491d076f904f2/image.png)
Open-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/346[many] request documentation button ?2016-02-16T13:05:27ZSébastien MARCEL[many] request documentation button ?In any documentation tab
Example:
http://beatweb-staging/experiments/aythamimm/aythamimm/atvs_keystroke_btas_benchmark/1/ATVS_keystroke_beckmark_btas2015/
what about having a button "Request documentation" to all objects on the pl...In any documentation tab
Example:
http://beatweb-staging/experiments/aythamimm/aythamimm/atvs_keystroke_btas_benchmark/1/ATVS_keystroke_beckmark_btas2015/
what about having a button "Request documentation" to all objects on the platform (expe/toolchains/algo/attestation) for a user to ask another one to document its stuff ?
In practice the other user will receive an email.
We can imagine to link this later to some rewarding mechanism with the gamification.
Open-source Releasehttps://gitlab.idiap.ch/beat/beat.web/-/issues/373[experiments] Clicking on "Expand" on a plot produce an error 5002016-02-16T09:08:37ZPhilip ABBET[experiments] Clicking on "Expand" on a plot produce an error 500For instance on this page: http://beatweb-staging/experiments/anjos/anjos/livdet-lda/1/livdet-2013-biometrika-test/For instance on this page: http://beatweb-staging/experiments/anjos/anjos/livdet-lda/1/livdet-2013-biometrika-test/Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/392[toolchains] Editor resets previous input sync if another input is attached t...2016-02-11T08:40:47ZAndré Anjos[toolchains] Editor resets previous input sync if another input is attached to a blockHow to reproduce:
1. Fork a toolchain
2. Create a connection from an output to an already connected input with a different synchronization channel
Results: the old connection will be synchronized with the new channel; a new connec...How to reproduce:
1. Fork a toolchain
2. Create a connection from an output to an already connected input with a different synchronization channel
Results: the old connection will be synchronized with the new channel; a new connection will not be drawn.
One of the two solutions must be adopted:
1. The new connection is not accepted and nothing changes
2. The new connection **replaces** the old connectionFinal DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/377[reports] Table/Figure adding pop-up does not have a dismiss button2016-02-10T10:44:12ZAndré Anjos[reports] Table/Figure adding pop-up does not have a dismiss buttonThis one keeps coming in and out and we must fix it because it is **really** counterintuitive in the way it is implemented today.
Little cut-n-paste from our dev mailing list:
```text
JG: ISSUE 2:
You create an experiment.
You c...This one keeps coming in and out and we must fix it because it is **really** counterintuitive in the way it is implemented today.
Little cut-n-paste from our dev mailing list:
```text
JG: ISSUE 2:
You create an experiment.
You create a report.
You add the experiment to the report.
You add a table --> results.
You select the results that you want to include in the table by ticking the boxes on the left.
Once you have finished selecting the results... what do you do?
I think it would be nice to have a "DONE" button at the bottom of the window where you select the results to be displayed in the table. This way when you finish selecting the results, you press the "DONE" button and it takes you back to the report.
```Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/384[toolchains] Editor allows double connection to input2016-02-08T13:23:37ZAndré Anjos[toolchains] Editor allows double connection to inputThe toolchain editor allows outputs of two blocks to be connected to a single input block.
1. This should not be allowed
2. If that is allowed, errors should be displayed. Currently, the problem is detected, but no errors are shown a...The toolchain editor allows outputs of two blocks to be connected to a single input block.
1. This should not be allowed
2. If that is allowed, errors should be displayed. Currently, the problem is detected, but no errors are shown at the bottom of the page.Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/376[reports] Reports without experiments could be made a bit more user-friendly2016-02-05T10:11:28ZAndré Anjos[reports] Reports without experiments could be made a bit more user-friendlyHere is the cut and paste from the mailing list discussion:
```text
JG: You go to the reports tab.
You create a new report.
You press on "add a new report item"
You press on figure/table
You press on results
Nothing happens and ...Here is the cut and paste from the mailing list discussion:
```text
JG: You go to the reports tab.
You create a new report.
You press on "add a new report item"
You press on figure/table
You press on results
Nothing happens and there is no way of exiting the screen except going backwards with the browser.
I understand this issue comes from the fact that no experiments have been "previously" added to the report. To add an experiment you have to go to that particular experiment and press "add to report".
From my point of view the user's experience would improve if:
- A button "add experiment" was included in the report (similar to the current button "add a report item"). So that you can add experiments directly from the report (instead of going back to the experiment)
- Also, if someone presses on "add a report item" before an experiment has been added to the report, it would be nice if a pop-up informed the user that: "you need to add an experiment to the report before you can add an item" (or something similar)
AA: The most effective way to implement this, IMO, would be to disable the button and have a static message, with an explanation, including a link back to the experiments page.
Adding an experiment through the report, though relatively easy to implement, would be limited in terms of information displayed (e.g. date and name) because of the pop-up size and the incredible amount of info a user may need to select one and not another.
```Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/379[databases] Serializer ships unindented declaration2016-02-02T08:47:19ZAndré Anjos[databases] Serializer ships unindented declarationThis is a minor issue, but annoying. I'm trying to download a database from http://beatweb-staging and re-upload it to https://beat-eu.org/platform. While downloading it, I realise the database declaration (JSON) is not indented (with 4 ...This is a minor issue, but annoying. I'm trying to download a database from http://beatweb-staging and re-upload it to https://beat-eu.org/platform. While downloading it, I realise the database declaration (JSON) is not indented (with 4 spaces), which is the standard for the other contributions. The whole JSON comes in a single line of code.
I guess the issue here is the serializer that, contrary to what is in ``common/serializers.py``, does not do any appropriate JSON dumping of the database declaration.
How to reproduce this issue:
```sh
$ ./bin/beat -p prefix -m http://beatweb-staging db pull livdet2013/1
...
$ cat prefix/databases/livdet2013/1.json
... #one single line of JSON file
$ ./bin/beat -p prefix -m http://beatweb-staging tc pull tutorial/eigenface/1
...
$ cat prefix/toolchains/tutorial/eigenface/1.json
... #perfectly indented
```Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/371[activity stream] Activities for a user may show shared objects with another ...2016-02-01T14:30:39ZAndré Anjos[activity stream] Activities for a user may show shared objects with another userFor some reason, objects shared with user X are also appearing to another user on the activity list. The case occurs with, for example, for user `tpereira` on object http://beatweb-staging/toolchains/chichan/full_pre_mlbphs_projection/1/...For some reason, objects shared with user X are also appearing to another user on the activity list. The case occurs with, for example, for user `tpereira` on object http://beatweb-staging/toolchains/chichan/full_pre_mlbphs_projection/1/
![image](/uploads/dd09926027a8bf6f881828206d4386f7/image.png)
As you can see from the list, it looks like user `chichan` shared that object with user `tpereira`. When the user `tpereira` clicks on the contribution, he gets a 404 (which is correct, since the object was not shared with that user).Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/374[experiments] no capture error log ?2016-01-12T14:55:28ZSébastien MARCEL[experiments] no capture error log ?I forked and re-ran the experiments
http://beatweb-staging/experiments/anjos/ivana7c/simple-antispoofing-updated/1/ivanas-experiment-xxx/
as
http://beatweb-staging/experiments/smarcel/ivana7c/simple-antispoofing-updated/1/ivanas-e...I forked and re-ran the experiments
http://beatweb-staging/experiments/anjos/ivana7c/simple-antispoofing-updated/1/ivanas-experiment-xxx/
as
http://beatweb-staging/experiments/smarcel/ivana7c/simple-antispoofing-updated/1/ivanas-experiment-yyy/
sadly it stopped but for the block that failed the captured error log is empty so so way to debug.
Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/372[activity stream] Attestations do not show gravatar2016-01-07T17:30:48ZAndré Anjos[activity stream] Attestations do not show gravatarWhen a user publishes an attestation, at the activity stream of another uesr, one cannot see the originating user's gravatar. Example:
![image](/uploads/cef8b58163f5c44d2f28792dfbc9e46d/image.png)
When a user publishes an attestation, at the activity stream of another uesr, one cannot see the originating user's gravatar. Example:
![image](/uploads/cef8b58163f5c44d2f28792dfbc9e46d/image.png)
Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/370[experiments] Anonymous user can't see any experiment2016-01-06T13:53:31ZPhilip ABBET[experiments] Anonymous user can't see any experimentWhen not logged in, going on an experiment page produces the following error:
![Screen_Shot_2016-01-06_at_08.38.15](/uploads/3b417aef914d2e831eb98319e41b83a6/Screen_Shot_2016-01-06_at_08.38.15.png)
When not logged in, going on an experiment page produces the following error:
![Screen_Shot_2016-01-06_at_08.38.15](/uploads/3b417aef914d2e831eb98319e41b83a6/Screen_Shot_2016-01-06_at_08.38.15.png)
https://gitlab.idiap.ch/beat/beat.web/-/issues/366[reports] Cannot expand plots2015-12-18T14:59:05ZAndré Anjos[reports] Cannot expand plotsFor some reason, this stopped working.
Example:
http://beatweb-staging/search/anjos/for_flavio/
Then click on the button "expand" to expand the plots. Open the JS console to see:
```text
Uncaught TypeError: Cannot read prope...For some reason, this stopped working.
Example:
http://beatweb-staging/search/anjos/for_flavio/
Then click on the button "expand" to expand the plots. Open the JS console to see:
```text
Uncaught TypeError: Cannot read property 'split' of undefined
```
From: http://beatweb-staging/static/experiments/js/utils.js?v1.0.0b13, line 223
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/360[reports] Missing attributes on table cells2015-12-18T09:24:57ZTiago de Freitas Pereira[reports] Missing attributes on table cellsIn the staging version I created the report (http://beatweb-staging/reports/914720457/).
This report has only one table containing informations regarding two algorithms, but only two experiments use these algorithms. For the ones that...In the staging version I created the report (http://beatweb-staging/reports/914720457/).
This report has only one table containing informations regarding two algorithms, but only two experiments use these algorithms. For the ones that don't use, it is possible to see a dash line in the table, but for the ones that use the algorithms ("Face ISV", "Periocular ISV") it is not possible to see their values.
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/362[experiments] Empty list of datasets when creating a new experiment2015-12-17T11:59:28ZPhilip ABBET[experiments] Empty list of datasets when creating a new experimentSteps to reproduce:
* Create a new experiment
* Click on [Advanced mode]
The dataset comboboxes are all empty.
If you first select a database/protocol combination in "simple mode", the "advanced mode" works correctly.Steps to reproduce:
* Create a new experiment
* Click on [Advanced mode]
The dataset comboboxes are all empty.
If you first select a database/protocol combination in "simple mode", the "advanced mode" works correctly.https://gitlab.idiap.ch/beat/beat.web/-/issues/364[experiments] Readability problem2015-12-17T10:57:49ZPhilip ABBET[experiments] Readability problemWhen creating a new experiment, in the "Select a toolchain" dialog, the documentation of the selected toolchain isn't readable in the list (written in gray on blue background).
I don't know if other dialogs are in the same case.When creating a new experiment, in the "Select a toolchain" dialog, the documentation of the selected toolchain isn't readable in the list (written in gray on blue background).
I don't know if other dialogs are in the same case.