beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2017-08-06T11:17:04Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/21Output method write() is not able to process beat.core.Data instances2017-08-06T11:17:04ZManuel GüntherOutput method write() is not able to process beat.core.Data instancesThe output method write() is currently not able to process beat.core.Data instances.
This means that when a complex data structure is read from the inputs and that this input has to be written in one of the outputs, the user currently...The output method write() is currently not able to process beat.core.Data instances.
This means that when a complex data structure is read from the inputs and that this input has to be written in one of the outputs, the user currently has to convert it into a JSON like python dictionary.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/71Inserting an invalid JSON for a database generates a beat.web error2015-03-18T12:52:42ZAndré AnjosInserting an invalid JSON for a database generates a beat.web errorA simple test is to copy-paste the JSON containing version and short doc strings.A simple test is to copy-paste the JSON containing version and short doc strings.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/19More robust JSON validation2017-08-06T11:17:04ZAndré AnjosMore robust JSON validationWe currently have in place a hand-crafted JSON validation strategy for the many JSON bits we manipulate inside the platform.
I propose we improve JSON validation by introducing [JSON schemas](http://json-schema.org/) for every piece o...We currently have in place a hand-crafted JSON validation strategy for the many JSON bits we manipulate inside the platform.
I propose we improve JSON validation by introducing [JSON schemas](http://json-schema.org/) for every piece of JSON we handle in the platform. There is a [Python package available on PyPI](https://pypi.python.org/pypi/jsonschema) that is compatible with draft-4 (the latest) of the specification.
Find [here](http://spacetelescope.github.io/understanding-json-schema/), a gentle introduction to JSON schemas.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/18beat experiment pull does not pull all dataformats and complains2017-08-06T11:17:04ZAndré Anjosbeat experiment pull does not pull all dataformats and complainsAfter changes with the version numbers, a simple `beat experiments pull` for a particular experiment does not pull all dataformats required by the experiment anymore. As a result, the experiment cannot be run immediately after.After changes with the version numbers, a simple `beat experiments pull` for a particular experiment does not pull all dataformats required by the experiment anymore. As a result, the experiment cannot be run immediately after.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.examples/-/issues/6Database development is a pain2017-10-04T21:58:16ZAndré AnjosDatabase development is a painCurrently, developing a database for inclusion in the platform is a difficult task.
The user has to practically install a functional beat.web platform on his own machine to do it thoroughly:
1. Create the JSON and RST descriptions ...Currently, developing a database for inclusion in the platform is a difficult task.
The user has to practically install a functional beat.web platform on his own machine to do it thoroughly:
1. Create the JSON and RST descriptions of the database
2. Upload that into the beat.databases package and install the contribution
3. Create a toolchain that can use the database
4. Create a new configuration that uses the database
5. Download all pieces locally so that one can debug the toolchain and make sure all is working fine.
We should try to simplify this a bit.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/53Validation of all Contributions must be more thorough2015-03-18T12:17:09ZAndré AnjosValidation of all Contributions must be more thoroughCurrently, the validation of contributions saved on our database does not go through important accessibility check that must be executed before object insertion.
Namely, the following checks should be performed:
* [x] When the user...Currently, the validation of contributions saved on our database does not go through important accessibility check that must be executed before object insertion.
Namely, the following checks should be performed:
* [x] When the user inserts a data format, that all referenced data formats are accessible
* [x] When the user saves an algorithm that all referenced data formats are acessible
* [x] When the user saves an experiment, that databases, algorithms, analysers, data formats and environments are accessible.
When all these items are checked, we can safely close this bug.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/51Reset statistics if Experiment results are cached, but Experiment is reset fr...2015-05-05T18:24:02ZAndré AnjosReset statistics if Experiment results are cached, but Experiment is reset from the admin interfaceIn the case the Experiment is reset from the admin interface, its cache files are not erased (they cannot since we don't know if they would be shared by other experiments). If the experiment is re-scheduled, the scheduler will not run a ...In the case the Experiment is reset from the admin interface, its cache files are not erased (they cannot since we don't know if they would be shared by other experiments). If the experiment is re-scheduled, the scheduler will not run a single block since all files are cached. When replying to the webserver, the scheduler will indicate successful completion, but no statistics, stdout or stderr will be present.
At this point, the web believes these are empty. Instead, it would be more correct if the backend would try to re-connect old statistics to the experiment instead.Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/49Django Superuser should have access to all website2015-05-04T16:39:08ZAndré AnjosDjango Superuser should have access to all websiteCurrently, the Django super user can edit any object using the admin interface, but it cannot inspect the object using the normal user interface. This is a bit inconsistent. We should modify this behaviour so that, if the user is a super...Currently, the Django super user can edit any object using the admin interface, but it cannot inspect the object using the normal user interface. This is a bit inconsistent. We should modify this behaviour so that, if the user is a super-user, it is granted access to all site objects in all views.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.examples/-/issues/5Installation of FRGC, GBU, LFW and NIST SRE2017-10-04T21:58:17ZAndré AnjosInstallation of FRGC, GBU, LFW and NIST SREA request to install the following databases on the platform.
These have to be "hidden" and usable only by us:
- [x] LFW
- [x] NIST SRE
These can be made public (we have authorizations for that):
- [x] FRGC
- [x] GBUA request to install the following databases on the platform.
These have to be "hidden" and usable only by us:
- [x] LFW
- [x] NIST SRE
These can be made public (we have authorizations for that):
- [x] FRGC
- [x] GBUTutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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.core/-/issues/16beat experiment run does not use external environment2018-11-03T15:23:12ZAndré Anjosbeat experiment run does not use external environmentCurrently, the command to run experiments on the user machine does not rely on the same infrastructure used by the platform to run experiments.
It would be good these two things converged at a certain point.Currently, the command to run experiments on the user machine does not rely on the same infrastructure used by the platform to run experiments.
It would be good these two things converged at a certain point.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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.core/-/issues/13Input management2018-11-03T15:23:12ZAndré AnjosInput managementIt would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.It would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/12Object renaming2018-11-03T15:23:12ZAndré AnjosObject renamingIt should be possible to rename:
- [ ] algorithms
- [ ] dataformats
- [ ] toolchains
- [ ] experiments
The platform should handle renaming gracefully.It should be possible to rename:
- [ ] algorithms
- [ ] dataformats
- [ ] toolchains
- [ ] experiments
The platform should handle renaming gracefully.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.core/-/issues/10Library support2018-11-03T15:23:12ZAndré AnjosLibrary supportA ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installe...A ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installed with the processing environment.
- Libraries should be version-nable such as algorithms.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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é Anjos