beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-11-10T11:58:55Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/221Few algorithms do directly use data_index attributes2015-11-10T11:58:55ZLaurent EL SHAFEYFew algorithms do directly use data_index attributesFew algorithms on the platform do directly use data_index{,_end} attributes of the inputs.
The I/O uses the SynchronizationListener class to ensure that outputs are always synchronized with the main input channel.
Therefore, the use of...Few algorithms on the platform do directly use data_index{,_end} attributes of the inputs.
The I/O uses the SynchronizationListener class to ensure that outputs are always synchronized with the main input channel.
Therefore, the use of these attributes in the algorithm side should not be neither required nor allowed.
See the following issue for more details: https://gitlab.idiap.ch/biometric/beat.examples/issues/11
Final Documentationhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/11Do not use of data_index{,_end} in algorithms2017-10-04T21:58:16ZLaurent EL SHAFEYDo not use of data_index{,_end} in algorithmsFew of the algorithms currently use the attribute data_index{,_end} of the inputs.
Since the I/O implements a synchronization mechanism to make sure that outputs are synchronized with the main input channel, this is useless and this bri...Few of the algorithms currently use the attribute data_index{,_end} of the inputs.
Since the I/O implements a synchronization mechanism to make sure that outputs are synchronized with the main input channel, this is useless and this brings an extra level of complexity when isolating the user process from the I/O operations.BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/220User object privacy (encryption)2019-07-04T08:37:03ZAndré AnjosUser object privacy (encryption)As discussed in various occasions, user objects at the platform, despite not accessible anymore by admin/staff users via the web GUI, are still accessible on disk by administrators.
We must setup a scheme to get rid of this "bug" as t...As discussed in various occasions, user objects at the platform, despite not accessible anymore by admin/staff users via the web GUI, are still accessible on disk by administrators.
We must setup a scheme to get rid of this "bug" as the trust on the platform itself depends on how well we can keep our users' information.
Here is a suggestion to get the ball rolling:
1. Stored objects have declaration, code and documentation (files) encrypted using the user's password
2. At execution, the complete experiment tree is passed to the scheduler, unencrypted, which relies solely on it (and not any longer on information on disk) to execute the experiment.
Possible issues:
1. How to deal with shared objects (public objects should be left unencrypted, I guess, but privately shared ones are not that clear)? Maybe we'll need to duplicate objects at sharing time.
2. How to effectively implement this?
Side effects:
1. The scheduler would have no longer to verify the hash of submitted experiments.https://gitlab.idiap.ch/beat/beat.examples/-/issues/10`integers_mean_analyzer` is not up to date2017-10-04T21:58:16ZLaurent EL SHAFEY`integers_mean_analyzer` is not up to dateThis analyzer uses an outdated format when writing the object 'plot' of dataformat `plot/scatter/1`.
See for instance `integers_echo_analyzer` for the correct way of writing such a plot.This analyzer uses an outdated format when writing the object 'plot' of dataformat `plot/scatter/1`.
See for instance `integers_echo_analyzer` for the correct way of writing such a plot.BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/219Natural keys fixture dumping for BEAT objects is missing2015-07-20T07:07:18ZAndré AnjosNatural keys fixture dumping for BEAT objects is missingSince a long time we have the option to backup using natural primary and foreign keys, but this setting is not effective for our BEAT objects.
This triggered a bug while trying to do a restore on our new staging server: experiments r...Since a long time we have the option to backup using natural primary and foreign keys, but this setting is not effective for our BEAT objects.
This triggered a bug while trying to do a restore on our new staging server: experiments reference database sets with integer foreigns keys, but there is no certainty that database sets will be re-stored on the same order or with the same primary keys, given they are re-created at restore time.
To fix this issue for good, we'd need to implement `natural_key()` and `get_by_natural_key()` on the relevant classes throughout the project.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/7Do not open input/output pipe at each request2017-08-08T04:40:37ZLaurent EL SHAFEYDo not open input/output pipe at each requestAs discussed with @andre.anjos , this would be too inefficient.As discussed with @andre.anjos , this would be too inefficient.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/218Moving to Django 1.82015-07-21T13:59:13ZAndré AnjosMoving to Django 1.8Django 1.8 is already on its 4th release (1.8.3). Shall we begin thinking about moving?
Release notes: https://docs.djangoproject.com/en/1.8/releases/1.8/Django 1.8 is already on its 4th release (1.8.3). Shall we begin thinking about moving?
Release notes: https://docs.djangoproject.com/en/1.8/releases/1.8/BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/217Total number of slots per Queue not correctly displayed on Backend page2015-07-21T14:20:27ZAndré AnjosTotal number of slots per Queue not correctly displayed on Backend pageSomething to be fixed. The current display shows only `--` if you click on the `Queues` tab.Something to be fixed. The current display shows only `--` if you click on the `Queues` tab.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/6Move algorithm and library into this package2017-08-08T04:40:37ZLaurent EL SHAFEYMove algorithm and library into this packageLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/5Parameters handling requires a string to numpy-type conversion2017-08-08T04:40:37ZLaurent EL SHAFEYParameters handling requires a string to numpy-type conversionHandling the parameters of an algorithm requires the backend to be able to perform a string to numpy-type conversion.
This is currently performed by the method _convert_parameter_types() of the beat.core.algorithm.Algorithm class. Since...Handling the parameters of an algorithm requires the backend to be able to perform a string to numpy-type conversion.
This is currently performed by the method _convert_parameter_types() of the beat.core.algorithm.Algorithm class. Since the backend does not use this class, we need to move this function somewhere else to deal with experiment parameters.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/216Locked attestations with other user's components could be improved2015-11-20T11:32:41ZAndré AnjosLocked attestations with other user's components could be improvedWhen the user goes to unlock an attestation by clicking on the respective button at the attestation page, in the case none of the components belong to that user, the display could be improved (see image).
![image](https://gitlab.idiap...When the user goes to unlock an attestation by clicking on the respective button at the attestation page, in the case none of the components belong to that user, the display could be improved (see image).
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/2475fa071eb26ef4b83ea600d311924b/image.png)
From the other perspective, unlocking an attestation with components which belong to the user shows components which are already public (see the second image).
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/255ad59e963468252dbab1679f87f072/image.png)
I wonder if we should not have a more consistent display through these use cases. A suggestion:
1. Always display all components involved or leave the option to display them by following a link, for example (if space is an issue on this pop-up)
2. If a component is public already, indicate so
3. If an algorithm is public and/or open-source, indicate soFinal Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/215Possibility to delete locked attestations2015-11-20T11:31:10ZAndré AnjosPossibility to delete locked attestationsIt would be nice if the user could delete locked (still not public) attestations. IMO, there is no reason why a "private" attestation could not be deleted by the user requesting it.
Unlocked attestations should not be deletable as the...It would be nice if the user could delete locked (still not public) attestations. IMO, there is no reason why a "private" attestation could not be deleted by the user requesting it.
Unlocked attestations should not be deletable as they are already.Final Documentationhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/4Statistics split2017-08-08T04:40:37ZLaurent EL SHAFEYStatistics splitThe statistics are now generated by two different processes: the I/O daemon and the user process. However, everything is handled in one class, which means that statistics objects are often created but only half populated.
We may conside...The statistics are now generated by two different processes: the I/O daemon and the user process. However, everything is handled in one class, which means that statistics objects are often created but only half populated.
We may consider to split the class definition of statitics object to better reflect the underlying implementation.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/3Properly define IO daemon address2017-08-08T04:40:37ZLaurent EL SHAFEYProperly define IO daemon addressThe address of the IO daemon is currently hard-coded as localhost.
This should be properly defined and passed as an argument of the execute script.The address of the IO daemon is currently hard-coded as localhost.
This should be properly defined and passed as an argument of the execute script.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/2Move dataformat from beat.core2017-08-08T04:40:37ZLaurent EL SHAFEYMove dataformat from beat.coreIdeally, we don't want this package to depend on `beat.core`. But it requires dataformat.
One possible solution would be to move the dataformat from beat.core into this package, and to make beat.core depeonds on this package.Ideally, we don't want this package to depend on `beat.core`. But it requires dataformat.
One possible solution would be to move the dataformat from beat.core into this package, and to make beat.core depeonds on this package.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/1IO synchronization is managed twice2017-08-08T04:40:37ZLaurent EL SHAFEYIO synchronization is managed twiceThe I/O synchronization is currently manage twice: in `beat.io` and in `beat.backend.python`.
Since `beat.io` is common to any backend, it would be nice to only manage I/O synchronization in this package to keep the backends as simple...The I/O synchronization is currently manage twice: in `beat.io` and in `beat.backend.python`.
Since `beat.io` is common to any backend, it would be nice to only manage I/O synchronization in this package to keep the backends as simple as possible.Laurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/214Public databases require users to be authenticated to `access` them2015-07-13T11:39:59ZLaurent EL SHAFEYPublic databases require users to be authenticated to `access` themHere is an example request:
```
GET https://www.beat-eu.org/platform/api/v1/databases/atnt/1/?object_format=string&fields=declaration,code,description
```
If the user is not authenticated, the answer is:
```403 Forbidden, {"deta...Here is an example request:
```
GET https://www.beat-eu.org/platform/api/v1/databases/atnt/1/?object_format=string&fields=declaration,code,description
```
If the user is not authenticated, the answer is:
```403 Forbidden, {"detail":"Authentication credentials were not provided."}```BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/6Pulling a database fails with a token error2018-04-13T08:03:56ZLaurent EL SHAFEYPulling a database fails with a token errorIt's seems that a regular user can't pull databases anymore.
```
$ ./bin/beat --prefix=prefix db pull
retrieving `databases/atnt/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: ...It's seems that a regular user can't pull databases anymore.
```
$ ./bin/beat --prefix=prefix db pull
retrieving `databases/atnt/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/banca/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/casme2/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/cbsr_nir_vis_2/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/cpqd/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/mnist/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/mobio/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/replay/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/utfvp/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/voxforge/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/xm2vts/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
```
This also occurs when pulling an experiment, which will try to pull the database used.BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/5Database view is not working properly2018-04-13T08:03:56ZLaurent EL SHAFEYDatabase view is not working properlyWhen trying to view a dataset,
```
./bin/beat --prefix web_dynamic_data db view banca/1/Mc/dev_probes
```
I sometimes get this kind of errors:
```
Traceback (most recent call last):
File "./bin/beat", line 33, in <module>
...When trying to view a dataset,
```
./bin/beat --prefix web_dynamic_data db view banca/1/Mc/dev_probes
```
I sometimes get this kind of errors:
```
Traceback (most recent call last):
File "./bin/beat", line 33, in <module>
sys.exit(beat.cmdline.scripts.beat.main())
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/scripts/beat.py", line 160, in main
return module.process(args)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 402, in process
return view_output(args['config'], args['<set_name>'])
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 355, in view_output
json_data[name] = common.stringify(value)
TypeError: 'str' object does not support item assignment
```
BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/213Cannot delete bus lines on toolchain editor (Safari on OS X)2015-08-14T15:47:08ZAndré AnjosCannot delete bus lines on toolchain editor (Safari on OS X)Apparently, this is not working as supposed. Could you please confirm?Apparently, this is not working as supposed. Could you please confirm?BTAS TutorialPhilip ABBETPhilip ABBET