beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-11-03T15:23:12Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/15Pull experiment does not work properly for user 'tutorial'2018-11-03T15:23:12ZLaurent EL SHAFEYPull experiment does not work properly for user 'tutorial'When trying to pull experiments:
```sh
../bin/beat exp pull --user tutorial
```
we end up with:
```text
Pulling the experiment tutorial/eigenface/Test17
The toolchain isn't valid, due to the following errors:
Errors w...When trying to pull experiments:
```sh
../bin/beat exp pull --user tutorial
```
we end up with:
```text
Pulling the experiment tutorial/eigenface/Test17
The toolchain isn't valid, due to the following errors:
Errors with the algorithm 'tutorial/postperf': Failed to find the algorithm file
```Biometrics Center Kickoff Meeting and BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://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.examples/-/issues/4Improve documentation for all databases2017-10-04T21:58:17ZAndré AnjosImprove documentation for all databasesInsert both short and long documentation strings for every database in this package.
Take the following page as input: https://gitlab.idiap.ch/biometric/beat.databases/wikis/homeInsert both short and long documentation strings for every database in this package.
Take the following page as input: https://gitlab.idiap.ch/biometric/beat.databases/wikis/homeRP Conference, Darmstadt, DEhttps://gitlab.idiap.ch/beat/beat.web/-/issues/20Improve deletion of databases from Django administration page2017-08-23T11:36:30ZLaurent EL SHAFEYImprove deletion of databases from Django administration pageThe current behaviour when deleting a database from Django administration page is as follows:
- Deletion of the 'Database' entry
- Deletion of the 'Database protocol' entries
- Deletion of the 'Database set' entries
Since adding a ...The current behaviour when deleting a database from Django administration page is as follows:
- Deletion of the 'Database' entry
- Deletion of the 'Database protocol' entries
- Deletion of the 'Database set' entries
Since adding a database may also imply adding a 'Database set template' and 'Database output's, it would be better to remove these entries as well, when they are not used by any other databases installed on the platform.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/19The toolchain editor generates invalid toolchains2014-09-04T11:59:49ZTiago de Freitas PereiraThe toolchain editor generates invalid toolchains- [X] Let say that you have 3 blocks A, B and C. The block A is a dataset block and the blocks B and C are regular blocks.
When you create a connection between blocks A and B, the connection uses the synchronization channel from A. Righ...- [X] Let say that you have 3 blocks A, B and C. The block A is a dataset block and the blocks B and C are regular blocks.
When you create a connection between blocks A and B, the connection uses the synchronization channel from A. Right after that, when you try to create a connection between the blocks A and C (using the same field on the "A" side), the synchronization channel is null, which invalidates the toolchain. Additionally, it is not possible to fix it.
- [X] In the same example as above (blocks A,B and C), when you create a connection between the blocks A and B, it is not possible to create a connection between A and C (using the same field in the "A" side). The only possible way is to create a connection between C and A. I know this is the same thing, but it is not intuitive.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/18Avoid particle "it" on experiment buttons2017-08-23T11:36:30ZAndré AnjosAvoid particle "it" on experiment buttonsTo standardize the button labels everywhere, would it be possible to remove the particle "it" from buttons like "fork it" and "cancel it"?
It is implicit from the context that it refers to the currently running experiment.To standardize the button labels everywhere, would it be possible to remove the particle "it" from buttons like "fork it" and "cancel it"?
It is implicit from the context that it refers to the currently running experiment.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/17Updating an algorithm which is used by experiment on the platform leads to th...2014-09-03T15:09:05ZIvana CHINGOVSKAUpdating an algorithm which is used by experiment on the platform leads to the deletion of this experimentHere are the steps to replicate the problem:
1. Create an experiment on the platform
2. On a local machine, pull an algorithm used by this experiment, modify it
3. Upload the modified version of the algorithm on the platform
Resu...Here are the steps to replicate the problem:
1. Create an experiment on the platform
2. On a local machine, pull an algorithm used by this experiment, modify it
3. Upload the modified version of the algorithm on the platform
Results:
The experiment disappears.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.core/-/issues/14createDataFromJSON() is failing on arrays of arrays structures2018-11-03T15:23:12ZLaurent EL SHAFEYcreateDataFromJSON() is failing on arrays of arrays structuresThe function createDataFromJSON() is failing on arrays of array structures, such as:
```
{
"input_subtract": "beat/array_1d_floats",
"input_divide": "beat/array_1d_floats",
"weights": [
0,
"beat/a...The function createDataFromJSON() is failing on arrays of array structures, such as:
```
{
"input_subtract": "beat/array_1d_floats",
"input_divide": "beat/array_1d_floats",
"weights": [
0,
"beat/array_2d_floats"
],
"biases": [
0,
"beat/array_1d_floats"
]
}
```
This currently generates the error:
*** ValueError: field named value not found.
where 'value' is the key of the 'beat/array_*' dictionary.https://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.core/-/issues/11(Local) Paced development2018-08-02T06:30:28ZAndré Anjos(Local) Paced developmentWhen the user develops a bit toolchain, s/he cannot test the toolchain if algorithms for *all* blocks are not implemented. This makes development a bit hard and demotivating.
A simple solution to this problem would be to implement som...When the user develops a bit toolchain, s/he cannot test the toolchain if algorithms for *all* blocks are not implemented. This makes development a bit hard and demotivating.
A simple solution to this problem would be to implement some sort of "noop" algorithm that could live inside the "beat" user account.
In local execution mode (with `beat run`), if such an algorithm would be found, then it would not execute the current algorithm or any other following it. This would allow the user to place "beat/noop" as an algorithm in all blocks to be developed and focus on a single block at a time.https://gitlab.idiap.ch/beat/beat.web/-/issues/16Q&A Forum2017-08-23T11:36:31ZAndré AnjosQ&A ForumForum - a la Stack-Overflow, hooked into the reputation system (relates to issue #13).Forum - a la Stack-Overflow, hooked into the reputation system (relates to issue #13).https://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/13Reputation system2016-03-14T18:30:44ZAndré AnjosReputation systemHow to assign and benefit for reputation.
Feel free to edit this bug with details.How to assign and benefit for reputation.
Feel free to edit this bug with details.https://gitlab.idiap.ch/beat/beat.web/-/issues/12Online code editor2014-10-06T10:18:58ZAndré AnjosOnline code editorFeatures:
- [x] Implementation à là github/gitlabFeatures:
- [x] Implementation à là github/gitlabBiometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/11Online documentation editor2017-08-23T11:36:43ZAndré AnjosOnline documentation editorFeatures:
- [x] Work à là github/gitlab issue edit.
- [x] Format of choice should be reestructured-text.Features:
- [x] Work à là github/gitlab issue edit.
- [x] Format of choice should be reestructured-text.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://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é Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/9Result display and search: missing features2015-11-10T12:02:44ZAndré AnjosResult display and search: missing featuresThe result search and display has been recently revamped.
Here is a list of missing features yet to be implemented:
- [X] Display only default (`+`) results
- [ ] The parameters, names of algorithms, versions, should be display-a...The result search and display has been recently revamped.
Here is a list of missing features yet to be implemented:
- [X] Display only default (`+`) results
- [ ] The parameters, names of algorithms, versions, should be display-able at the search results.
- [X] Filter out columns from the results on user request
- [ ] Order columns from the results on user request
- [x] Save searches (implement user micro-site tab)
- [x] Sharing of saved search results
- [ ] Modify front page to display public searches instead of public toolchains, which are less useful.
- [ ] It should be possible to export figures and tables in a search result for scientific publishing. Plotting should also be improved. It is far from scientific standards of today. E.g., it would be nice to get it exported into PDF, with nice fonts and configurable colors. A compromise would be to export the plotting data and let the user handle it the way they want.
- [ ] It should be possible to annex complementary search results when showing previous results. This gives users an overview if a certain result is still representative of the state-of-the-art, for example. It also allows for recommendations.
Final DocumentationPhilip ABBETPhilip ABBET