beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-11-19T15:41:27Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/335[reports] Display bug in Report2015-11-19T15:41:27ZSushil BHATTACHARJEE[reports] Display bug in ReportPlease refer to the following report:
https://www.beat-eu.org/platform/reports/990149671/
The table in the report, comparing two experiments, displays the statistics for only
one experiment. The values for the other experiment are n...Please refer to the following report:
https://www.beat-eu.org/platform/reports/990149671/
The table in the report, comparing two experiments, displays the statistics for only
one experiment. The values for the other experiment are not visible.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/337[reports] button settings and delete visible in edition mode via number access2015-11-20T08:37:27ZFlavio TARSETTI[reports] button settings and delete visible in edition mode via number accessThis should be removedThis should be removedFinal DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/281[plotter] Parameters are not associated to Plotters2015-11-20T11:23:06ZAndré Anjos[plotter] Parameters are not associated to PlottersThey should, otherwise we'll see parameters sometimes related to specific plotters showing up everywhere.They should, otherwise we'll see parameters sometimes related to specific plotters showing up everywhere.Final DocumentationAndré AnjosAndré Anjoshttps://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/268[algorithms] View successful environments in which algorithm was run2015-11-20T11:24:59ZAndré Anjos[algorithms] View successful environments in which algorithm was runIn order to improve usability and predictability of algorithm behaviour on new environments, it would be good to display statistics of algorithm usage on environments, w.r.t. success on experiments/blocks.
For that purpose, I have imp...In order to improve usability and predictability of algorithm behaviour on new environments, it would be good to display statistics of algorithm usage on environments, w.r.t. success on experiments/blocks.
For that purpose, I have implemented modifications to the schema and new methods that allow us to easily query for ``environments()`` in which an algorithm has successfully ran. The method ``beat.web.algorithms.Algorithm.environments()`` now returns a dictionary object that has as keys the environment objects and as values the number of times the algorithm has been used with that environment on a successful experiment (or block [status == Block.CACHED], in case the experiment has failed).
I'm not sure how to best plug this django method so that we can visualise the results on an algorithm display page. Could one of you please do it?
I think the idea is to:
1. Update the serialiser for the algorithm class, to include ``environments``
2. Display the environments with the algorithm display page.Final Documentationhttps://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/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/235Cannot jump to algorithm/toolchain page from a (completed/failed) experiment ...2015-11-20T11:27:21ZLaurent EL SHAFEYCannot jump to algorithm/toolchain page from a (completed/failed) experiment pageWhen an experiment is being configured, it is possible to visualize the algorithm code and/or the toolchain.
In contrast, once an experiment has completed (or failed), the number of links on the webpage is very limited.
Besides, the ...When an experiment is being configured, it is possible to visualize the algorithm code and/or the toolchain.
In contrast, once an experiment has completed (or failed), the number of links on the webpage is very limited.
Besides, the algorithm name may only be partially visible by looking at the toolchain graph. It would be better to have entry points to both the algorithm and the toolchain pages, similarly to what we have when we set up an experiment.
Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/234Feature request2015-11-20T11:27:43ZSébastien MARCELFeature requestJust my 2 cent.
Will it be possible to give a user the possibility to report an issue on gitlab directly from popup window with the error message by clicking on a button in that windows ?Just my 2 cent.
Will it be possible to give a user the possibility to report an issue on gitlab directly from popup window with the error message by clicking on a button in that windows ?Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/230E-mail notification upon sharing2015-11-20T11:28:35ZAndré AnjosE-mail notification upon sharingIt would be a good feature to allow users to globally enable notification when something is shared with them.
As @philip.abbet pointed out, it would be good if e-mails could be summarized in case a lot has been just shared with a pers...It would be a good feature to allow users to globally enable notification when something is shared with them.
As @philip.abbet pointed out, it would be good if e-mails could be summarized in case a lot has been just shared with a person (e.g., when sharing an experiment, this normally includes algorithms, dataformats, the toolchain, libraries, etc). At this point, it would be best to receive a single e-mail listing all objects from the last sharing actions.
We should also think about the situation where various experiments are shared at once and avoid the e-mail spam once more on this case.
This feature could also have a hook to our to-be-implemented "activity" tab.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/215Possibility to delete locked attestations2015-11-20T11:31:10ZAndré AnjosPossibility to delete locked attestationsIt would be nice if the user could delete locked (still not public) attestations. IMO, there is no reason why a "private" attestation could not be deleted by the user requesting it.
Unlocked attestations should not be deletable as the...It would be nice if the user could delete locked (still not public) attestations. IMO, there is no reason why a "private" attestation could not be deleted by the user requesting it.
Unlocked attestations should not be deletable as they are already.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/216Locked attestations with other user's components could be improved2015-11-20T11:32:41ZAndré AnjosLocked attestations with other user's components could be improvedWhen the user goes to unlock an attestation by clicking on the respective button at the attestation page, in the case none of the components belong to that user, the display could be improved (see image).
![image](https://gitlab.idiap...When the user goes to unlock an attestation by clicking on the respective button at the attestation page, in the case none of the components belong to that user, the display could be improved (see image).
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/2475fa071eb26ef4b83ea600d311924b/image.png)
From the other perspective, unlocking an attestation with components which belong to the user shows components which are already public (see the second image).
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/255ad59e963468252dbab1679f87f072/image.png)
I wonder if we should not have a more consistent display through these use cases. A suggestion:
1. Always display all components involved or leave the option to display them by following a link, for example (if space is an issue on this pop-up)
2. If a component is public already, indicate so
3. If an algorithm is public and/or open-source, indicate soFinal Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/180Search: More flexible filters specification2015-11-20T11:33:46ZPhilip ABBETSearch: More flexible filters specificationAt the Search page, it would be good to be able to add logical-OR conditionals. Grouping of ANDs and ORs would be a plus.
**The report feature could be seen has a workaround for this feature!**At the Search page, it would be good to be able to add logical-OR conditionals. Grouping of ANDs and ORs would be a plus.
**The report feature could be seen has a workaround for this feature!**Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/82Harmonisation of statistics and processing times sent by the scheduler2015-11-20T11:35:02ZAndré AnjosHarmonisation of statistics and processing times sent by the schedulerWe must harmonize the displaying of computing power informed by the scheduler and calculated by the worker in some way. Currently, we find some inconsistencies between the values displayed on the user page (experiments tab) and the "sequ...We must harmonize the displaying of computing power informed by the scheduler and calculated by the worker in some way. Currently, we find some inconsistencies between the values displayed on the user page (experiments tab) and the "sequential processing" times displayed on the experiment page.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/42Multi-resolution support2015-11-20T11:36:14ZAndré AnjosMulti-resolution supportSome of our pages at the website are no well-adapated to smaller displays. When running representations on low-resolution projectors or using tablets and phones, it would be nice that the data presented is, at least, not overlapping.
...Some of our pages at the website are no well-adapated to smaller displays. When running representations on low-resolution projectors or using tablets and phones, it would be nice that the data presented is, at least, not overlapping.
A specialised page for small devices would be a plus.Final DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/78Locked attestations do not properly expire2015-11-20T11:36:56ZAndré AnjosLocked attestations do not properly expireThe `creation_date` is correctly set for all locked attestations. The `publication_date` is set for all public attestations. The only thing we need to implement to get this going is:
- [x] A warning on the locked attestation page that t...The `creation_date` is correctly set for all locked attestations. The `publication_date` is set for all public attestations. The only thing we need to implement to get this going is:
- [x] A warning on the locked attestation page that tells the user about the remaining unlock time (which is a constant on the `settings.py` file for the project.
- [x] A cronjob that runs a (very simple) script that, for all attestations w/o publication_date, compares the current date to the creation date and deletes that attestation (just the attestation, not the experiment) if the time difference pass a threshold.Final Documentationhttps://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/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/320[reports] Problem with the precision and labels update2015-11-23T06:57:26ZTiago de Freitas Pereira[reports] Problem with the precision and labels updateWhen you have an empty report and starts to work on it, the events that need a refresh, such as, the precision update, the experiment labels and so on do not work. These things only start to work smoothly when you refresh the page.
St...When you have an empty report and starts to work on it, the events that need a refresh, such as, the precision update, the experiment labels and so on do not work. These things only start to work smoothly when you refresh the page.
Steps to reproduce the issue:
- Create a new report;
- Add some experiments on it;
- Open the report;
- Add a table;
- Change the floating point precision (this will not work);
- Refresh the page (F5)
- Change the floating point precision (Now starts to work properly);
Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://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.