beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2014-11-21T11:50:14Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/80validate_queue_environment() does not work well2014-11-21T11:50:14ZLaurent EL SHAFEYvalidate_queue_environment() does not work wellWhile performing some update on the database, we noticed that validate_queue_environment() was not validating a tuple (Queue, Env), which seemed to be correct. We have to investigate why.
https://gitlab.idiap.ch/biometric/beat.web/blo...While performing some update on the database, we noticed that validate_queue_environment() was not validating a tuple (Queue, Env), which seemed to be correct. We have to investigate why.
https://gitlab.idiap.ch/biometric/beat.web/blob/master/beat/web/experiments/models.py#L35Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/79Cancelled experiment page is wrong when no associated jobs was cancelled2014-11-20T14:49:24ZLaurent EL SHAFEYCancelled experiment page is wrong when no associated jobs was cancelledThe cancelled experiment page does not show any useful information, when the cancellation of this experiment does not involve the cancellation of a specific job. In this case, we get the configuration page for this experiment instead of ...The cancelled experiment page does not show any useful information, when the cancellation of this experiment does not involve the cancellation of a specific job. In this case, we get the configuration page for this experiment instead of a page indicated that the experiment has been cancelled.
I do not know the exact cause of the problem. I suspect that the lack of error message such as 'Job x was cancelled by an external user agent' leads to the problem.Second BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/78Locked attestations do not properly expire2015-11-20T11:36:56ZAndré AnjosLocked attestations do not properly expireThe `creation_date` is correctly set for all locked attestations. The `publication_date` is set for all public attestations. The only thing we need to implement to get this going is:
- [x] A warning on the locked attestation page that t...The `creation_date` is correctly set for all locked attestations. The `publication_date` is set for all public attestations. The only thing we need to implement to get this going is:
- [x] A warning on the locked attestation page that tells the user about the remaining unlock time (which is a constant on the `settings.py` file for the project.
- [x] A cronjob that runs a (very simple) script that, for all attestations w/o publication_date, compares the current date to the creation date and deletes that attestation (just the attestation, not the experiment) if the time difference pass a threshold.Final Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/77Backend page time out since partitions are now -noac mounted2014-12-02T12:12:52ZLaurent EL SHAFEYBackend page time out since partitions are now -noac mountedThe backend page now seems to time out when e.g. a clean-up is performed.
This is caused by the use of the -noac NFS flag while mounting the partition on beatsched, which affects the filesystem performance.The backend page now seems to time out when e.g. a clean-up is performed.
This is caused by the use of the -noac NFS flag while mounting the partition on beatsched, which affects the filesystem performance.Second BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/76Cannot reset database configurator2015-06-17T15:02:41ZLaurent EL SHAFEYCannot reset database configuratorIt is currently not possible to reset the database configurator from its discrete state into the database protocol selector format. It would be nice to have a reset button to allow the user to do so on the experiment confiugration page.It is currently not possible to reset the database configurator from its discrete state into the database protocol selector format. It would be nice to have a reset button to allow the user to do so on the experiment confiugration page.BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/75Cannot use same analysis tool twice2014-11-21T10:53:29ZManuel GüntherCannot use same analysis tool twiceThe short verison: When I have two analyzers that output the same name, only one of it is shown in the result section.
The longer version:
I have a complicated toolchain, including dev and eval sets.
In total, I have three analyzers...The short verison: When I have two analyzers that output the same name, only one of it is shown in the result section.
The longer version:
I have a complicated toolchain, including dev and eval sets.
In total, I have three analyzers, one computing EER and HTER from both sets, and an ROC curve generator for each of the sets.
In my experiment, I use the simple algorithm to plot the ROC curves for both the dev and eval set. I expected two plots. However, since the output of the ROC algorithm is called "ROC" and there is no way to change this name in the toolchain, I get only one ROC curve displayed (I guess the one that was produced first).
See: https://www.beat-eu.org/platform/experiments/siebenkopf/FaceRec-NoTraining/1/PhaseDiffPlusCanberra_TT_Banca_P8/ if you can.
https://gitlab.idiap.ch/beat/beat.web/-/issues/74Error reading parameter for analysis block2014-11-21T12:02:48ZManuel GüntherError reading parameter for analysis blockI continue receiving "internal BEAT system error"s while trying to access a parameter in an analysis block. The relevant code is something like:
```python
## INPUTS
## scores: tutorial/probe_scores/1
## INPU...I continue receiving "internal BEAT system error"s while trying to access a parameter in an analysis block. The relevant code is something like:
```python
## INPUTS
## scores: tutorial/probe_scores/1
## INPUTS_END
## RESULTS
## ROC: beat/chart/1
## RESULTS_END
## PARAMETERS
## points: uint16 100
## PARAMETERS_END
import bob
class Algorithm:
def __init__(self):
self.positives = []
self.negatives = []
def setup(self, parameters):
self.points = parameters.get('points', 100)
return True
def process(self, inputs, output):
...
roc = bob.measure.roc(self.negatives, self.positives, self.points)
...
return True
```
(see https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/6, if you can). Second BEAT Reviewhttps://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.core/-/issues/20Reliability of data I/O2017-08-06T11:17:04ZAndré AnjosReliability of data I/OSimilarly to what we did for the indexes, we should also promote some check-summing capabilities for the data which is produced and consumed in our environments. I leave this open for discussion here.Similarly to what we did for the indexes, we should also promote some check-summing capabilities for the data which is produced and consumed in our environments. I leave this open for discussion here.Second BEAT ReviewLaurent EL SHAFEYLaurent EL SHAFEYhttps://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 ABBEThttps://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/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.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/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/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/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/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/64Possibility to reset a failed experiment2014-12-02T11:54:03ZAndré AnjosPossibility to reset a failed experimentIt would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. Fo...It would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. For those situations, the user may reset the experiment, which would take him to the configuration page again.
The experiment model class in our Django app already supports the "reset()" functionality, which is successfuly used in the admin page already. This ticket is only about hooking in the possibility to reset from the result page itself.Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/63When a block takes longer than the computation time allowed by a queue, the e...2014-11-06T13:12:18ZPedro TOMEWhen a block takes longer than the computation time allowed by a queue, the experiment is stopped without a precise error messageIf the computation of a block takes longer than the duration allowed by a queue, the experiment is aborted as expected.
However, the only information the user get back is 'ERROR' and the experiment page does not mention anything about...If the computation of a block takes longer than the duration allowed by a queue, the experiment is aborted as expected.
However, the only information the user get back is 'ERROR' and the experiment page does not mention anything about this fact.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://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 Tour