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.core/-/issues/31Experiment setup() does not handle properly blocks with multiple outputs2017-08-06T11:17:03ZLaurent EL SHAFEYExperiment setup() does not handle properly blocks with multiple outputsFollowing the major revamping of this package, blocks with multiple outputs are not handled in the right way.
In particular, the current implementation of the setup() method for Experiment assumes that a block has a single output (e.g. ...Following the major revamping of this package, blocks with multiple outputs are not handled in the right way.
In particular, the current implementation of the setup() method for Experiment assumes that a block has a single output (e.g. see https://gitlab.idiap.ch/biometric/beat.core/blob/v0.8.1/beat/core/experiment.py#L858).
I am unsure whether there are other implications in the code or not.Tutorial for the FG2015 ConferenceLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/9Problems with SQLite2017-10-04T21:58:16ZTiago de Freitas PereiraProblems with SQLiteThis issue applies for database views that use xbob.dbs with SQLite.
After several fetches in the database (during the execution of the next method in the view), the SQLAlchemy raises the exception "Cannot operate on a closed database...This issue applies for database views that use xbob.dbs with SQLite.
After several fetches in the database (during the execution of the next method in the view), the SQLAlchemy raises the exception "Cannot operate on a closed database".
For some reason the connection with the database closes in the middle of the execution.
A workaround was done redefining (inside the view) the pool configuration to NullPool(http://docs.sqlalchemy.org/en/latest/core/pooling.html#sqlalchemy.pool.NullPool).
This works, but we have no clue what is going on.
This bug keeps track of this issue.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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 GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/103The JS canvas of the toolchain editor stopped working2015-04-09T11:32:54ZAndré AnjosThe JS canvas of the toolchain editor stopped workingThe JS canvas of the JS editor stopped working after the last upgrade.
@philip.abbet: could you please take a look since you're our only expert on this component?The JS canvas of the JS editor stopped working after the last upgrade.
@philip.abbet: could you please take a look since you're our only expert on this component?Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/102"Send configuration to scheduler" button stopped working2015-04-08T20:00:54ZAndré Anjos"Send configuration to scheduler" button stopped workingAfter the latest upgrades, we can no longer send the configuration to the scheduler.
The reason is related:
```text
{"detail":"CSRF Failed: CSRF token missing or incorrect."}
```
A missing CSRF protection, likely, on the JS si...After the latest upgrades, we can no longer send the configuration to the scheduler.
The reason is related:
```text
{"detail":"CSRF Failed: CSRF token missing or incorrect."}
```
A missing CSRF protection, likely, on the JS side.
We must fix this ASAP.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/30beat db index improvements2017-08-06T11:17:03ZAndré Anjosbeat db index improvementsShould index all databases, if not specified which.
It should also support multiple databases to be indexed.Should index all databases, if not specified which.
It should also support multiple databases to be indexed.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/101Worker: missing easy deactivation action2015-04-20T16:26:07ZAndré AnjosWorker: missing easy deactivation actionIt should be possible to quickly deactivate a number of workers from the configuration, w/o removing all of the configuration from its place. This would allow us to adjust the farm size on demand.
Items to be executed:
- [x] Add a ...It should be possible to quickly deactivate a number of workers from the configuration, w/o removing all of the configuration from its place. This would allow us to adjust the farm size on demand.
Items to be executed:
- [x] Add a field on each worker indicating its state (active/deactive)
- [x] Add an action to the worker admin to deactivate/activate workers in batch
- [x] Modify the configuration logic so that, if a worker is active, is the same as it not belonging to the configuration
- [x] Display this information adequately on the scheduler/backend pageTutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/100Backend/scheduler administration page improvements2020-08-03T08:41:33ZAndré AnjosBackend/scheduler administration page improvementsA small list of improvements for the backend/scheduler page:
1. The worker listing takes too much space and does not allow for the visualisation of important information. It would be better to transform it into a table, in which each ...A small list of improvements for the backend/scheduler page:
1. The worker listing takes too much space and does not allow for the visualisation of important information. It would be better to transform it into a table, in which each line corresponds to a host and each column shows the following information: IP address, cores (in-use/available), memory (in-use/available), beat.scheduler version. The color of the line can be color coded: light green means 100% free, light read means 100% occupied, light yellow means partially occupied.
2. The total number of cores affected to a queue should be displayed
3. The queue listing should also become a table with more compact information displayed.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/99Normal registration and minimal profile page2015-05-01T16:08:43ZAndré AnjosNormal registration and minimal profile pageFor the tutorial in May, we absolutely need to put in place a minimal registration page (or revive the one we have) and let users change passwords and reset their secret tokens via a profile page.
Here are the features:
- [x] Reviv...For the tutorial in May, we absolutely need to put in place a minimal registration page (or revive the one we have) and let users change passwords and reset their secret tokens via a profile page.
Here are the features:
- [x] Revive registration
- [x] Allow users to reset their passwords using their profile page
- [x] Allow users to re-generate their secret tokens using their profile pageTutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://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/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 Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/96Inspect the experiment datasets2015-05-04T16:42:23ZTiago de Freitas PereiraInspect the experiment datasetsWhen a experiment is opened, it is not possible to see the dataset setup.
When a experiment is opened, it is not possible to see the dataset setup.
Tutorial for the FG2015 Conferencehttps://gitlab.idiap.ch/beat/beat.web/-/issues/95Search for experiments with datasets of different databases2015-06-17T07:04:23ZTiago de Freitas PereiraSearch for experiments with datasets of different databasesHi,
In the experiment setup, it is possible to play with datasets of different databases.
For example, I can define the train and the development set of one database and select the test set of another.
However, once the experiment i...Hi,
In the experiment setup, it is possible to play with datasets of different databases.
For example, I can define the train and the development set of one database and select the test set of another.
However, once the experiment is done, there is not a nice way to serch for this particular dataset setup.
I think we should think in a way to do it nicely.
Thanks
TiagoBEAT Tourhttps://gitlab.idiap.ch/beat/beat.web/-/issues/94URL field "format=string" does not work after Django rest framework port2015-03-27T12:38:34ZAndré AnjosURL field "format=string" does not work after Django rest framework portThis field in the URL is used by the rest framework to define which serializer/marshaller to use.
We will need to change this everywhere to something like `object-format=string`.This field in the URL is used by the rest framework to define which serializer/marshaller to use.
We will need to change this everywhere to something like `object-format=string`.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAIST