beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2015-05-06T10:10:57Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/47Algorithm editor should be smarter2015-05-06T10:10:57ZAndré AnjosAlgorithm editor should be smarterCurrently, the algorithm editor relies on a CodeMirror widget that allows the user to input a Python descriptor of the algorithm.
The algorithm is checked for conformance regarding its inputs, outputs and parameter lists.
It would ...Currently, the algorithm editor relies on a CodeMirror widget that allows the user to input a Python descriptor of the algorithm.
The algorithm is checked for conformance regarding its inputs, outputs and parameter lists.
It would be nicer if the editor would, instead of providing an overall Python text editor, that it worked more like a wizard in which the user would go selecting input and output types or parameters. The final algorithm text would be composed from this form.Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/44User secret keys are not verified2015-03-27T05:59:53ZAndré AnjosUser secret keys are not verifiedIt would be good that, at a certain point, the usage and definition of secret keys by users actually worked for authenticating users.
Today it is not the case.It would be good that, at a certain point, the usage and definition of secret keys by users actually worked for authenticating users.
Today it is not the case.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/32Plotting library request (migrated from github)2015-05-07T08:33:14ZAndré AnjosPlotting library request (migrated from github)It would be useful if the platform provided a set of library functions to allow the creation of charts in easier terms, instead of everyone re-implementing theirs. Bob already provides APIs for plotting. It would make sense that BEAT pro...It would be useful if the platform provided a set of library functions to allow the creation of charts in easier terms, instead of everyone re-implementing theirs. Bob already provides APIs for plotting. It would make sense that BEAT provided a similar API for functionality in Bob:
A good starting point for this API is Bob's plotting API, which is available here.
A tricky plot to perform is a DET curve. I hope this is still possible using RGraph's API.Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/21New django action for experiment deletion2017-08-23T11:36:30ZAndré AnjosNew django action for experiment deletionWe should add a new django admin action (https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/) for treating Experiment objects in the BEAT django DB.
In case this action is clicked by the administrator, it allows him/her t...We should add a new django admin action (https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/) for treating Experiment objects in the BEAT django DB.
In case this action is clicked by the administrator, it allows him/her to:
- Delete the Experiment + all associated results
- Clean-up the cache from the experiment:
* Clean-up local cache entries in the Django DB
* Send a message to the scheduler to delete certain cache files (see biometric/beat.scheduler#10). Notice you don't need to cancel any experiment (in case they are running). The scheduler shall be able to handle this gracefully.
If another experiment shares cache files with the experiment being deleted, then:
1) The cache files of that experiment are also cleaned-up
2) The experiment is marked as "Pending", so the user can re-run it at a later stage (unless the experiment was also running, in which case it will be cancelled by the scheduler automatically).
We understand this is a rather drastic action, but may be required in case of severe cache corruption.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/15Consolidation of platform statistics2015-03-06T08:15:22ZAndré AnjosConsolidation of platform statisticsWe current have an initial implementation for the platform statistics. We need to improve on it so its useful for platform demonstrations and system administration.
It would be nice to integrate this with the new scheduler state as well.We current have an initial implementation for the platform statistics. We need to improve on it so its useful for platform demonstrations and system administration.
It would be nice to integrate this with the new scheduler state as well.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/14User grouping2015-03-27T06:02:04ZAndré AnjosUser groupingTracker for user grouping. Edit as we progress on the understanding of this feature.Tracker for user grouping. Edit as we progress on the understanding of this feature.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/10Usage/Upload of docstrings2017-08-23T11:36:34ZAndré AnjosUsage/Upload of docstringsThe usage and upload of docstrings need to be implemented through out the platform. Currently:
- [x] Database pages generate a 404 error
- [x] Short/Long documentation strings are not very flexible or editable online or even through ...The usage and upload of docstrings need to be implemented through out the platform. Currently:
- [x] Database pages generate a 404 error
- [x] Short/Long documentation strings are not very flexible or editable online or even through the command-line. It would be good to have an interface that is similar to github or gitlab, in which you can attach images to descriptions. I'm not sure how to handle garbage collection in this case (i.e., pictures which are not being used anymore).Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/4Changes to the TOS web site behavior2015-03-18T13:16:48ZAndré AnjosChanges to the TOS web site behaviorBased on discussions with our lawyers and legal partner (Els), I've updated the ToS documentation that is required for Users (i.e. people registering into the platform). Things to do:
1. [x] @Kanma: **URGENT**: Update the ToS using th...Based on discussions with our lawyers and legal partner (Els), I've updated the ToS documentation that is required for Users (i.e. people registering into the platform). Things to do:
1. [x] @Kanma: **URGENT**: Update the ToS using the new `tos.rst` in `docs`.
2. [x] In the ToS, a "Contact Form" is mentioned. This form should be used to notify Idiap of problems with the use or management of the BEAT platform. Currently, this contact form does not exist in our platform. It must be created (with a captcha to avoid spamming). Once that is established, one should replace the placeholder for the contact form in the ToS with the final address. Currently it is set to https://beat-eu.org/platform/contact
3. [x] In discussion with our lawyers, it became clear we need to establish a feature that identifies if a certain **Visitor** (this is != User) is a first time visitor or a recurrent visitor (possibly using cookies). If the visitor is a first time visitor, a banner should pop-up (discretely) and say: "The BEAT Platform, like other sites on the internet, uses cookies to customise your interaction with the platform itself. By visiting the IDIAP BEAT Platform you implicitly acknowledge our Legal Disclaimer." At this point, the words "Legal Disclaimer" should be clickable and point to the `legal_disclaimer.rst` file in the `docs` directory. The file should be displayed like the ToS, as a pop-up. *Users that dismiss the banner, get a cookie indicating they have accepted the disclaimer, with a given version number*.
4. [x] In the Legal Disclaimer, a link to the ToS should be made available. A place holder pointing to "https://beat-eu.org/platform/tos" is there, but should be updated if that changes. Action Point: We should create a URL that points to the ToS like stated.
5. [x] Both the "ToS" and our "Legal Disclaimer" have a version number. Users that access the platform **after** the ToS has been updated, should get a banner pointing to the new ToS. Visitors that access the platform **after** the "Legal Disclaimer" has been updated should also check it again. Note that **Users** don't need to go through the "Legal Disclaimer", just visitors. *This feature can be achieved by comparing the cookie established on the user browser with the current version of the ToS/Legal Disclaimer and showing/updating it*.
6. [x] While we can make sure that a person that does not accept the ToS cannot register, we cannot make sure that a Visitor that does not agree with the Legal Disclaimer will not continue visiting the website. By clicking on the "banner close" button or by popping up the "Legal Disclaimer", the user implicitly agrees with what is said in there. If they don't agree, then they should just leave the website. At this point, creating a mechanism to block the contents may be tricky (@Kanma: what do you think about this?)
After all these items have been implemented, I think we can finally close this issue.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjos