beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2016-04-04T14:37:02Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/276[search] Plot template not showing up on search2016-04-04T14:37:02ZFlavio TARSETTI[search] Plot template not showing up on searchMissing the new feature "plot template selection" on searchMissing the new feature "plot template selection" on searchFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/11Create PipeSource/Sink instead of changing Output class2017-08-08T04:40:37ZAndré AnjosCreate PipeSource/Sink instead of changing Output classWe need to revert the design currently available on this package so that it respects the old beat.core design. Instead of overwriting the Input/Output classes, we need to create both a PipeSource and a PipeSink classes that can be used t...We need to revert the design currently available on this package so that it respects the old beat.core design. Instead of overwriting the Input/Output classes, we need to create both a PipeSource and a PipeSink classes that can be used to input and output data for the Input/Output classes respectively.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/10Improve test-ability of this package2017-08-08T04:40:37ZAndré AnjosImprove test-ability of this packageAs of today, it is not very easy to test the user process w/o an I/O daemon. We'd have to figure out a way to build unit tests around this package.As of today, it is not very easy to test the user process w/o an I/O daemon. We'd have to figure out a way to build unit tests around this package.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/236Plots from locked attestation don't appear2015-07-30T06:53:58ZSébastien MARCELPlots from locked attestation don't appearWhen not logged-in the plots of this locked attestation https://www.beat-eu.org/platform/attestations/809977024/
don't appear. My web-browser tries to load them ...
When not logged-in the plots of this locked attestation https://www.beat-eu.org/platform/attestations/809977024/
don't appear. My web-browser tries to load them ...
André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/37Some toolchains show execution errors despite looking similar to existing ones2017-10-16T09:01:26ZAndré AnjosSome toolchains show execution errors despite looking similar to existing onesIn particular, this happened today with a toolchain forked by @sebastien.marcel at the platform. The same happened with another colleague.
If the user runs on the original fork, everything runs fine. If the user tries to use his versi...In particular, this happened today with a toolchain forked by @sebastien.marcel at the platform. The same happened with another colleague.
If the user runs on the original fork, everything runs fine. If the user tries to use his version, the error shows up.
@sebastien.marcel: Could you please share with me user `anjos`, the said toolchain? I'll try to have a look on its contents and figure out the problem.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/9Remove prefix access and pass everything by value/json2017-08-08T04:40:37ZLaurent EL SHAFEYRemove prefix access and pass everything by value/jsonThe user process still has access to the prefix to fetch dataformats/algorithms/etc. Ideally, we need to get rid of this and to pass everything by value/json.The user process still has access to the prefix to fetch dataformats/algorithms/etc. Ideally, we need to get rid of this and to pass everything by value/json.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/8Split beat.core and beat.backend.python2017-08-08T04:40:37ZLaurent EL SHAFEYSplit beat.core and beat.backend.pythonFollowing a discussion with @andre.anjos , few beat.core functionalities need to be in beat.backend.python.
To achieve this, we need to:
1. Move all the relevant code from beat.core to beat.backend.python
2. Make beat.core depends o...Following a discussion with @andre.anjos , few beat.core functionalities need to be in beat.backend.python.
To achieve this, we need to:
1. Move all the relevant code from beat.core to beat.backend.python
2. Make beat.core depends on beat.backend.python
3. Make all packages use features from beat.backend.python (when they were moved from beat.core to beat.backend.python)André 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.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.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/208Copy and paste blocks in the toolchain designer2015-07-13T07:10:10ZTiago de Freitas PereiraCopy and paste blocks in the toolchain designerHi
I'm designing a toolchain with 56 blocks, would be very useful to have a copy and paste tool in the toolchain designer.
Will save a lot of time.
Hi
I'm designing a toolchain with 56 blocks, would be very useful to have a copy and paste tool in the toolchain designer.
Will save a lot of time.
https://gitlab.idiap.ch/beat/beat.web/-/issues/203Experiment page is not displayed when a floating point result value has a spe...2015-06-26T08:45:22ZTiago de Freitas PereiraExperiment page is not displayed when a floating point result value has a special value such as `+inf`I ran the following experiments on the CPqD database:
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/full_isv/2/btas2015_face_cpqd-smartphone-female/
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/...I ran the following experiments on the CPqD database:
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/full_isv/2/btas2015_face_cpqd-smartphone-female/
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/full_isv/2/btas2015_face_cpqd-smartphone-male/
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/full_isv/2/btas2015_periocular_cpqd-smartphone-male_take2/
https://www.beat-eu.org/platform/experiments/tpereira/tpereira/full_isv/2/btas2015_periocular_cpqd-smartphone-female_take2/
The experiment is done, but when I click them to see the results I get the following message box:
"Syntax error: Unexpected token l"
Usually, I use google Chrome.
Testing in a different browser (firefox), I get the following message box:
"SyntaxError: JSON.parse: unexpected non-digit at line 1 column 6684 of the JSON data"
This behavior only happens with experiments with the CPqD database.
Thanks
Tiago
https://gitlab.idiap.ch/beat/beat.web/-/issues/196Django-rest-swagger uses http scheme instead of https2015-07-21T10:31:29ZLaurent EL SHAFEYDjango-rest-swagger uses http scheme instead of httpsOn the production platform, the API documentation is available [here](https://www.beat-eu.org/platform/docs/). However, there is an issue with django-rest-swagger.
When clicking on the above mentioned documentation link, the address h...On the production platform, the API documentation is available [here](https://www.beat-eu.org/platform/docs/). However, there is an issue with django-rest-swagger.
When clicking on the above mentioned documentation link, the address http://www.beat-eu.org/platform/docs/api-docs/ is shown instead of https://www.beat-eu.org/platform/docs/api-docs/, and the API documentation is not shown. If we manually update this address (to use https), then the API documentation shows up.
The suggestion of [this issue](https://github.com/marcgibbons/django-rest-swagger/issues/220) is already applied in the Django's settings.py of the production server and this does not help.
Debugging at the javascript level, swagger submits a request with ``scheme`` set to ``http`` instead of ``https``. Unfortunately, I've not found any way to force the use of `https` in django-rest-swagger.https://gitlab.idiap.ch/beat/beat.web/-/issues/187team creation is not api v1 compatible2015-05-27T15:23:25ZLaurent EL SHAFEYteam creation is not api v1 compatibleWhile defining the API v1, it seems that the team creation has been forgotten.
If I try to create a team, I end up with such an error:
```
Page not found (404)
Request Method:
POST
Request URL:
http://127.0.0.1:8000/api/teams...While defining the API v1, it seems that the team creation has been forgotten.
If I try to create a team, I end up with such an error:
```
Page not found (404)
Request Method:
POST
Request URL:
http://127.0.0.1:8000/api/teams/user/
Using the URLconf defined in beat.web.urls,
Django tried these URL patterns, in this order:
^$
[name='index']
^login/$
[name='login']
^user/(?P<username>\w+)/$
[name='userpage']
^settings/$
[name='user-settings']
^search/(?P<username>\w+)/(?P<queryname>[\w\-]+)/$
[name='search']
^search/$
[name='search']
^tos/$
[name='terms-of-service']
^disclaimer/$
[name='legal-disclaimer']
^contact/$
[name='contact']
^logout/$
[name='logout']
^signup/$
[name='registration']
^signup/complete/$
[name='registration-complete']
^signup/activate/(?P<activation_key>\w+)/$
[name='registration-activation']
^preregister/$
[name='pre-registration']
^preregistration/complete/$
[name='pre-registration-complete']
^algorithms/
^libraries/
^attestations/
^backend/
^dataformats/
^databases/
^experiments/
^statistics/
^toolchains/
^teams/
^plotters/
^admin/
^api/v1/teams/
^api/v1/algorithms/
^api/v1/attestations/
^api/v1/backend/
^api/v1/databases/
^api/v1/dataformats/
^api/v1/experiments/
^api/v1/libraries/
^api/v1/statistics/
^api/v1/toolchains/
^api/v1/plotters/
^api/v1/
^static\/(?P<path>.*)$
The current URL, api/teams/user/, didn't match any of these.
```
I guess that fixing the URL in the form should be enough.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/182Reports: Add a reports tab on the user page2015-06-02T09:58:17ZPhilip ABBETReports: Add a reports tab on the user pageDepends on #181
Similar to the *Attestations* one, with a *New* buttonDepends on #181
Similar to the *Attestations* one, with a *New* buttonFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/181Reports: Model creation + Web API2015-06-02T09:58:11ZPhilip ABBETReports: Model creation + Web API**About the model:**
- A set of hand-picked experiments
- An author
- A name
- A documentation
- A unique number (see attestations)
- Must lock (not ```modifiable()``` nor ```deletable()```) experiments assigned to it
- Three po...**About the model:**
- A set of hand-picked experiments
- An author
- A name
- A documentation
- A unique number (see attestations)
- Must lock (not ```modifiable()``` nor ```deletable()```) experiments assigned to it
- Three possible states: edition, locked, published
- The content of the report is defined using a JSON array (stored in the database),
where each entry might represent either a table (which columns + how to sort the
experiments + an optional caption) or a figure (whatever is needed to plot it +
an optional caption)
**Web API:**
* [x] creation of a report
* [x] deletion of a report
* [x] retrieval of a report
* [x] retrieval of a list of reports
* [x] locking of a report
* [x] publication of a locked report
* [x] addition of experiments in a report
* [x] removal of experiments from a report
* [x] update of the content of a report
Each endpoint must be tested.Flavio TARSETTIFlavio TARSETTI