beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2015-05-05T12:11:47Zhttps://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/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/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/122Creation of *public* algorithm/library/plotter from the admin page causes 500...2015-05-04T21:08:36ZLaurent EL SHAFEYCreation of *public* algorithm/library/plotter from the admin page causes 500 errorWhen using the admin page, the creation of algorithm/library/plotter leads to an internal error 500, when sharing is set to public.
There is no problem when the sharing attribute is set to private.When using the admin page, the creation of algorithm/library/plotter leads to an internal error 500, when sharing is set to public.
There is no problem when the sharing attribute is set to private.Tutorial for the FG2015 Conferencehttps://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/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/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/118beat.web.algorithms.Algorithm & related code cannot handle Libraries on save()2015-05-03T20:04:28ZAndré Anjosbeat.web.algorithms.Algorithm & related code cannot handle Libraries on save()As it is currently implemented, the Algorithm class on beat.web cannot handle an existing JSON (for example through an upload via the command-line), which references libraries. Its `save()` method will not updated the library relationshi...As it is currently implemented, the Algorithm class on beat.web cannot handle an existing JSON (for example through an upload via the command-line), which references libraries. Its `save()` method will not updated the library relationship as it should.
The JSON of an algorithm (or library for that matter), already contains a mapping description, which defines which libraries it uses. Upon `save()`, the field `referenced_libraries` should be updated.
I think the issue comes from the fact you can add a library w/o going through the `save()`, whereas I think the system was designed in such a way you must always go through the `save()`.
This means that any modification operation should:
1. Load the old JSON
2. Allow the user to modify it
3. Overwrite the old JSON on the object with the new one (at the file field)
4. Call the object's save() method
This strategy should automatically update the `referenced_libraries` field. This strategy also assures that we have a consistent representation of the object w.r.t. beat.web and beat.core.
We allow for no other way to modify this object.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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/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/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/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/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/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/109Cannot submit experiments with the green "Go" button2015-04-15T13:45:58ZAndré AnjosCannot submit experiments with the green "Go" buttonApparently, also a missing CSRF token somewhere.
PS: Would it be possible to scan for those missing places automatically?Apparently, also a missing CSRF token somewhere.
PS: Would it be possible to scan for those missing places automatically?Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/108Experiments panel at user micro-site is incomplete2015-04-14T09:32:00ZAndré AnjosExperiments panel at user micro-site is incompleteAfter the (very useful) mod to all visible objects displayed, there is a small issue concerning the experiment list: we cannot see who's the experiment owner. It would be good to add this field.
As a matter of fact, it would be better...After the (very useful) mod to all visible objects displayed, there is a small issue concerning the experiment list: we cannot see who's the experiment owner. It would be good to add this field.
As a matter of fact, it would be better to merge "Toolchain" and "Label" into a single heading (called "Label"), for which we print the whole experiment label (i.e. as returned by experiment.fullname()). That would be more consistent with the other panels.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/107Re-using a saved search after platform update not working2015-04-14T11:55:44ZSébastien MARCELRe-using a saved search after platform update not workingon my Search tab https://www.beat-eu.org/platform/user/smarcel/?tab=searches
I am re-using a previous search by clicking to reach
https://www.beat-eu.org/platform/search/smarcel/MOBIO/
and I got a pop-p error message "Error: Forbi...on my Search tab https://www.beat-eu.org/platform/user/smarcel/?tab=searches
I am re-using a previous search by clicking to reach
https://www.beat-eu.org/platform/search/smarcel/MOBIO/
and I got a pop-p error message "Error: Forbidden" then loading forever.
Alternatively on my Search tab I am not able to create new Search anymore ?
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/106Re-running forked experiments after platform update not working2015-05-07T08:30:02ZSébastien MARCELRe-running forked experiments after platform update not workingBug 1
Re-running https://www.beat-eu.org/platform/experiments/smarcel/tutorial/digit/2/character-recognition-2-mlp-nhu10-iter50-rr/
forked and named character-recognition-2-mlp-nhu10-iter50-rr3
pressed GO and pop-up error messag...Bug 1
Re-running https://www.beat-eu.org/platform/experiments/smarcel/tutorial/digit/2/character-recognition-2-mlp-nhu10-iter50-rr/
forked and named character-recognition-2-mlp-nhu10-iter50-rr3
pressed GO and pop-up error message "ERROR: The scheduler did not accept the experiment (saved for later execution).\nREASON: Block `mean_compute_train' of experiment `smarcel/tutorial/digit/2/character-recognition-2-mlp-nhu10-iter50-rr3' requests to run on queue `Default' (on 1 slot(s)) with environment `Scientific Python 2.7 (0.0.3)`, but that combination does not seem currently possible"
Bug 2
interestingly for on the same page I clicked to select a new Scientific Environment, pressed GO again I obtained a new pop-up error message:
"The label 'character-recognition-2-mlp-nhu10-iter50-rr3' is already used"
Bug 3 (similar to Bug 1?)
Re-running https://www.beat-eu.org/platform/experiments/smarcel/tpereira/full_isv/1/PR-ISV-mobio-male-rr/ (already attested)
forked and named PR-ISV-mobio-male-rr3
pressed GO and pop-up error message "Traceback (most recent call last):\n File \"/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py\", line 114, in create_experiment\n experiment.save()\n File \"/remote/sw/beat.web/src/beat.web/beat/web/experiments/models.py\", line 261, in save\n raise SyntaxError(message % '\\n * '.join(errors))\nSyntaxError: The experiment isn't valid, due to the following errors:\n * /globals: Additional properties are not allowed ('tpereira/periocular_crop' was unexpected) (rule: /properties/globals/additionalProperties)\n"
Bug 4 (similar to Bug 2 ?)
Re-running https://www.beat-eu.org/platform/experiments/smarcel/elie_khoury/ubmgmm_voxforge/1/ubmgmm-voxforge-g32iter25-rr2/
forked and named ubmgmm-voxforge-g32iter25-rr3
pressed GO and pop-up error message "ERROR: The scheduler did not accept the experiment (saved for later execution).\nREASON: Block `preprocessing_ubm' of experiment `smarcel/elie_khoury/ubmgmm_voxforge/1/ubmgmm-voxforge-g32iter25-rr3' requests to run on queue `Default' (on 1 slot(s)) with environment `Scientific Python 2.7 (0.0.3)`, but that combination does not seem currently possible"
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/105User w/o permissions can still access restricted queues2015-04-08T21:46:27ZAndré AnjosUser w/o permissions can still access restricted queuesFor example, the queue "Idiap Biometrics (Long)", should only be accessible to users of the "Idiap Biometrics" group, but are accessible to any user. Actually, there are no users on that group, so the queue should be accessible to none.For example, the queue "Idiap Biometrics (Long)", should only be accessible to users of the "Idiap Biometrics" group, but are accessible to any user. Actually, there are no users on that group, so the queue should be accessible to none.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/104Public algorithms are not being listed2015-04-10T10:08:24ZAndré AnjosPublic algorithms are not being listedIn the user microsite, the others' public algorithms available are not being displayed. Need a fix.In the user microsite, the others' public algorithms available are not being displayed. Need a fix.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAIST