beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2015-08-28T12:46:51Zhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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 TARSETTI