beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2016-09-16T09:35:04Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/406[teams] Teams can be deleted, even if there are resources which are shared th...2016-09-16T09:35:04ZAndré Anjos[teams] Teams can be deleted, even if there are resources which are shared through themThere is, currently, some inconsistence with the team deletion property and sharing.
If a contribution is shared via a team with someone, then the contribution is marked as "Shared" (sharing status) and the team is add to its ``shared...There is, currently, some inconsistence with the team deletion property and sharing.
If a contribution is shared via a team with someone, then the contribution is marked as "Shared" (sharing status) and the team is add to its ``shared_with_team`` list.
The owner of the team may now proceed and delete the team, which will leave the contribution marked with ``Shared``, but now with no one on the ``shared_with_team`` list.
If the user has used the contribution, I'm not sure in which status that leaves us.
My understanding for the simplest way out is this: if a team has been used to share a contribution, it can no longer be deleted.Open-source Releasehttps://gitlab.idiap.ch/beat/beat.web/-/issues/407[experiments] can't share an experiments with the one I forked to toolchain from2016-03-02T13:39:20ZSébastien MARCEL[experiments] can't share an experiments with the one I forked to toolchain fromI forked this toolchain
https://www.beat-eu.org/platform/toolchains/smarcel/vein-recognition-example1/1/
from Philip
https://www.beat-eu.org/platform/toolchains/Kanma/vein_recognition/1/
but NOT the algorithms that were shared wi...I forked this toolchain
https://www.beat-eu.org/platform/toolchains/smarcel/vein-recognition-example1/1/
from Philip
https://www.beat-eu.org/platform/toolchains/Kanma/vein_recognition/1/
but NOT the algorithms that were shared with me.
Then I ran an expe from my new toolchain (including Philip algorithms) as:
https://www.beat-eu.org/platform/experiments/smarcel/smarcel/vein-recognition-example1/1/WV_PUT-R_dummy/
ran OK but when sharing the expe with Philip I had the error message:
Error during submission - BAD REQUEST (400)
Error:
The algorithm 'Kanma/rgb2gray/1' isn't usable by all
The algorithm 'Kanma/cropping_grayscale__u8_to_u8/1' isn't usable by all
The algorithm 'Kanma/rescale_grayscale__u8_to_f/1' isn't usable by all
The algorithm 'Kanma/histogram_equalization_f/1' isn't usable by all
The algorithm 'Kanma/smoothing_grayscale/1' isn't usable by all
The algorithm 'Kanma/thresholding/1' isn't usable by all
The algorithm 'Kanma/vein_enrollment/1' isn't usable by all
The algorithm 'Kanma/vein_user_enrollment/1' isn't usable by all
The algorithm 'Kanma/vein_hamming_scoring/1' isn't usable by all
This is strange as these also are shared with me !
https://gitlab.idiap.ch/beat/beat.web/-/issues/408[experiments] DB protocol sub-sets not assigned correctly in simple mode2016-03-01T17:44:29ZSébastien MARCEL[experiments] DB protocol sub-sets not assigned correctly in simple modeconfiguring a new expe from the
https://www.beat-eu.org/platform/toolchains/smarcel/vein-recognition-example1/1/
on the DB put vein by default we select in simple mode say "Wrist R" then it can be observed in advanced mode
that the...configuring a new expe from the
https://www.beat-eu.org/platform/toolchains/smarcel/vein-recognition-example1/1/
on the DB put vein by default we select in simple mode say "Wrist R" then it can be observed in advanced mode
that the sets are not assigned correctly:
Datasets [Reset]
train
putvein/1/wrist_R/dev_probes
dev_templates
putvein/1/wrist_R/test_templates
dev_probes
putvein/1/wrist_R/dev_templates
test_templates
putvein/1/wrist_R/train
test_probes
putvein/1/wrist_R/test_probes
the same issue was observed with other DBs.
Besides the fact that the user should double-check in advanced mode -- it will be great if the fuzzy matching probably used to check the corespondance here works better.https://gitlab.idiap.ch/beat/beat.web/-/issues/409[team] can't disable leaderboards shared with me2016-03-02T15:17:59ZSébastien MARCEL[team] can't disable leaderboards shared with meinteresting
Philip shared with me a search
https://www.beat-eu.org/platform/search/Kanma/putvein-wrist/
as I have already a similar search as leaderboard I wanted to see if I can disable the search from Philip on my page.
I not...interesting
Philip shared with me a search
https://www.beat-eu.org/platform/search/Kanma/putvein-wrist/
as I have already a similar search as leaderboard I wanted to see if I can disable the search from Philip on my page.
I noticed that all the search pages have now a tick-box on the right to subscribe / unsubscribe.
For this leaderboard shared with me this box is not ticked and I can't disable this leaderboard myself -- ticking on/off is not effective.
This is not critical but may be annoying if 10 people are sharing their leaderboards with me.
https://gitlab.idiap.ch/beat/beat.web/-/issues/410[user guide] all references to on request send to wrong email2016-03-03T10:34:31ZSébastien MARCEL[user guide] all references to on request send to wrong emailbeat.support@beat-eu.org -> beat.support@idiap.chbeat.support@beat-eu.org -> beat.support@idiap.chhttps://gitlab.idiap.ch/beat/beat.web/-/issues/411[algorithms] Editing an algorithm erase its short description2016-03-14T13:38:48ZPhilip ABBET[algorithms] Editing an algorithm erase its short descriptionSteps to reproduce:
1. Create and save a new algorithm
2. Fill its short description and save it
3. Edit the source code of the algorithm, save it
4. The short description is now empty
Note that the long description is still there.Steps to reproduce:
1. Create and save a new algorithm
2. Fill its short description and save it
3. Edit the source code of the algorithm, save it
4. The short description is now empty
Note that the long description is still there.https://gitlab.idiap.ch/beat/beat.web/-/issues/412[experiments] In the editor, boolean parameters aren't correctly displayed2016-03-14T16:34:17ZPhilip ABBET[experiments] In the editor, boolean parameters aren't correctly displayedOn Chrome on Windows, the checkbox of the boolean parameters is very big (see screenshot). In Firefox on Windows, it looks ok.
![Capture](/uploads/367f07367a4fe13f5c0eab8f6b26cc07/Capture.PNG)
Additionally, on both browsers, the do...On Chrome on Windows, the checkbox of the boolean parameters is very big (see screenshot). In Firefox on Windows, it looks ok.
![Capture](/uploads/367f07367a4fe13f5c0eab8f6b26cc07/Capture.PNG)
Additionally, on both browsers, the documentation string of the boolean parameter isn't displayed. I don't have access to my Mac right now to test if its displayed there.https://gitlab.idiap.ch/beat/beat.web/-/issues/413[experiments] The order of the blocks on the setup page seems random in Chrome2016-03-15T10:10:49ZPhilip ABBET[experiments] The order of the blocks on the setup page seems random in ChromeOn Firefox, their order match the logical flow of the toolchainOn Firefox, their order match the logical flow of the toolchainhttps://gitlab.idiap.ch/beat/beat.web/-/issues/414Experiments API issue ?2016-03-14T09:44:31ZFlavio TARSETTIExperiments API issue ?Some experiments are accessible, some not ?
This is strange:
Accessible:
http://beatweb-staging/api/v1/experiments/tutorial/tutorial/eigenface_with_preprocessing/1/atnt-eigenfaces-3-comp-preproc-para/
Not accessible:
http:...Some experiments are accessible, some not ?
This is strange:
Accessible:
http://beatweb-staging/api/v1/experiments/tutorial/tutorial/eigenface_with_preprocessing/1/atnt-eigenfaces-3-comp-preproc-para/
Not accessible:
http://beatweb-staging/api/v1/experiments/tutorial/tutorial/eigenface_with_preprocessing/1/atnt-eigenfaces-10-comp-tantriggs/Open-source ReleaseAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/14Security improvements2017-10-16T09:47:16ZAndré AnjosSecurity improvementsThis bug tracks improvements to the security for running user algorithms inside the beat backend.
The possible best way to handle this would be with RestrictedPython (see this SO thread http://stackoverflow.com/questions/1350466/preve...This bug tracks improvements to the security for running user algorithms inside the beat backend.
The possible best way to handle this would be with RestrictedPython (see this SO thread http://stackoverflow.com/questions/1350466/preventing-python-code-from-importing-certain-modules).Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/416When an algorithm with buggy documentation is forked, the documentation bug c...2016-03-14T13:39:35ZPavel KORSHUNOVWhen an algorithm with buggy documentation is forked, the documentation bug cannot be correctedIf an algorithm has wrong/buggy documentation, once it is forked, it can neither be corrected (documentation cannot be edited) nor it can be saved (platform complains about the bug). This issue prevents anyone, besides the author of the ...If an algorithm has wrong/buggy documentation, once it is forked, it can neither be corrected (documentation cannot be edited) nor it can be saved (platform complains about the bug). This issue prevents anyone, besides the author of the original algorithm, to edit or extent this algorithm.
An example of the algorithm with wrong documentation, which, effectively, cannot be corrected: http://beatweb-staging/algorithms/elie_khoury/gmm_scoring/
https://gitlab.idiap.ch/beat/beat.web/-/issues/417Clicking 'edit' for the algorithm leads to an empty page2016-03-14T17:10:16ZPavel KORSHUNOVClicking 'edit' for the algorithm leads to an empty pageWhen clicking edit or try to fork this algorithm:
https://www.beat-eu.org/platform/algorithms/pkorshunov/cepstral/
it leads to an empty page (tried on Mac's Chrome and Safari). When the page is checked with a browser inspection tool, a...When clicking edit or try to fork this algorithm:
https://www.beat-eu.org/platform/algorithms/pkorshunov/cepstral/
it leads to an empty page (tried on Mac's Chrome and Safari). When the page is checked with a browser inspection tool, an uncaught syntax error is reported in console.
I could not reproduce this issue with another algorithm.https://gitlab.idiap.ch/beat/beat.web/-/issues/418[reports] plot_404 error2016-03-21T15:27:04ZFlavio TARSETTI[reports] plot_404 erroron editable reports, plotter seems to sometimes get no experiment informationon editable reports, plotter seems to sometimes get no experiment informationOpen-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/419[reports] unable to do a PUT on reports2016-04-06T09:09:00ZFlavio TARSETTI[reports] unable to do a PUT on reportsThis is due to the merge/expand that corrupts the selected_template in the database.This is due to the merge/expand that corrupts the selected_template in the database.Open-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/420[reports] merge/expand correct flag to be set2016-04-06T09:09:01ZFlavio TARSETTI[reports] merge/expand correct flag to be setOpen-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/421[reports] fix alias issue2017-08-06T16:44:52ZFlavio TARSETTI[reports] fix alias issueOn dynamic aliasing, the experiment was not found and set to plotter as the alias changesOn dynamic aliasing, the experiment was not found and set to plotter as the alias changesOpen-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/422[reports] on multiple aliasing change avoid error with database2017-08-06T16:44:52ZFlavio TARSETTI[reports] on multiple aliasing change avoid error with databaseOpen-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/423[report] reload on saved and unified saving action with the rest of the report2017-08-06T16:44:52ZFlavio TARSETTI[report] reload on saved and unified saving action with the rest of the reportTo make sure everything is saved properly, it's better to reload the page after a save.To make sure everything is saved properly, it's better to reload the page after a save.Open-source ReleaseFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/424[search] Allow spaces separating terms in OR'ed search2017-08-06T16:44:52ZAndré Anjos[search] Allow spaces separating terms in OR'ed searchFeedback from an user:
```text
I have a minor reccomendation (not important). In the explanation of the search rules with OR operator:
"In order to search using a logical-OR, add search terms to the text boxes separated by a singl...Feedback from an user:
```text
I have a minor reccomendation (not important). In the explanation of the search rules with OR operator:
"In order to search using a logical-OR, add search terms to the text boxes separated by a single comma."
It could be useful to allow the "bar space" after the comma. I mean: "eifanfaces,fisherfaces" works well
as in the example but not "eifanfaces, fisherfaces". It will be very common error in my opinion (it was
my error :)). If it is not possible, you could add a warning about the use of space:
"In order to search using a logical-OR, add search terms to the text boxes separated by a single comma
(without bar-space between terms)."
For those who read fast the instructions.
```André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/425[algorithms] If algorithms are only usable, users can still see it through th...2017-08-06T16:44:52ZAndré Anjos[algorithms] If algorithms are only usable, users can still see it through the "diff" panelExample:
https://www.beat-eu.org/platform/algorithms/diff/anjithgeorge/KBOC_IITKGP_ANJITH_APRIL7_1/10/anjithgeorge/KBOC_IITKGP_ANJITH_APRIL7_1/14/
This option should be removed.Example:
https://www.beat-eu.org/platform/algorithms/diff/anjithgeorge/KBOC_IITKGP_ANJITH_APRIL7_1/10/anjithgeorge/KBOC_IITKGP_ANJITH_APRIL7_1/14/
This option should be removed.Open-source ReleaseAndré AnjosAndré Anjos