beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-06-17T06:22:00Zhttps://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/111Cancelling an experiment may prevent execution info area to be displayed pro...2015-05-07T06:46:13ZLaurent EL SHAFEYCancelling an experiment may prevent execution info area to be displayed properlyAfter cancelling an experiment (via cancel all), we noticed that the display of the execution info on the experiment page may be stuck with the animation.
At the JS level, there is the following error:
```javascript
Uncaught TypeE...After cancelling an experiment (via cancel all), we noticed that the display of the execution info on the experiment page may be stuck with the animation.
At the JS level, there is the following error:
```javascript
Uncaught TypeError: Cannot read property 'appendChild' of undefinedpanels.js:3751 beat.experiments.panels.Results._setuppanels.js:3813
beat.experiments.panels.Results.update(index):166
(anonymous function)jquery-1.11.1.min.js:2 m.Callbacks.jjquery-1.11.1.min.js:2 m.Callbacks.k.fireWithjquery-1.11.1.min.js:4 xjquery-1.11.1.min.js:4 m.ajaxTransport.send.b
```
Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/112Global variables are currently ignored by experiment execution2015-04-23T09:58:24ZLaurent EL SHAFEYGlobal variables are currently ignored by experiment executionIt seems that global variables are currently ignored by experiment execution, while they are displayed properly on the experiment page.
I don't know if the problem is at the beat.web or beat.core level.
To reproduce the problem:
1. ...It seems that global variables are currently ignored by experiment execution, while they are displayed properly on the experiment page.
I don't know if the problem is at the beat.web or beat.core level.
To reproduce the problem:
1. Create a simple Eigenface experiment and run it.
2. Fork it and update the 'global' number of pca components parameter.
3. After pressing go on the forked experiment, it will complete very fast and leads to the exact same results.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/113Algorithm ptome/fingervein-miura_scoring/2 causes webpage crashes2015-05-04T13:12:40ZLaurent EL SHAFEYAlgorithm ptome/fingervein-miura_scoring/2 causes webpage crashesThe algorithm ptome/fingervein-miura_scoring/2 causes webpage crashes.
After selecting it in an experiment, the webpage get stuck on the algorithm selection and an error "'Uncaught TypeError: Cannot read property 'length' of undefined...The algorithm ptome/fingervein-miura_scoring/2 causes webpage crashes.
After selecting it in an experiment, the webpage get stuck on the algorithm selection and an error "'Uncaught TypeError: Cannot read property 'length' of undefined' " is reported in the JS side.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/114Antispoofing toolchains are broken2015-04-23T09:06:06ZLaurent EL SHAFEYAntispoofing toolchains are brokenThe antispoofing toolchains (ivana7c/simple-antispoofing-updated/1 and smarcel/face-antispoofing/1) on the platform are currently broken.
After configuring the experiment, pressing go leads to the following error:
in beat/web/experim...The antispoofing toolchains (ivana7c/simple-antispoofing-updated/1 and smarcel/face-antispoofing/1) on the platform are currently broken.
After configuring the experiment, pressing go leads to the following error:
in beat/web/experiments/models.py (line 142, create_experiment experiment.save())
beat/web/experiments/models.py (line 297, raise SyntaxError() "The experiment isn't valid due to the following errors: toolchain data is not valid, because: /representation/connections/classifier_dev.scores/analyzer.scores_dev_pos not listed on /connections; /representation/connections/classifier_test.scores/analyzer.scores_test_pos not listed on /connections; /representation/connections/dev_probes.class/analyzer.scores_dev_neg not listed on /connections;")
Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/115Creation APIs doesn't check the validity of the specified contribution name2015-05-04T13:09:27ZPhilip ABBETCreation APIs doesn't check the validity of the specified contribution nameThe creation API for toolchains, algorithms and data formats allows an empty string to be passed as the name of the new contribution.
Only the fact that the name is a string is checked.The creation API for toolchains, algorithms and data formats allows an empty string to be passed as the name of the new contribution.
Only the fact that the name is a string is checked.https://gitlab.idiap.ch/beat/beat.web/-/issues/116Cannot edit newly created objects2015-05-05T17:49:59ZLaurent EL SHAFEYCannot edit newly created objectsNew objects created through the web interface (this is the case, at least, for algorithms, libraries and dataformats), cannot be modified anymore. This is inconsistent w.r.t. the behavior of the "Delete" button, that shows up unlocked (a...New objects created through the web interface (this is the case, at least, for algorithms, libraries and dataformats), cannot be modified anymore. This is inconsistent w.r.t. the behavior of the "Delete" button, that shows up unlocked (as it should) for newly created objects, meaning we can delete them.
If we can delete an object, we should have the ability to modify it completely (for example, edit its code or declaration).Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/117Cannot specify database/algorithm/analyzer version in search2015-05-05T17:46:27ZLaurent EL SHAFEYCannot specify database/algorithm/analyzer version in searchActually, it is not possible to specify version numbers in a search.
This is particularly annoying for analyzers, since we can only compare experiments generated with the same analyzer and version.
Actually, it is not possible to specify version numbers in a search.
This is particularly annoying for analyzers, since we can only compare experiments generated with the same analyzer and version.
Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/119Recursive behavior of can_be_deleted()2015-05-03T20:56:02ZAndré AnjosRecursive behavior of can_be_deleted()I think that the behavior of `can_be_deleted()`, at least on Libraries is not 100% correct. An object can be deleted if it is not used by another object. So, I think the straightfoward way to check for it would be to just verify if any a...I think that the behavior of `can_be_deleted()`, at least on Libraries is not 100% correct. An object can be deleted if it is not used by another object. So, I think the straightfoward way to check for it would be to just verify if any algorithm is using that library. If that is the case, it cannot be deleted. Else, if nobody references this library, then it can be deleted.
Could you please confirm?Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/120Saving an invalid algorithms at admin micro-site causes a 500 error2015-05-05T06:54:12ZAndré AnjosSaving an invalid algorithms at admin micro-site causes a 500 errorThis used to work. Now, if the algorithm is invalid (for example, uses an invalid data format on its declaration), the website generates a 500 error.
Desired behavior: It should gracefully indicate that the declaration is invalid, and...This used to work. Now, if the algorithm is invalid (for example, uses an invalid data format on its declaration), the website generates a 500 error.
Desired behavior: It should gracefully indicate that the declaration is invalid, and the problem.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/121Cannot update dataformat JSON from admin website2015-05-05T17:45:55ZAndré AnjosCannot update dataformat JSON from admin websiteThis also used to work. It is now broken.
For example, try to remove the whole contents of any data format and observe it is not properly saved.This also used to work. It is now broken.
For example, try to remove the whole contents of any data format and observe it is not properly saved.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/123Adding a short description of an algorithm with more than 100 characters gene...2015-05-06T17:16:59ZLaurent EL SHAFEYAdding a short description of an algorithm with more than 100 characters generates a 500 errorWhen adding a short description of an algorithm with more than 100 characters, it currently generates a 500 internal error.
The expected behavior would be to warn the user that the description is too long.When adding a short description of an algorithm with more than 100 characters, it currently generates a 500 internal error.
The expected behavior would be to warn the user that the description is too long.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/124Cannot update description of algorithm parameters2015-05-07T06:43:34ZLaurent EL SHAFEYCannot update description of algorithm parametersIt is currently not possible to update the description of algorithm parameters through the web interface.It is currently not possible to update the description of algorithm parameters through the web interface.Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/125Cannot update toolchain description2015-05-05T12:11:47ZLaurent EL SHAFEYCannot update toolchain descriptionIt is currently not possible to update a toolchain (short/long) description.
When clicking on the save button, nothing happens and the user is stuck with the edition form.
It is currently not possible to update a toolchain (short/long) description.
When clicking on the save button, nothing happens and the user is stuck with the edition form.
Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/126Special (accented) characters in toolchain/algorithm description causes error2015-05-05T11:03:36ZLaurent EL SHAFEYSpecial (accented) characters in toolchain/algorithm description causes errorI've noticed the following problem with special (accented) characters. When they are used in a toolchain/algorithm description, installing these contributions will just work fine. However, when I try to load the toolchain/algorithm page,...I've noticed the following problem with special (accented) characters. When they are used in a toolchain/algorithm description, installing these contributions will just work fine. However, when I try to load the toolchain/algorithm page, the page cannot be loaded properly, and the following error occured:
```
Subject: [BEAT] ERROR (EXTERNAL IP): Internal Server Error:
/api/algorithms/user/
From: no-reply@beat-project.eu
To: E-MAIL ADDRESS
Date: Tue, 05 May 2015 09:33:03 -0000
Message-ID: <20150505093303.27891.45893@futurix08.idiap.ch>
Internal Server Error: /api/algorithms/user/
Traceback (most recent call last):
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 137, in get_response
response = response.render()
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/site-packages/django/template/response.py", line 103, in render
self.content = self.rendered_content
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/site-packages/rest_framework/response.py", line 59, in rendered_content
ret = renderer.render(self.data, media_type, context)
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/site-packages/rest_framework/renderers.py", line 99, in render
separators=separators
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/json/__init__.py", line 250, in dumps
sort_keys=sort_keys, **kw).encode(obj)
File "/idiap/project/beat/beat.env.develop/usr/lib/python2.7/json/encoder.py", line 210, in encode
return ''.join(chunks)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 546: ordinal not in range(128)
```Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/127Algorithm description cannot be edited properly2015-05-05T11:02:38ZLaurent EL SHAFEYAlgorithm description cannot be edited properlyLet's consider the algorithm [tutorial/cropping_rgb/3/](https://www.beat-eu.org/platform/algorithms/tutorial/cropping_rgb/3/).
This algorithm has both a short and long descriptions (as shown by clicking on `more`).
However, if we pre...Let's consider the algorithm [tutorial/cropping_rgb/3/](https://www.beat-eu.org/platform/algorithms/tutorial/cropping_rgb/3/).
This algorithm has both a short and long descriptions (as shown by clicking on `more`).
However, if we press on edit, the long description field will be filled with a filename `http://www.beat-eu.org/platform/api/algorithms/tutorial/cropping_rgb/3/fe/30/tutorial/cropping_rgb/3.rst` instead of the real content of the long description.Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/129[search] Cannot search for "tutorial/postperf/1" uniquely2015-05-05T19:04:58ZAndré Anjos[search] Cannot search for "tutorial/postperf/1" uniquelyIf the user types a full string for an object, it should be an exact match, otherwise, how could we filter for it?If the user types a full string for an object, it should be an exact match, otherwise, how could we filter for it?Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/133Database label are incorrect in experiment page2015-05-06T14:27:22ZAndré AnjosDatabase label are incorrect in experiment pageThe labels of the datasets used in the experiment page (user micro-site) are not consistent with what is actually used on the related experiment. For example, check your user micro-site (on the production platform), for the public experi...The labels of the datasets used in the experiment page (user micro-site) are not consistent with what is actually used on the related experiment. For example, check your user micro-site (on the production platform), for the public experiment: /tutorial/tutorial/full_lbphs/1/atnt-lbphs/, the displayed dataset on the user micro-site is "banca.Md", where this experiment clearly uses "atnt.idiap". If you click on it, the experiment display page shows the right configuration.
This must be an issue with the javascript parsing on the experiment list page.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/134Search page alerts with a 404 for a given experiment (when plotting)2015-05-05T17:43:45ZAndré AnjosSearch page alerts with a 404 for a given experiment (when plotting)The search results page is getting a 404 error when looking up data for an experiment in which the author name and the toolchain author names match.
This is because of this "simplification" we used to have, in which an experiment full...The search results page is getting a 404 error when looking up data for an experiment in which the author name and the toolchain author names match.
This is because of this "simplification" we used to have, in which an experiment full name could be shortened if the author name of the experiment matched the author name of the toolchain. So, this used to work:
```text
<url>/experiments/<user>/<toolchain>/<number>/<label>
```
Basically, that meant our code had to have this branching all the time: does it contain 4 or 5 bits? To avoid this and simplify the code everywhere, since a few commits, the 4-tiered version was deprecated. Experiments should be referred by their full name (i.e., the 5-tiered thingy):
```text
<url>/experiments/<experiment-user>/<toolchain-user>/<toolchain-name>/<toolchain-version>/<label>
```
Somewhere in the search, this simplification is still being done and, therefore the 404.
@flavio.tarsetti: Could you please remove all instances of this?Tutorial for the FG2015 ConferenceFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/135Diff view not working (at least for) Algorithms2015-05-05T19:15:09ZAndré AnjosDiff view not working (at least for) AlgorithmsTo reproduce, click on the [compare] button in any algorithm with at least two versions.To reproduce, click on the [compare] button in any algorithm with at least two versions.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAIST