beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2014-11-21T10:37:38Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/61Missing "Environments" panel for the user2014-11-21T10:37:38ZAndré AnjosMissing "Environments" panel for the userWe miss a panel at the user dashboard allow the user to list existing software environments, queue configurations and number of slots available.
This web page should allow the user to visualize existing software environments and brows...We miss a panel at the user dashboard allow the user to list existing software environments, queue configurations and number of slots available.
This web page should allow the user to visualize existing software environments and browser user queues to view the number of slots available and queue properties.
Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/60Experiment configurator block order could be improved2014-11-11T08:33:32ZAndré AnjosExperiment configurator block order could be improvedCurrently, our experiment configurator uses the block order to determine the setup order in the configuration page. This not always translates to a reasonable organisation of the blocks. For example, if the user starts drawing on the rig...Currently, our experiment configurator uses the block order to determine the setup order in the configuration page. This not always translates to a reasonable organisation of the blocks. For example, if the user starts drawing on the right of the page, then the first blocks on the configuration page would be the last ones in the dataflow order. An uninformed user could find this particularly counter-intuitive.
This can be fixed in two ways:
1. We allow the user to setup the "configuration" order by introducing some property that one can set while drawing the toolchain, **or**
2. We try to devise what is the best order by looking at the "x" (ordinate) position of the block.Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://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.web/-/issues/59 Cannot create new version of existing Toolchain2014-11-18T11:51:51ZAndré Anjos Cannot create new version of existing ToolchainI'm not able to create anymore a new version of existing (public) toolchains. This should be possible:
![Screenshot - 311014 - 10:16:56](https://gitlab.idiap.ch/uploads/biometric/beat.web/e1d46fe655/Screenshot_-_311014_-_10_16_56.png)...I'm not able to create anymore a new version of existing (public) toolchains. This should be possible:
![Screenshot - 311014 - 10:16:56](https://gitlab.idiap.ch/uploads/biometric/beat.web/e1d46fe655/Screenshot_-_311014_-_10_16_56.png)
Any ideas?Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.examples/-/issues/8Eigenface and Full-Eigenface algorithms incompatible2017-10-04T21:58:16ZAndré AnjosEigenface and Full-Eigenface algorithms incompatibleOriginally, these toolchains were supposed to share most of the algorithms, but now we realise this is not possible since the input data formats are different.
For example, in the simple eigenface toolchain, image objects are of type ...Originally, these toolchains were supposed to share most of the algorithms, but now we realise this is not possible since the input data formats are different.
For example, in the simple eigenface toolchain, image objects are of type `uint8`, while in the advanced version, image inputs are preprocessed (cropped, corrected, etc) and, therefore are of type `float64`.
We must fix this situation by creating 2 versions of the concerned algorithms.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/7Database UTFVP is taken from the master tip of github2017-10-04T21:58:16ZAndré AnjosDatabase UTFVP is taken from the master tip of githubThis bug is opened until `xbob.db.utfvp` has a proper PyPI page and a version.
What to do:
1. First, the github package must be tagged appropriately
2. The package must be released to PyPI with a version
3. You must modify `beat....This bug is opened until `xbob.db.utfvp` has a proper PyPI page and a version.
What to do:
1. First, the github package must be tagged appropriately
2. The package must be released to PyPI with a version
3. You must modify `beat.env.syspy` so that its buildout does not use the github version anymore
4. You must notify our `beat-devel` mailing list with the precise version that will be used in the platform.
Thanks!Biometrics Center Kickoff Meeting and BEAT ReviewPedro TOMEPedro TOMEhttps://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/58Synchronization channels marked as a black color (unknown channels)2014-11-06T12:56:12ZPedro TOMESynchronization channels marked as a black color (unknown channels)You need to connect the database blocks outputs before the algorithms blocks.
To reproduce the bug:
First connect the synchronization channels between two blocks of the algorithms until the analyzer, after them connect synchronizatio...You need to connect the database blocks outputs before the algorithms blocks.
To reproduce the bug:
First connect the synchronization channels between two blocks of the algorithms until the analyzer, after them connect synchronization channel between the block of the database and the first block of the algorithm.
Problem: The system marks the synchronization channels between the algorithm as black color (unknown channels).
Reported the error: "Invalid synchronized channel"
Solution: Delete the synchronization channels between the blocks and connect in order starting from the database block.https://gitlab.idiap.ch/beat/beat.web/-/issues/57Toolchain editor - Feature Request2019-01-09T16:46:19ZPedro TOMEToolchain editor - Feature RequestI propose the next improvements to improve the editor (by order of priority):
- [ ] ~~Use the right button of the mouse to show an informative menu with the options available in each case: block selected, line selected, blocks and lines...I propose the next improvements to improve the editor (by order of priority):
- [ ] ~~Use the right button of the mouse to show an informative menu with the options available in each case: block selected, line selected, blocks and lines selected, etc.
Possible options: delete, copy, cut, info, etc.~~
- [x] Include 2 new scrollbars (horizontal and vertical) inside of the toolchain map
- [x] Move "Save" and "Close" buttons up and make the editor operate a bit more like an WYSIWYG editor
- [x] Add "Zoom-in" and "Zoom-out" buttons to the new bar on the top, together with the "Save" and "Close" buttons
- [ ] Copy/Paste selected blocks by the mouse. Using the mouse right button (previous point) or the keyboard Crtl+c (linux/windows) or Cmd+c (mac).Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/56Reproducibility of experiments with private databases2015-07-28T13:52:26ZAndré AnjosReproducibility of experiments with private databasesWe have recently introduced the concept of confidentiality with databases. This move brings a new set of possibilities for databases that can be inserted into the platform, but also brings a few restrictions. We must study and find solut...We have recently introduced the concept of confidentiality with databases. This move brings a new set of possibilities for databases that can be inserted into the platform, but also brings a few restrictions. We must study and find solutions for the following use-cases:
- [ ] User wants to publish results for an experiment using a private database.
- [ ] User publishes results for an experiment using a database that later becomes private (e.g. its license is not renewed and we must make it private - i.e., no new experiments can be conducted using it. Existing results remain valid).
Once the proper behaviour has been implemented into the platform, we can safely close this bug.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/55deleting experiment: strange behavior ?2014-11-03T13:17:56ZSébastien MARCELdeleting experiment: strange behavior ?why in some cases I am able to delete an experiment:
https://www.beat-eu.org/platform/experiments/smarcel/tutorial/digit/1/character-recognition-mlp-nhu10-iter50/
and not:
https://www.beat-eu.org/platform/experiments/smarcel/tpereir...why in some cases I am able to delete an experiment:
https://www.beat-eu.org/platform/experiments/smarcel/tutorial/digit/1/character-recognition-mlp-nhu10-iter50/
and not:
https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv/1/test3/
in both base experiments are private
Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/54Incorrect experiment links ?2014-10-28T08:18:57ZSébastien MARCELIncorrect experiment links ?pour certaines experiences example:
https://www.beat-eu.org/platform/search/?query=db:banca%20type:results
quand on clique sur le lien il y a un "/" qui manque:
https://www.beat-eu.org/platform/experiments/tpereirafull_isv/1/PERIOCU...pour certaines experiences example:
https://www.beat-eu.org/platform/search/?query=db:banca%20type:results
quand on clique sur le lien il y a un "/" qui manque:
https://www.beat-eu.org/platform/experiments/tpereirafull_isv/1/PERIOCULAR_ISV_bancaP_10/
au lien de
https://www.beat-eu.org/platform/experiments/tpereira/full_isv/1/PERIOCULAR_ISV_bancaP_10/
autre example avec https://www.beat-eu.org/platform/search/?query=spoofing
sur le lien
https://www.beat-eu.org/platform/user/smarcelface-antispoofing/
ou https://www.beat-eu.org/platform/user/ivana7csimple-antispoofing-updated/
Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://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/52Failed experiment scheduling from user page results in "private" icon being s...2014-10-20T09:08:33ZAndré AnjosFailed experiment scheduling from user page results in "private" icon being shownIf I try to start an experiment from the user micro-site, by clicking on the "play" button on any pending experiment and, at this time, the scheduler is not available for running the experiment, a window pops-up telling me the reason of ...If I try to start an experiment from the user micro-site, by clicking on the "play" button on any pending experiment and, at this time, the scheduler is not available for running the experiment, a window pops-up telling me the reason of the failure. All this is good, the problem comes after I dismiss the window: the experiment icon goes from the "play" button to the "lock" icon, indicating the experiment is now private. Since the experiment did not run, this should not happen. The play button should remain available so the user can try again later.
Note: Reloading the user micro-site seems to "fix" the problem, making me believe this is just a javascript error.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://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/50User page (slight) redesign2014-10-31T09:20:06ZAndré AnjosUser page (slight) redesignAfter some use, I have seconds thoughts about the design I have originally suggested for the user page.
Indeed, the panels on the right (containing user details and connections) occupy far too much space and are not that useful for si...After some use, I have seconds thoughts about the design I have originally suggested for the user page.
Indeed, the panels on the right (containing user details and connections) occupy far too much space and are not that useful for site usage.
I would propose we completely eliminate those panels on the right:
[X] Move the user info into the new "Profile" page, which the user can get to by clicking on its gravatar on the top-right menu bar. This is also the place in which the user must have access to change its password and e-mail details, as well as, reset the API key.
[X] The information on "Your connections" panel on the right should be move into a Tab, like "Experiments", "Toolchains", etc. The tab should be named "Network" and should indicate the number of new items for the user to inspect.
[X] We should also introduce a new tab to cover for "Databases" the given user has access to.
Once all that is in place, you can safely close this bug.
Biometrics Center Kickoff Meeting and BEAT Reviewhttps://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.core/-/issues/17Refer to "ISO/IEC 19795-1:2006 "Biometric performance testing and reporting -...2018-11-03T15:23:12ZLaurent EL SHAFEYRefer to "ISO/IEC 19795-1:2006 "Biometric performance testing and reporting -- Part 1: Principles and framework" in performance evaluationFollowing a remark raised after the RP Conference, it would be nice to implement the biometric metrics according to the ISO standard. In particular, it seems that the ROC displayed during the conference was not respecting the definition ...Following a remark raised after the RP Conference, it would be nice to implement the biometric metrics according to the ISO standard. In particular, it seems that the ROC displayed during the conference was not respecting the definition given in the standard.
One simple option would be to add a reference to the standard in the documentation of the analyzer algorithms.https://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é Anjos