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/247[reports] Workflow for adding a Table of results is not very intuitive2019-07-04T08:37:03ZAndré Anjos[reports] Workflow for adding a Table of results is not very intuitiveThe current workflow to add a Table of results gets the user through a sequence of clicks up to the point a list with select boxes is shown.
At this point, there is no "set" button or anything that allows the user to dismiss/apply the...The current workflow to add a Table of results gets the user through a sequence of clicks up to the point a list with select boxes is shown.
At this point, there is no "set" button or anything that allows the user to dismiss/apply the options. It is not very automatic that clicking outside the pop-up window makes it apply the options. I'd rather think it should cancel the action...
Anyways, some improvement on this area would be welcome.https://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/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/240[reports] Clicking on "New" Report brings user to the front page2015-08-13T15:34:01ZAndré Anjos[reports] Clicking on "New" Report brings user to the front pageYou can't currently click on the "New" button on the Report's tab at the user micro-site. It gets you to the front page instead.
@flavio.tarsetti: Can you confirm we are missing a new Reports editor?
The only way to create a report...You can't currently click on the "New" button on the Report's tab at the user micro-site. It gets you to the front page instead.
@flavio.tarsetti: Can you confirm we are missing a new Reports editor?
The only way to create a report is currently using the admin panel.BTAS TutorialFlavio 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/241[reports] Cannot have spaces on their name, but no validation takes place2015-08-26T15:02:17ZAndré Anjos[reports] Cannot have spaces on their name, but no validation takes placeNo validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1...No validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1. Create a report through the admin site with spaces on its name
2. On the user site search for this report and click on it
Results: Django exception being thrown
Expected result: Either finds the page or has validation implemented so that names with spaces are not allowed.
Note: There is no good reason why reports with spaces should not be allowed. Or is there?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/242[reports] Analyzer hint on experiment lists2015-11-20T11:26:17ZAndré Anjos[reports] Analyzer hint on experiment listsBecause the analyzer plays an important role on the search and on the reports, it would be good if it is also displayed along side experiment tables (e.g., on the user microsite or by the end of a toolchain page). This would help users a...Because the analyzer plays an important role on the search and on the reports, it would be good if it is also displayed along side experiment tables (e.g., on the user microsite or by the end of a toolchain page). This would help users avoid the selection of experiments without matching analyzers and would understand why there are errors when neglecting that piece of information.
Furthermore, when refusing to add experiments, a list of conflicting choices and the reasoning why one can't add an experiment would be welcome, if easy to implement.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/243[reports] Cannot add Table/Figure2015-08-13T15:34:00ZAndré Anjos[reports] Cannot add Table/FigureIt is currently not possible to add a table to an existing report on the staging system. The report in question has a couple of experiments added to it.
Clicking on the any of the entries when the pop-up window appears does not do any...It is currently not possible to add a table to an existing report on the staging system. The report in question has a couple of experiments added to it.
Clicking on the any of the entries when the pop-up window appears does not do anything.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/244[reports] Experiments are not shown on the report page2015-08-13T15:34:00ZAndré Anjos[reports] Experiments are not shown on the report pageDespite the fact I could successfully insert 2 experiments on my report, it is currently not possible to see them (at least a list) through the respective report page.Despite the fact I could successfully insert 2 experiments on my report, it is currently not possible to see them (at least a list) through the respective report page.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/245[reports] Sharing/locking behaviour2015-08-27T14:43:51ZAndré Anjos[reports] Sharing/locking behaviourHow can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be th...How can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be the workflow to collaboratively create a report or (on a minor scale) an attestation.
Differently than attestations, reports combine displaying features that authors (working remotely) may need to agree while composing an article. IMO, being able to share a report sounds like a good idea.
Attestations don't suffer from this problem because, if you lock them, other people can see it. Reports, on the other end, can only be seen while locked so the user would have to:
1. Lock report
2. Share link with remote party
3. If comments from remote party: unlock report (now not visible anymore to remote party)
4. Modify the report and go back to 1 as many times as necessary
This looks a bit cumbersome - would you agree? In this context, would it make sense to have reports a subclass of "Shareable" as suggested on one of our discussions?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/246[plots] Not working on the staging system2015-08-04T12:29:59ZAndré Anjos[plots] Not working on the staging systemThe plotting is not working on the staging system. Probably related to the experiment label -> name changes.The plotting is not working on the staging system. Probably related to the experiment label -> name changes.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/253Long description field gets mangled symbols2015-08-28T12:46:10ZAndré AnjosLong description field gets mangled symbolsFor some reason, when the platform copies the object description to the edit box (restructuredtext), symbols like ``<`` (typically used inside URLs in restructuredtext) gets translated to ``&lt;`` and is displayed as such. If the user tr...For some reason, when the platform copies the object description to the edit box (restructuredtext), symbols like ``<`` (typically used inside URLs in restructuredtext) gets translated to ``<`` and is displayed as such. If the user tries to save the text, he/she will get an error in a place typically unrelated to the change.
How to reproduce this problem:
1. At http://beatweb-staging, fork the algorithm ``tutorial/linear_machine_projection/5``
2. Scroll down as to edit its documentation. It shows:
```text
The linear transformation relies on the `Bob <http://www.idiap.ch/software/bob>`_ library (version 2).
```
Whereas it should show:
```text
The linear transformation relies on the `Bob <http://www.idiap.ch/software/bob>`_ library (version 2).
```
I guess we're escaping too much somewhere.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/254[experiments] Label auto-completion seems broken2015-08-17T21:52:39ZAndré Anjos[experiments] Label auto-completion seems brokenFor some reason, label auto-completion seems broken at the staging platform.
If you try to create an experiment and click on its name, it will auto-complete the full experiment name instead just the final bit:
![image](https://gitl...For some reason, label auto-completion seems broken at the staging platform.
If you try to create an experiment and click on its name, it will auto-complete the full experiment name instead just the final bit:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/db7dcd300231202e7167faf5e2663a36/image.png)
I guess this change is related to the recent ``label`` -> ``name`` clean-ups performed.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/255[backend] Queue-less environments should not be displayed at experiment confi...2015-08-19T21:04:19ZAndré Anjos[backend] Queue-less environments should not be displayed at experiment configuratorAs of today, the experiment configuration is displaying environments for selection that correspond to no configured queue. This generates a awkward situation for the user. Must be fixed as soon as possible.As of today, the experiment configuration is displaying environments for selection that correspond to no configured queue. This generates a awkward situation for the user. Must be fixed as soon as possible.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/256[experiments] Rename button is not working2015-08-17T21:52:38ZAndré Anjos[experiments] Rename button is not workingWe cannot anylonger rename a experiment with the "rename" button on the experiment display page. The button leads to no pop-up or similar.
When I click on the button, the JS console shows me:
```text
Uncaught TypeError: Cannot set...We cannot anylonger rename a experiment with the "rename" button on the experiment display page. The button leads to no pop-up or similar.
When I click on the button, the JS console shows me:
```text
Uncaught TypeError: Cannot set property 'value' of undefinedbeat.experiments.dialogs.show
ExperimentRenaming @ dialogs.js?v0.13.0b3:977
(anonymous function) @ (index):579
m.event.dispatch @ jquery-1.11.1.min.js?v0.13.0b3:3
r.handle @ jquery-1.11.1.min.js?v0.13.0b3:3
```
Possibly, also related to the ``label`` -> ``name`` changes.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/257[experiments] Long name for experiment causes an error2015-08-25T12:36:53ZAndré Anjos[experiments] Long name for experiment causes an errorIf a name with more than 100 characters is chosen for an experiment (using the experiment configuration), the platform shows a pop-up window with some sort of Python exception that is not digestable by the end-user:
![image](https://g...If a name with more than 100 characters is chosen for an experiment (using the experiment configuration), the platform shows a pop-up window with some sort of Python exception that is not digestable by the end-user:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/3a4b7850786d378b0e34de66de5069db/image.png)
Ideally, it should point out the problem and let the user choose another name.
This is probably related to the latest ``label`` -> ``name`` changes on experiments.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/258[reports] "Add to report" button on freshly finished experiments is grayed-out2015-08-27T14:43:50ZAndré Anjos[reports] "Add to report" button on freshly finished experiments is grayed-outI guess it is just missing a "refresh" after the experiment is finished.
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/552128c7a240269eeb67ac23e8d2c065/image.png)
I guess it is just missing a "refresh" after the experiment is finished.
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/552128c7a240269eeb67ac23e8d2c065/image.png)
BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/259[toolchains] New editor scrollbars quirks2015-12-15T11:54:57ZAndré Anjos[toolchains] New editor scrollbars quirksHello and thanks for the scrollbars. It is a very useful addition! A few quirks/suggestions:
1. On both Safari and Chromium the toolchain placement is initialised strangely (I have disabled the cache to make sure it was loading proper...Hello and thanks for the scrollbars. It is a very useful addition! A few quirks/suggestions:
1. On both Safari and Chromium the toolchain placement is initialised strangely (I have disabled the cache to make sure it was loading properly, but still):
![Screen_Shot_2015-08-18_at_00.06.03](https://gitlab.idiap.ch/biometric/beat.web/uploads/bf0d38f66090daa9e8897e34eb48497f/Screen_Shot_2015-08-18_at_00.06.03.png)
2. On my Mac, a two-finger movement does not translate into canvas movement, but on zoom-in/zoom-out. Do you think we could re-bind it so that: (a) two-finger movement is the same as canvas movement and (b) zoom-in/zoom-out is Cmd + two-finger movement or whatever the natural combination should be? That may make the editor a bit more intuitive.
3. Since you're developing a toolbar, it would be great to have a button that would make the whole toolchain visible on the viewport, re-centering it on the canvas.
4. Movement is a bit weird... This idea of infinite canvas is implemented in other tools (such as Dia or Excel) in a more natural way. I guess the size is defined by the drawn area contents and then expanded as the user forces in each direction. If the canvas continues blank after the user goes back, then it is re-trimmed. At least, that is the (loose) impression I have by looking at how it works. Of course, the toolkit and widgets for this are very different than the ones we probably have access through a JS canvas, but I thought maybe that could be a helpful hint for an algorithm for this task.Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/263[experiments] Running experiments are shown at the bottom of the experiment list2015-11-20T11:25:40ZAndré Anjos[experiments] Running experiments are shown at the bottom of the experiment listIt is a bit cumbersome to find running experiments this way. I think it would be more eloquent to have pending and running experiments first. Then order by date.
Of course, being able to sort the columns would be a plus. @philip.abbet...It is a bit cumbersome to find running experiments this way. I think it would be more eloquent to have pending and running experiments first. Then order by date.
Of course, being able to sort the columns would be a plus. @philip.abbet: do you think we could integrate the column sorter you introduced at the search on this table as well?Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/264[plotters] Default plotter for plot/scatter/1 is generating a 500 error2015-08-20T10:25:21ZAndré Anjos[plotters] Default plotter for plot/scatter/1 is generating a 500 errorSomething changed since our last update. Needs to be checked as soon as possible.Something changed since our last update. Needs to be checked as soon as possible.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/266[attestations] Migration is not setting a proper expiration date on existing ...2015-08-21T00:57:42ZAndré Anjos[attestations] Migration is not setting a proper expiration date on existing attestationsWe should implement this as a migration, otherwise existing attestations will never expire.We should implement this as a migration, otherwise existing attestations will never expire.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/269[reports] No way to remove an experiment from a report2015-08-27T14:43:49ZAndré Anjos[reports] No way to remove an experiment from a reportThis was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.This was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/271If algorithm sharing state is "usable" (i.e. executable-only by others), then...2015-08-28T12:46:51ZAndré AnjosIf algorithm sharing state is "usable" (i.e. executable-only by others), then it should not be forkable on the UIIn the staging, system, the algorithm "AntonioCandia/hist/1" is usable by all, but not readable. So, a fork button should **not** appear on its list line.
Furthermore, clicking on the said button will generate a 404, since the user h...In the staging, system, the algorithm "AntonioCandia/hist/1" is usable by all, but not readable. So, a fork button should **not** appear on its list line.
Furthermore, clicking on the said button will generate a 404, since the user has no access to the algorithm code.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/273500 error when accessing queue permissions2015-08-27T14:43:10ZAndré Anjos500 error when accessing queue permissionsJust hit: http://beatweb-staging/admin/backend/queue/5/permissions/Just hit: http://beatweb-staging/admin/backend/queue/5/permissions/BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/274Sharing modal window does not update w.r.t. shared users/teams2015-11-20T11:24:26ZAndré AnjosSharing modal window does not update w.r.t. shared users/teamsIf a user shares a contribution with another user or a team, there is no way to see who the contribution is shared with (after the contribution page is reloaded).
It would be good if the sharing modal window was correctly pre-filled w...If a user shares a contribution with another user or a team, there is no way to see who the contribution is shared with (after the contribution page is reloaded).
It would be good if the sharing modal window was correctly pre-filled with the people/teams the contribution was shared with.Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/278[swagger] Is currently broken2015-09-01T17:03:51ZAndré Anjos[swagger] Is currently brokenIt complains it cannot visit one of the required web pages. Hitting on it, for example:
http://beatweb-staging/docs/api-docs/api/v1/reports
Shows:
![Screen_Shot_2015-09-01_at_15.45.20](https://gitlab.idiap.ch/biometric/beat.web/...It complains it cannot visit one of the required web pages. Hitting on it, for example:
http://beatweb-staging/docs/api-docs/api/v1/reports
Shows:
![Screen_Shot_2015-09-01_at_15.45.20](https://gitlab.idiap.ch/biometric/beat.web/uploads/5d088ce45de4107fa8e309ba2deaa1e0/Screen_Shot_2015-09-01_at_15.45.20.png)
BTAS TutorialSamuel GAISTSamuel GAISThttps://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/316[reports] error to export a table2015-10-29T09:12:10ZSébastien MARCEL[reports] error to export a tableon beat staging I created a new report
http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/
when trying to export the table it generates a link data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 that my web brows...on beat staging I created a new report
http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/
when trying to export the table it generates a link data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 that my web browser (Safari) is not able to open.
Error message:
Safari ne parvient pas à ouvrir la page « data:blob:http://beatweb-staging/1f829b44-7fa5-4165-b9f8-3f4039f61365 » en raison de l’erreur « L’opération n’a pas pu s’achever. (kCFErrorDomainCFNetwork erreur -10). » (kCFErrorDomainCFNetwork:-10)
Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/317[reports] adding measure type (%, time) in tables2015-12-03T12:43:37ZSébastien MARCEL[reports] adding measure type (%, time) in tablesAdding on the first row of table the measure type (%, time, ...) for each columns would be beneficial:
E.g in http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/ (% and time in seconds ?).
Adding on the first row of table the measure type (%, time, ...) for each columns would be beneficial:
E.g in http://beatweb-staging/reports/smarcel/fr-dct-ubm-gmm/ (% and time in seconds ?).
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/318[toolchains] Editor gets really small if object is documented2015-10-29T17:50:31ZAndré Anjos[toolchains] Editor gets really small if object is documentedFor example, try to fork:
http://beatweb-staging/toolchains/anjos/livdet-lda/1/
Result screen:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/8197663fad88091908b40b09dc31380b/image.png)
For example, try to fork:
http://beatweb-staging/toolchains/anjos/livdet-lda/1/
Result screen:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/8197663fad88091908b40b09dc31380b/image.png)
Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/321[notification] Quirks2015-11-13T15:49:38ZAndré Anjos[notification] QuirksFor some reason, the following is happening (staging):
1) I get "failed" e-mail notifications for cached (successful) experiments. How to reproduce: fork a successful experiment, run it, wait for the e-mail.
2) I don't get an e-mai...For some reason, the following is happening (staging):
1) I get "failed" e-mail notifications for cached (successful) experiments. How to reproduce: fork a successful experiment, run it, wait for the e-mail.
2) I don't get an e-mail for experiments that execute, but fail.Final DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/338[multiple] History viewer rows are out of place after new design merger2015-12-15T14:43:01ZAndré Anjos[multiple] History viewer rows are out of place after new design mergerAfter our new design merger, we now have a history viewer in which rows are out of order.
@philip.abbet: could you please have a look at this and try to understand the reason of this misplacement? (Likely a change from my side, but I'...After our new design merger, we now have a history viewer in which rows are out of order.
@philip.abbet: could you please have a look at this and try to understand the reason of this misplacement? (Likely a change from my side, but I'm not sure where that would be.)Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/339[experiments] Re-running reset experiments generates invalid results2015-12-01T14:22:44ZAndré Anjos[experiments] Re-running reset experiments generates invalid resultsResult screen after re-running an experiment that was reset:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/891489c5dc0a7469fc52924195060fe3/image.png)
Result screen after re-running an experiment that was reset:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/891489c5dc0a7469fc52924195060fe3/image.png)
Final DocumentationAndré 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/342[experiments] Blocks on result display are out of order2015-11-20T12:02:29ZAndré Anjos[experiments] Blocks on result display are out of order![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/59cf206f5c8587a9de80686b420c2114/image.png)
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/59cf206f5c8587a9de80686b420c2114/image.png)
André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/343[experiments] Cancel page refresh if not on "Result Display" mode2015-12-10T14:50:41ZAndré Anjos[experiments] Cancel page refresh if not on "Result Display" modeOtherwise user changes may be forgotten.Otherwise user changes may be forgotten.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/344[attestations] Show all existing attestations on user page2015-11-20T11:48:42ZAndré Anjos[attestations] Show all existing attestations on user pagePresently, only user attestations are displayed. This is not true any longer for all other contribution types.Presently, only user attestations are displayed. This is not true any longer for all other contribution types.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/345[ui] More meaningful names for tabs on main page2015-12-01T14:21:54ZSébastien MARCEL[ui] More meaningful names for tabs on main pagehttp://beatweb-staging/events/smarcel/
Events -> Activity ?
this could be a place to put also later on a Leaderboard
System Objects -> Resources (Data and Computing)
For the others what about sticky to the Open Science terminol...http://beatweb-staging/events/smarcel/
Events -> Activity ?
this could be a place to put also later on a Leaderboard
System Objects -> Resources (Data and Computing)
For the others what about sticky to the Open Science terminology ( https://en.wikipedia.org/wiki/Open_science ) ?
Objects -> Open Source -- it might not be 100% correct if we accommodate binaries are some point !
Queries -> Open Access
Note that the Teams can me moved from Objects to Queries as it is a sharing feature.
My 2 cents
Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/347[staging] impossible to fill documentation when expe running2015-11-24T10:38:25ZSébastien MARCEL[staging] impossible to fill documentation when expe runningimpossible to fill documentation when expe running because of automatic page reload
impossible to fill documentation when expe running because of automatic page reload
https://gitlab.idiap.ch/beat/beat.web/-/issues/348[experiments] Green toolchain filling while running2015-12-11T10:30:57ZSébastien MARCEL[experiments] Green toolchain filling while runningWhen running an experiment we don't see anymore the process in "green" on the graphical representation of the toolchain.
This would have to be hooked in into the new setup page.When running an experiment we don't see anymore the process in "green" on the graphical representation of the toolchain.
This would have to be hooked in into the new setup page.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/349[staging] cache occupancy incorrect ?2015-11-24T10:21:36ZSébastien MARCEL[staging] cache occupancy incorrect ?on http://beatweb-staging/backend/scheduler/ the cache occupancy is indicated as 100% which is clearly not true.
on http://beatweb-staging/backend/scheduler/ the cache occupancy is indicated as 100% which is clearly not true.
https://gitlab.idiap.ch/beat/beat.web/-/issues/350[teams] list of teams a user is part of but not created2015-11-30T14:52:30ZSébastien MARCEL[teams] list of teams a user is part of but not createdExample: http://beatweb-staging/teams/smarcel/
it will be good to list also the team a user is part of even if that team is not created by that userExample: http://beatweb-staging/teams/smarcel/
it will be good to list also the team a user is part of even if that team is not created by that userFinal Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/351[staging] list of shared objects within a team inconsistent ?2015-11-24T10:35:44ZSébastien MARCEL[staging] list of shared objects within a team inconsistent ?I have the impression that the detailed sharing information if
For instance for this "shared" toolchain http://beatweb-staging/toolchains/smarcel/eigenface_prepro/1/ I can see the persons it is shared with but not for:
http://beatwe...I have the impression that the detailed sharing information if
For instance for this "shared" toolchain http://beatweb-staging/toolchains/smarcel/eigenface_prepro/1/ I can see the persons it is shared with but not for:
http://beatweb-staging/toolchains/chichan/full_mlbphs_projection/1/
Also for http://beatweb-staging/experiments/anjos/ivana7c/simple-antispoofing-updated/1/ivanas-experiment/ I don't see the sharing details although it is indicated as shared
https://gitlab.idiap.ch/beat/beat.web/-/issues/352[dataformats] Invalid data format may generate 500 error on "fork"2015-11-30T14:50:47ZAndré Anjos[dataformats] Invalid data format may generate 500 error on "fork"Upon forking a dataformat, the user may slightly modify the said format and generate an internal logical error leading to a 500 page displayed.
I just received this e-mail from our beat.web server:
```text
Internal Server Error: /...Upon forking a dataformat, the user may slightly modify the said format and generate an internal logical error leading to a 500 page displayed.
I just received this e-mail from our beat.web server:
```text
Internal Server Error: /platform/dataformats/fork/chichan/a-collection-of-linear_machines/1/
Traceback (most recent call last):
File "/remote/sw/beat.env.web-0.0.1/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/remote/sw/beat.env.web-0.0.1/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 110, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/remote/sw/beat.env.web-0.0.1/usr/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view
return view_func(request, *args, **kwargs)
File "/remote/sw/beat.web/src/beat.web/beat/web/dataformats/views.py", line 165, in fork_dataformat
dataformat.author.username,
AttributeError: 'NoneType' object has no attribute 'author'
```
Indeed, this bit of code needs protection:
```python
if form.is_valid():
(dataformat, errors) = DataFormat.objects.create_dataformat(
author=request.user,
name=form.cleaned_data['name'],
short_description=form.cleaned_data['short_description'],
description=form.cleaned_data['description'],
declaration=form.cleaned_data['file'],
fork_of=fork_of
)
# Redirect to the page of the dataformat just created
return HttpResponseRedirect(
reverse('dataformats-view',
args=(
dataformat.author.username,
dataformat.name,
dataformat.version,
),
)
)
```
For example, it does not handle the case in which the "validation" generates an error and the returned data format is `None`, generating the error above. This code must be corrected both on the branch "0.14" as well as on the "master" branch.Final DocumentationSamuel GAISTSamuel GAISThttps://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/363[ui] Navigation problem2015-12-17T10:57:49ZPhilip ABBET[ui] Navigation problemWhen you go on a page with tabs (for example: http://beatweb-staging/toolchains/anjos/livdet-lda/1/) and you click on one tab (say: "Experiments"), when you click on the "Back" button of your browser, nothing happens.
You don't come b...When you go on a page with tabs (for example: http://beatweb-staging/toolchains/anjos/livdet-lda/1/) and you click on one tab (say: "Experiments"), when you click on the "Back" button of your browser, nothing happens.
You don't come back on the first tab you were one, nor on the previous page. Another click on "Back" will send you to the previous page in the history.
The URL change in the browser, but not the content of the page.
Tested in Chrome and Firefox.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.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/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/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/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/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/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/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/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/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/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/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 ABBET