beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-05-07T07:22:55Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/151Can request attestation for experiment that I don't own2015-05-07T07:22:55ZAndré AnjosCan request attestation for experiment that I don't ownThe button to request an attestation still shows up even if the experiment is not yours.
Reproduce:
Following this link (while you're not user "siebenkopf"): https://www.beat-eu.org/platform/experiments/siebenkopf/siebenkopf/FaceRe...The button to request an attestation still shows up even if the experiment is not yours.
Reproduce:
Following this link (while you're not user "siebenkopf"): https://www.beat-eu.org/platform/experiments/siebenkopf/siebenkopf/FaceRec-WithOut-Training/2/Banca_P-PhaseDiff/Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/150Doc strings on search save are required, but not displayed2015-05-07T07:40:08ZAndré AnjosDoc strings on search save are required, but not displayedWe have an issue with documentation strings on searches. Here is what happens:
1. The user must provide a short description **and** a long description while saving
2. At the user micro-site, these are not displayed
This is what sh...We have an issue with documentation strings on searches. Here is what happens:
1. The user must provide a short description **and** a long description while saving
2. At the user micro-site, these are not displayed
This is what should happen:
1. The user *may* provide a short description and/or a long description.
2. The short description should be displayed at the user micro-site like for other objects.Tutorial for the FG2015 ConferenceFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/148Cannot return plot output in an analyzer2015-05-06T15:07:33ZManuel GüntherCannot return plot output in an analyzerWhen creating a new version of an analyzer as:
https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/14/
I cannot select the output used for plotting, but only ``float32``, ``int32``, ``bool`` and ``string`` can be selected.When creating a new version of an analyzer as:
https://www.beat-eu.org/platform/algorithms/siebenkopf/ROC/14/
I cannot select the output used for plotting, but only ``float32``, ``int32``, ``bool`` and ``string`` can be selected.Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/147When documenting data formats, the location of the .rst file is shown2015-05-06T15:14:33ZManuel GüntherWhen documenting data formats, the location of the .rst file is shownI recently added documentation for a data format:
https://www.beat-eu.org/platform/dataformats/siebenkopf/jet/1
After saving the long description, the location of the .rst file is shown, instead of its (parsed) content.
Note: When...I recently added documentation for a data format:
https://www.beat-eu.org/platform/dataformats/siebenkopf/jet/1
After saving the long description, the location of the .rst file is shown, instead of its (parsed) content.
Note: When I click on ``edit``, the correct .rst file is opened again.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/146The LaTeX interpreter in .rst files is quite poor2015-05-07T06:34:02ZManuel GüntherThe LaTeX interpreter in .rst files is quite poorFor some reason, the interpreter for LaTeX formulas in the documentation is rather poor.
When I compare the output of ``rst2html`` (generated on the Idiap machines; attached) with the web output:
https://www.beat-eu.org/platform/algori...For some reason, the interpreter for LaTeX formulas in the documentation is rather poor.
When I compare the output of ``rst2html`` (generated on the Idiap machines; attached) with the web output:
https://www.beat-eu.org/platform/algorithms/siebenkopf/GaborGraphSimilarity/12
I can see a clear difference, with a clear preference to ``rst2html``, at least in my browser (iceweasel).
This issue does not need to be solved immediately, but in the long term, formulas like the one in the link above don't really look nice.
[GaborGraphSimilarity.html](https://gitlab.idiap.ch/biometric/beat.web/uploads/b8d8d8568afd8f11af1b01acd1d925e4/GaborGraphSimilarity.html)
https://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/144Cancel button of experiment2015-05-06T12:26:39ZManuel GüntherCancel button of experimentWhen I want to cancel an experiment, and I click on the ``Cancel`` button, a window pops up, where I have the two choices: ``Yes, cancel it`` and ``Cancel``. So, which button do I use to cancel the experiment? From the text written on th...When I want to cancel an experiment, and I click on the ``Cancel`` button, a window pops up, where I have the two choices: ``Yes, cancel it`` and ``Cancel``. So, which button do I use to cancel the experiment? From the text written on the buttons, both do cancel the experiment.
Maybe we should rename the ``Cancel`` button in the pop-up window to something different, such as ``No, continue experiment``?Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://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/142Invalid error message in validation of environments2015-05-06T11:24:09ZLaurent EL SHAFEYInvalid error message in validation of environmentsDuring the validation of an environment, the following 500 internal error may happen:
Internal Server Error: /platform/admin/experiments/experiment/562/
Traceback (most recent call last):
File "/remote/sw/beat.env.deploy/usr/lib/p...During the validation of an environment, the following 500 internal error may happen:
Internal Server Error: /platform/admin/experiments/experiment/562/
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/contrib/admin/options.py", line 583, in wrapper
return self.admin_site.admin_view(view)(*args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 105, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/views/decorators/cache.py", line 52, in _wrapped_view_func
response = view_func(request, *args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/contrib/admin/sites.py", line 206, in inner
return view(request, *args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1456, in change_view
return self.changeform_view(request, object_id, form_url, extra_context)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 29, in _wrapper
return bound_func(*args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 105, in _wrapped_view
response = view_func(request, *args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/utils/decorators.py", line 25, in bound_func
return func.__get__(self, type(self))(*args2, **kwargs2)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/db/transaction.py", line 394, in inner
return func(*args, **kwargs)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/contrib/admin/options.py", line 1396, in changeform_view
if form.is_valid():
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/forms/forms.py", line 162, in is_valid
return self.is_bound and not bool(self.errors)
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/forms/forms.py", line 154, in errors
self.full_clean()
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/forms/forms.py", line 353, in full_clean
self._clean_fields()
File "/remote/sw/beat.env.deploy/usr/lib/python2.7/site-packages/django/forms/forms.py", line 371, in _clean_fields
value = getattr(self, 'clean_%s' % name)()
File "/remote/sw/beat.web/src/beat.web/beat/web/experiments/admin.py", line 66, in clean_file
self.cleaned_data['toolchain'].json())
File "/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py", line 88, in validate_experiment
return xp, xp.errors + validate_environments(xp)
File "/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py", line 63, in validate_environments
errors.append("The combination of queue '%s' with environment '%s (%s)' in the global experiment configuration does not exist" % (q, env_name, env_version))
UnboundLocalError: local variable 'q' referenced before assignmentTutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/141Public dataformats listed while sharing an experiment with a private algorithm 2015-05-06T11:41:03ZLaurent EL SHAFEYPublic dataformats listed while sharing an experiment with a private algorithm While turning an experiment public, few dataformats are listed in the sharing preferences, while there are public.
I think this is not expected.
More specifically, these dataformats are the ones used by a private algorithm, whose sha...While turning an experiment public, few dataformats are listed in the sharing preferences, while there are public.
I think this is not expected.
More specifically, these dataformats are the ones used by a private algorithm, whose sharing preferences are going to change, when the experiment become public.
In addition, I've noticed an inconsistency in the following two methods of the Experiment class in beat/web/experiments/models.py
* __share_dataformats
line 211: errors.extend(needed_format.is_accessible(users=users, teams=teams))
* __share_algorithms
line 238: errors.extend(needed_algorithm.is_accessible(False))
The method is_accessible() being common to both classes, the False argument is surprising. It is defined in beat/web/commons/models.py
155 def is_accessible(self, users=None, teams=None):
To reproduce the problem.
1. Create a new (private) version of an existing public algorithm
2. Run an algorithm with this private version of the algorithm
3. Try to make the experiment publicTutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/140Turning a private experiment into public does not seem to work2015-05-06T10:22:16ZLaurent EL SHAFEYTurning a private experiment into public does not seem to workWhen trying to make an experiment public, it currently causes a 500 internal error:
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, ...When trying to make an experiment public, it currently causes a 500 internal error:
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/experiments/api.py", line 689, in post
experiment.share(users=users, teams=teams, algorithms_infos=algorithms_infos)
File "/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py", line 358, in share
self.__share_algorithms(users=users, teams=teams, algorithms_infos=algorithms_infos)
File "/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py", line 243, in __share_algorithms
if algorithms_infos.has_key(algorithm.fullname()):
AttributeError: 'NoneType' object has no attribute 'has_key'Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.web/-/issues/139Parameter choices of type string are not displayed correctly in an experiment...2015-05-06T09:40:37ZManuel GüntherParameter choices of type string are not displayed correctly in an experiment designI have an algorithm, which takes as parameter a string, which can be selected from a list.
The list is correctly displayed in the algorithm page, but when I try to design and run an experiment, each letter is displayed individually, inc...I have an algorithm, which takes as parameter a string, which can be selected from a list.
The list is correctly displayed in the algorithm page, but when I try to design and run an experiment, each letter is displayed individually, including the ``[``, ``]`` and ``,`` characters.
As a consequence, I cannot run the experiment, but I rather get the error message:
```
"Traceback (most recent call last):\n File \"/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py\", line 131, in create_experiment\n experiment.save()\n File \"/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py\", line 291, in save\n raise SyntaxError(message % '\\n * '.join(errors))\nSyntaxError: The experiment isn't valid, due to the following errors:\n * /globals/siebenkopf/GaborGraphSimilarity/10/gabor_jet_similarity: cannot convert value `[' to required type: value for `gabor_jet_similarity' ('[') must be one of `['ScalarProduct', 'Canberra', 'Disparity', 'PhaseDiff', 'PhaseDiffPlusCanberra']'\n"
```
Enjoy debugging!
ManuelPhilip 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/137Algorithm parameters with 'choice' are not displayed properly in the experime...2015-05-06T11:32:02ZLaurent EL SHAFEYAlgorithm parameters with 'choice' are not displayed properly in the experiment setup pageAlgorithm parameters with 'choice' are not displayed properly in the experiment setup page.
To reproduce this bug, just create an experiment with the toolchain "tpereira/full_isv/2/".
Then for one of the cropping block, select the al...Algorithm parameters with 'choice' are not displayed properly in the experiment setup page.
To reproduce this bug, just create an experiment with the toolchain "tpereira/full_isv/2/".
Then for one of the cropping block, select the algorithm "tpereira/periocular_crop/3"
The "color" menu list then displays much more options than what it should.Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/136Link on algorithm name leads to an error2015-05-05T20:17:41ZAndré AnjosLink on algorithm name leads to an errorIf you load this public algorithm page:
https://www.beat-eu.org/platform/algorithms/elie_khoury/cepstral/1/
And then, right on the top, click on the word saying "cepstral", an error page will be produced.
The issue is that the f...If you load this public algorithm page:
https://www.beat-eu.org/platform/algorithms/elie_khoury/cepstral/1/
And then, right on the top, click on the word saying "cepstral", an error page will be produced.
The issue is that the formed URL is not legal. It must include the version number as well.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://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 GAISThttps://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/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/132In the experiment display page, toolchain naming is not consistent2015-05-05T19:22:59ZAndré AnjosIn the experiment display page, toolchain naming is not consistentIt is better now with the full name of the experiment being show. A little optimisation is required though:
<user> / "<maybe-another-user>/<toolchain-name>/<toolchain-version>" / <label>
<user> - Points to the user micro-site
"<ma...It is better now with the full name of the experiment being show. A little optimisation is required though:
<user> / "<maybe-another-user>/<toolchain-name>/<toolchain-version>" / <label>
<user> - Points to the user micro-site
"<maybe-another-user>/<toolchain-name>/<toolchain-version>" - Points to the toolchain
<label> - Points to self.
Could you please do it like so? Thanks, ATutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/131When creating a new version of an algorithm, outputs might disappear2015-05-06T14:26:22ZManuel GüntherWhen creating a new version of an algorithm, outputs might disappearI lately tried to create a new version of the algorithm:
https://www.beat-eu.org/platform/algorithms/tutorial/lbphs_features/2
This algorithm comes with two inputs and one output, which are correctly displayed in the last version (2).
...I lately tried to create a new version of the algorithm:
https://www.beat-eu.org/platform/algorithms/tutorial/lbphs_features/2
This algorithm comes with two inputs and one output, which are correctly displayed in the last version (2).
When I now try to create a new version (3) of the algorithm, the output disappears.
Saving the new version of the algorithm is not possible any more, so it seems to be a consistent issue.
Also, reloading the page doesn't help.
I hope that you can reproduce the issue. The algorithm is public.
Cheers, ManuelPhilip ABBETPhilip ABBET