beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-05-22T15:16:05Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/157Team creation and editor could see a face lift2015-05-22T15:16:05ZAndré AnjosTeam creation and editor could see a face liftApparently we're using Django's form widgets to get that going, but it certainly does not look as nice as the other editors we have.
It would be good to see it face-lifted after the tutorial.Apparently we're using Django's form widgets to get that going, but it certainly does not look as nice as the other editors we have.
It would be good to see it face-lifted after the tutorial.API Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/154Edit button in non-editable algorithm2015-05-11T14:53:00ZManuel GüntherEdit button in non-editable algorithmI have an algorithm that belongs to a failed experiment:
https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/
The experiment was not deleted yet, and I should not be able to edit the algorithm.
However, there is an ``Edit`` b...I have an algorithm that belongs to a failed experiment:
https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/
The experiment was not deleted yet, and I should not be able to edit the algorithm.
However, there is an ``Edit`` button, which I can click and which leads me to the algorithm editing page.
Nevertheless, when I try to ``Save`` the algorithm, I get the error message:
```
Algorithm not created, please fix the errors below
{"detail":"The algorithm isn't modifiable anymore (either shared with someone else, or needed by an attestation)"}
```
So, it seems that the algorithm knows that it is not modifiable, but still the ``Edit`` button exists.API DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/153Long delay after clicking the 'Go' button2015-05-29T14:43:59ZManuel GüntherLong delay after clicking the 'Go' buttonWhen starting an experiment, sometimes it takes quite some time until something happens (e.g., the execution of the experiment is displayed).
Particularly, when the experiment status is "Scheduled", the experiment submission webpage doe...When starting an experiment, sometimes it takes quite some time until something happens (e.g., the execution of the experiment is displayed).
Particularly, when the experiment status is "Scheduled", the experiment submission webpage doesn't change, until the experiment actually started to execute.
My problem is that there is absolutely no response, whether the submission was successful or not.
In my point of view, there are three options to display the successive submission:
1. Show the experiment execution page immediately after successful submission
2. Change the "Go" button into something else, for example a "Stop" button
3. Open a message box, saying: "Experiment was scheduled, waiting for it to start" with two buttons "Cancel experiment" and "Show experiment", which closes automatically after the experiment was startedAPI DocumentationLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/145Unify toolchain creation page so all happens in a single form2015-05-13T15:28:25ZManuel GüntherUnify toolchain creation page so all happens in a single formWhen I try to create a new version of a toolchain, such as:
https://www.beat-eu.org/platform/toolchains/tutorial/full_lbphs/2
I can only see and edit the description of the toolchain, but the toolchain itself is not shown, and I cannot...When I try to create a new version of a toolchain, such as:
https://www.beat-eu.org/platform/toolchains/tutorial/full_lbphs/2
I can only see and edit the description of the toolchain, but the toolchain itself is not shown, and I cannot edit it.
The same applies, when a new toolchain is created.API Documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/143In an experiment setup: database changes when removing/changing algorithms2015-05-12T17:14:43ZManuel GüntherIn an experiment setup: database changes when removing/changing algorithmsThe is an issue with the experiment editor. After forking an old experiment, and changing an algorithm (for example one for scoring), the database entry is modified, switching to a completely unrelated database, or even becomes empty.
I...The is an issue with the experiment editor. After forking an old experiment, and changing an algorithm (for example one for scoring), the database entry is modified, switching to a completely unrelated database, or even becomes empty.
It seems that the same applies, when a new experiment is created.API DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/138Global algorithm parameters are not removed properly2015-05-12T17:12:18ZLaurent EL SHAFEYGlobal algorithm parameters are not removed properlyIf:
1. I fork an experiment that uses a given algorithm (e.g. tutorial/pca/1),
2. Replace this algorithm (e.g. by tutorial/pca/2)
(3. This algorithm is not used by any other block of the experiment)
Then:
I am unable to run this e...If:
1. I fork an experiment that uses a given algorithm (e.g. tutorial/pca/1),
2. Replace this algorithm (e.g. by tutorial/pca/2)
(3. This algorithm is not used by any other block of the experiment)
Then:
I am unable to run this experiment, and I get the following alert message:
(...) The experiment isn't valid, since (...) globals: found parameter section for algorithm `tutorial/pca/1' which is not used anywhere in the experiment.
API DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/98Free text area for the experiments and search2015-05-19T11:55:31ZTiago de Freitas PereiraFree text area for the experiments and searchWould be nice in the experiment session to have free text space.
Sometimes you want to highlight something that is beyond the results itself.
Consider to add a free text space in the experiment session.
I think the same for the se...Would be nice in the experiment session to have free text space.
Sometimes you want to highlight something that is beyond the results itself.
Consider to add a free text space in the experiment session.
I think the same for the search area.
When you save a search, would be nice to say something about it (this will be the bridge between an eventual publication and the source code).
API DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/90Harmonisation of experiments web API2015-05-13T15:25:18ZAndré AnjosHarmonisation of experiments web APIWe presently have our web API for experiments in a bit of an inconsistent state:
1. Some of the calls go through <base>/experiments
2. Some others go through <base>/experiments/configuration
This is not the case for other platform...We presently have our web API for experiments in a bit of an inconsistent state:
1. Some of the calls go through <base>/experiments
2. Some others go through <base>/experiments/configuration
This is not the case for other platform objects (such as data formats, toolchains, or else). This creates a slight complication for API users.
@philip.abbet: is this just legacy behaviour or is there a good reason for keeping it this way?API DocumentationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/198New text on the front page ?2015-06-16T13:04:16ZSébastien MARCELNew text on the front page ?To make it more general I would suggest to replace the text
"The BEAT (Biometrics Evaluation and Testing) platform provides easy online access to experimentation and testing for Biometrics. You define what data and modules you would lik...To make it more general I would suggest to replace the text
"The BEAT (Biometrics Evaluation and Testing) platform provides easy online access to experimentation and testing for Biometrics. You define what data and modules you would like to use, we make sure the system runs and provides you with a result. Data from different experiments can be easily compared and searched."
by
"The BEAT platform provides easy online access to experimentation and testing in computational science. You define what data and modules you would like to use, we make sure the system runs and provides you with a result. Data from different experiments can be easily compared and searched."
What do you think ?
BEAT TourPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/197Cannot see system dataformats anymore2015-06-03T06:25:31ZAndré AnjosCannot see system dataformats anymoreHow to reproduce it (just visit):
https://www.beat-eu.org/platform/dataformats/system/uint64/1/
Error:
```text
Internal Server Error: /platform/api/v1/dataformats/system/uint64/1/
Traceback (most recent call last):
File "/r...How to reproduce it (just visit):
https://www.beat-eu.org/platform/dataformats/system/uint64/1/
Error:
```text
Internal Server Error: /platform/api/v1/dataformats/system/uint64/1/
Traceback (most recent call last):
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 111, in get_response
response = wrapped_callback(request, *callback_args, **callback_kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/views/decorators/csrf.py", line 57, in wrapped_view
return view_func(*args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/views/generic/base.py", line 69, in view
return self.dispatch(request, *args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/views.py", line 452, in dispatch
response = self.handle_exception(exc)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/views.py", line 449, in dispatch
response = handler(request, *args, **kwargs)
File "/remote/sw/beat.web/src/beat.web/beat/web/common/api.py", line 248, in get
return Response(serializer.data)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 466, in data
ret = super(Serializer, self).data
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 213, in data
self._data = self.to_representation(self.instance)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 435, in to_representation
ret[field.field_name] = field.to_representation(attribute)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/fields.py", line 1323, in to_representation
return method(value)
File "/remote/sw/beat.web/src/beat.web/beat/web/dataformats/serializers.py", line 107, in get_referencing_databases
return serializer.data
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 618, in data
ret = super(ListSerializer, self).data
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 213, in data
self._data = self.to_representation(self.instance)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 568, in to_representation
self.child.to_representation(item) for item in iterable
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/serializers.py", line 435, in to_representation
ret[field.field_name] = field.to_representation(attribute)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/rest_framework/fields.py", line 1322, in to_representation
method = getattr(self.parent, self.method_name)
AttributeError: 'ReferencingDatabaseSerializer' object has no attribute 'get_description'
```BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/195Experiment forking does not work anymore2015-06-02T13:49:13ZLaurent EL SHAFEYExperiment forking does not work anymoreWhen forking an experiment, we end up on the experiment setup page with the correct toolchain. However, algorithm (inclusive parameters) and datasets are both missing.When forking an experiment, we end up on the experiment setup page with the correct toolchain. However, algorithm (inclusive parameters) and datasets are both missing.BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/194Experiment API does not return anything when field 'sharing' is provided2015-06-02T13:49:13ZLaurent EL SHAFEYExperiment API does not return anything when field 'sharing' is providedWhen performing a query such as:
GET api/v1/experiments/<experiment-fullname>/?fields=sharing
it currently does not return anything.
Since such a construction is used to display experimental results, this makes impossible to display...When performing a query such as:
GET api/v1/experiments/<experiment-fullname>/?fields=sharing
it currently does not return anything.
Since such a construction is used to display experimental results, this makes impossible to display the results of a private experiment. Looking at the code, this is related to the serializers (-> @samuel.gaist ).BEAT TourSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/193Use Swagger for ReSTful API2015-06-01T07:38:52ZAndré AnjosUse Swagger for ReSTful APIWith the BEAT deliverables out of the way, it would be nice to think about a longer term documentation strategy for our web APIs. Now everything (please correct me if I'm wrong) uses Django's rest framework, it would be good to go for Sw...With the BEAT deliverables out of the way, it would be nice to think about a longer term documentation strategy for our web APIs. Now everything (please correct me if I'm wrong) uses Django's rest framework, it would be good to go for Swagger. It is, at least, the recommendation from that library: http://www.django-rest-framework.org/topics/documenting-your-api/BEAT Tourhttps://gitlab.idiap.ch/beat/beat.core/-/issues/35Move command-line client to another package2017-08-06T11:17:03ZAndré AnjosMove command-line client to another packageAs discussed, we should move the command-line client to another package, since it depends on the `beat.web` API. This creates some sort of reverse dependence which we should get rid of.As discussed, we should move the command-line client to another package, since it depends on the `beat.web` API. This creates some sort of reverse dependence which we should get rid of.BEAT TourAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/170Sort protocols on a database page2015-05-18T07:35:49ZLaurent EL SHAFEYSort protocols on a database pageCurrently, the protocols are listed in a random order on a database page. We should likely sort them in alphabetical order.Currently, the protocols are listed in a random order on a database page. We should likely sort them in alphabetical order.BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/166Dataformat validation on beat.web is incomplete2015-05-12T16:18:35ZLaurent EL SHAFEYDataformat validation on beat.web is incompleteWhen creating the following dataformat on beat.web,
```
{
"bla": "uint32",
"blo": "uint24"
}
```
a 500 internal error is generated instead of a proper error message.When creating the following dataformat on beat.web,
```
{
"bla": "uint32",
"blo": "uint24"
}
```
a 500 internal error is generated instead of a proper error message.BEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/165`dataset-name` in search causes 500 internal error2015-05-12T16:11:21ZLaurent EL SHAFEY`dataset-name` in search causes 500 internal errorWhen selecting the field `dataset-name` in a search, pressing the `apply` button will cause a 500 internal error.When selecting the field `dataset-name` in a search, pressing the `apply` button will cause a 500 internal error.BEAT TourLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.core/-/issues/32Dash '-' as a valid (or invalid) character for element names (dataformats, al...2017-08-06T11:17:03ZLaurent EL SHAFEYDash '-' as a valid (or invalid) character for element names (dataformats, algorithms, etc.)?I've noticed an inconsistency wrt. the usage of the dash '-' character for element names.
There is currently a bunch of elements (e.g. algorithm 'ptome/fingervein-miura_scoring/1/') defined on the platform, which contains the '-' char...I've noticed an inconsistency wrt. the usage of the dash '-' character for element names.
There is currently a bunch of elements (e.g. algorithm 'ptome/fingervein-miura_scoring/1/') defined on the platform, which contains the '-' character.
In contrast, the '-' character is not 'always' part of the valid character at the JSON validation schema level (see beat/core/schema/experiment.json line 48).
The list of valid characters needs to be properly defined, and the characters accepted by the beat.web interface need to match the ones of the JSON validation schema.BEAT TourLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/110SQLite search feature incomplete2015-06-17T06:22:00ZSamuel GAISTSQLite search feature incompleteThe search feature currently runs properly on MySQL and PostgreSQL however the SQLite implementation returns always the same row of values. This only affects the results.
The code related to that can be found in beat/web/navigation/ut...The search feature currently runs properly on MySQL and PostgreSQL however the SQLite implementation returns always the same row of values. This only affects the results.
The code related to that can be found in beat/web/navigation/utils.cpp:992BEAT TourSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/97Rename an experiment2015-06-17T15:02:42ZTiago de Freitas PereiraRename an experimentIt is not possible to rename an experiment.It is not possible to rename an experiment.BEAT Tour