beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-07-13T12:21:08Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/48Databases should be versioned and subject to confidentiality controls2015-07-13T12:21:08ZAndré AnjosDatabases should be versioned and subject to confidentiality controlsCurrently, all installed databases are usable by all registered users.
Given we may not have publication rights for all databases we could potentially insert into the platform, it would be nicer to implement confidentiality controls i...Currently, all installed databases are usable by all registered users.
Given we may not have publication rights for all databases we could potentially insert into the platform, it would be nicer to implement confidentiality controls into databases so that only a controlled subset of people would have access to them.
This would allow us to install databases into the platform that can, for example, only be used within the group context.BTAS Tutorialhttps://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.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/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/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/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/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/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/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/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/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.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/62Cannot delete search and other featurettes2015-06-17T15:02:40ZAndré AnjosCannot delete search and other featurettesIt is currently not possible to delete a stored search from the user dashboard. It would be good to be able to do so, as well as re-configure the search.
Here is a list of featurettes that would be nice to have:
- [x] The user should b...It is currently not possible to delete a stored search from the user dashboard. It would be good to be able to do so, as well as re-configure the search.
Here is a list of featurettes that would be nice to have:
- [x] The user should be able to delete the search
- [x] The user should be able to share the search with other users or make it public
- [x] The user should be able to alter the search and re-save it
- [x] The user should be able to see a column indicating "attested" (certified) results
- [x] The user should be able to filter to only see "attested" (certified) results
- [x] The user should be able to document the search (short and long descriptions)
- [x] ~~The user should be able to hide the filtering panel and only see either the table or plots in a search, together with is description~~BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/65Contribution control through the dash board2015-06-15T13:20:27ZAndré AnjosContribution control through the dash boardCurrently, it is only possible to click on the contribution from the dashboard to actually do something with it.
It would be useful that, when highlighted, the contributions showed buttons to:
- Delete
- Fork
- Share
- View (jus...Currently, it is only possible to click on the contribution from the dashboard to actually do something with it.
It would be useful that, when highlighted, the contributions showed buttons to:
- Delete
- Fork
- Share
- View (just for completeness)
- ~~Browse versions (an arrow to the right and another to the left - in this case, the version number is updated on the display)~~.BEAT TourPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/66Missing tab for attestations2014-11-19T11:56:48ZLaurent EL SHAFEYMissing tab for attestationsThere is currently no way for a user to list his attestations. It would be nice to have a tab showing them with their state (locked/unlocked, expiration time).There is currently no way for a user to list his attestations. It would be nice to have a tab showing them with their state (locked/unlocked, expiration time).Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/67Display error on the backend page2014-11-11T10:18:07ZLaurent EL SHAFEYDisplay error on the backend page1. If the button refresh of the backend page is pressed twice, information about the queue are shown twice.
2. If an environment is deactivated but still present in the work, its box is colored in red. This should not be the case.1. If the button refresh of the backend page is pressed twice, information about the queue are shown twice.
2. If an environment is deactivated but still present in the work, its box is colored in red. This should not be the case.Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/68Synchronization channels between scoring and analyzer do not update correctly2014-11-10T12:15:36ZPedro TOMESynchronization channels between scoring and analyzer do not update correctlyI detected a problem on the synchronization channels.
For reproduce the bug:
0. Use the toolchain: full_fisherface
1. Remove the two cables between the analyzer and the two scoring blocks.
2. Configure the two scoring block by s...I detected a problem on the synchronization channels.
For reproduce the bug:
0. Use the toolchain: full_fisherface
1. Remove the two cables between the analyzer and the two scoring blocks.
2. Configure the two scoring block by synchronization channel of development sets (dev_templates and test_templates), before to connect to the analyzer.
3. Connect the outputs of the scoring blocks to the analyzer.
4. Change the synchronization channels of the scoring blocks to dev_probe and test_probe
5. voila!: the synchronization channel of the analyzer does no change (is configured based on the dev_templates and test_templates)
Solution: Disconnect the cables between the two scoring blocks and the analyzer and reconnect, then you can select in the analyzer the synchronization channel of dev_probe or test_probe
https://gitlab.idiap.ch/beat/beat.web/-/issues/70utfvp database - Incorrect assignation of datasets2014-11-07T07:38:25ZPedro TOMEutfvp database - Incorrect assignation of datasetsError in the configuration of the experiment:
test_templates = utfvp/1/nom/dev_templates
dev_templates = utfvp/1/nom/test_templates
To reproduce the error:
[1] New experiment using the toolchain: ptome/fingervein_advanced
[2] Sele...Error in the configuration of the experiment:
test_templates = utfvp/1/nom/dev_templates
dev_templates = utfvp/1/nom/test_templates
To reproduce the error:
[1] New experiment using the toolchain: ptome/fingervein_advanced
[2] Select Database: 'utfvp/1' and Protocol: 'nom'
[3] Click on 'Advanced mode'
There you can see how the associations for test_templates and dev_templates are wrong.https://gitlab.idiap.ch/beat/beat.web/-/issues/72Experiment setup page error - buttons are greyed out if reset database2014-11-11T08:33:39ZAndré AnjosExperiment setup page error - buttons are greyed out if reset databaseApparently, there is a small error in the JS of experiment configurations. For a forked experiment, if the user resets the database and then sets it to one of the possible values, the "Go" and "Queue" buttons are not reset properly and r...Apparently, there is a small error in the JS of experiment configurations. For a forked experiment, if the user resets the database and then sets it to one of the possible values, the "Go" and "Queue" buttons are not reset properly and remained greyed out.Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/73After sharing algorithm, page doesn't reload2014-11-11T12:37:11ZAndré AnjosAfter sharing algorithm, page doesn't reloadIn an algorithm page (maybe this also happens for other contributions), it would be handy that the sharing information (or the whole page) is reloaded after the user has shared the contribution, to show the change. This currently doesn't...In an algorithm page (maybe this also happens for other contributions), it would be handy that the sharing information (or the whole page) is reloaded after the user has shared the contribution, to show the change. This currently doesn't happen.Second BEAT ReviewPhilip ABBETPhilip ABBET