beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-12-06T09:53:24Zhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/53strange behaviour of beat.cmline when pulling objects from platform results i...2018-12-06T09:53:24ZZohreh MOSTAANIstrange behaviour of beat.cmline when pulling objects from platform results in beat.editor crashing as well.Hi,
Today when I ran beateditor command to edit some experiment, it did not show me anything on the Firefox. It only shows the page for split second and then it is a blank page. I updated beat.editor with conda in case there were some c...Hi,
Today when I ran beateditor command to edit some experiment, it did not show me anything on the Firefox. It only shows the page for split second and then it is a blank page. I updated beat.editor with conda in case there were some changes but the problem is still there.https://gitlab.idiap.ch/beat/beat.core/-/issues/10Library support2018-11-03T15:23:12ZAndré AnjosLibrary supportA ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installe...A ticket for holding information on library support. Some aspects discussed over the last months:
- The easiest to start with would be: 1 library = 1 file, pretty much like algorithms.
- External (bigger packages) need to be installed with the processing environment.
- Libraries should be version-nable such as algorithms.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/483[experiments] Not allowed to share unfinished experiments2017-12-04T10:46:41ZPavel KORSHUNOV[experiments] Not allowed to share unfinished experimentsI forked the experiment, modified an algorithm, started the experiment, and tried to share it with @sebastien.marcel but got the error that "This experiment is not done yet", then it went to "page not found" page.
Here is the experiment...I forked the experiment, modified an algorithm, started the experiment, and tried to share it with @sebastien.marcel but got the error that "This experiment is not done yet", then it went to "page not found" page.
Here is the experiment:
https://www.beat-eu.org/platform/experiments/pkorshunov/pkorshunov/speech-pad-simple/1/speech-pad_lbp_hist_ratios_lr-pa_aligned-rr4/
Here is the error, when tried to share it:
![Screen_Shot_2017-12-04_at_11.11.13](/uploads/8e927c930758d1f1805658c26c8abf36/Screen_Shot_2017-12-04_at_11.11.13.png)https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/54Linux builds are failing with new docker-py 3.6.02018-12-15T07:15:00ZAndré AnjosLinux builds are failing with new docker-py 3.6.0@samuel.gaist: could you have a look at this today?
Job [#153447](https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/153447) failed for 2580eac2427657fd6b7cf395b03b4a06bdcd3745:
N.B.: there is an issue with the current "Schedules" featur...@samuel.gaist: could you have a look at this today?
Job [#153447](https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/153447) failed for 2580eac2427657fd6b7cf395b03b4a06bdcd3745:
N.B.: there is an issue with the current "Schedules" feature of gitlab (https://secure.idiap.ch/bugzilla5/show_bug.cgi?id=15791)
TBC: I just re-ran the nightlies manually to see if the builds would get stuck in the same position: https://gitlab.idiap.ch/beat/beat.nightlies/pipelines/25464Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/9Versionning support2018-11-03T15:23:12ZAndré AnjosVersionning supportAutomatic versionning suport should be implemented through out the platform. I'm putting this bug here, but surely this affects most packages in the project. I detail our existing workplan and some key behavioral aspects.
- Each objec...Automatic versionning suport should be implemented through out the platform. I'm putting this bug here, but surely this affects most packages in the project. I detail our existing workplan and some key behavioral aspects.
- Each object in the system (databases, toolchains, dataformats, algorithms, attached documentation strings, environments) should be version-able. Every time the user uploads or changes that object, the version number of that object is bumped.
- Each time a new version is entered, the user should be able to attach a version comment, which is independent from the object documentation itself.
- For the platform, the combination of the object name and the version determines the uniqueness of such object.
- The sharing, usage and tagging status of each unique object (name/version) should be tracked independently. This outdates the usage of "/private" paths which seems to be a bit confusing for some users.
- While visualizing the object, the user by defaults accesses the latest version to which it has access to. This should be made consistent through the platform.
- There is always an option to see/use an earlier version of an object, but that requires the user to specify it explicitly. For example, in the command-line utilities, a "--version=xxx" could be passed. On the web interface, the version of a certain object is chosen automatically as the latest, but a field allows the user to browse for an earlier version.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.web/-/issues/484[backend] Not all available resources are being utilised2017-12-04T10:47:12ZAndré Anjos[backend] Not all available resources are being utilisedFor some reason, there are experiments being scheduled and get stuck on apparent lack of resources. Meanwhile, there are idle computers on the system that seem to not take any jobs:
![image](/uploads/f0771efaf35e733b2fa76b7821a9b7f1/ima...For some reason, there are experiments being scheduled and get stuck on apparent lack of resources. Meanwhile, there are idle computers on the system that seem to not take any jobs:
![image](/uploads/f0771efaf35e733b2fa76b7821a9b7f1/image.png)Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/54Implement Bob's tutorial experiment by scratch2018-05-22T14:53:43ZJaden DIEFENBAUGHImplement Bob's tutorial experiment by scratchConvert [the tutorial](https://www.idiap.ch/software/bob/docs/bob/bob/master/example.html) and find pain pointsConvert [the tutorial](https://www.idiap.ch/software/bob/docs/bob/bob/master/example.html) and find pain pointsStuff before worrying about deploymenthttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/55beat --version does not work at latest release2019-01-21T14:07:25ZAndré Anjosbeat --version does not work at latest releaseWhat I get:
```sh
$ beat --version
Usage: ....
Error: Missing Command.
$
```What I get:
```sh
$ beat --version
Usage: ....
Error: Missing Command.
$
```Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/22investigate graphviz formating the toolchains via server endpoint2018-05-15T09:52:51ZJaden DIEFENBAUGHinvestigate graphviz formating the toolchains via server endpointStuff before worrying about deploymenthttps://gitlab.idiap.ch/beat/beat.editor/-/issues/91Auto-launch new browser tab when starting `beateditor` script2018-05-04T13:11:00ZJaden DIEFENBAUGHAuto-launch new browser tab when starting `beateditor` scriptAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/57"potentially unsaved changes" remark2018-03-20T15:27:38ZJaden DIEFENBAUGH"potentially unsaved changes" remarkActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to serverActually checking if the server element is different than the local element is too expensive. Just have a flag "potential_changes_made" that turns on when the user edits something, and turns off when they save/write to serverhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/51Assigning a protocol for an experiment's datasets doesn't always assign the d...2018-03-13T13:21:59ZJaden DIEFENBAUGHAssigning a protocol for an experiment's datasets doesn't always assign the datasets properlyThis is an issue with the `user/user/fisherface/1/atnt` experiment. After pulling it from a local BEAT instance, it using the `atnt/3` database. Because the current version of `beat.cmdline` only supports `atnt/5`, I pulled that db tried...This is an issue with the `user/user/fisherface/1/atnt` experiment. After pulling it from a local BEAT instance, it using the `atnt/3` database. Because the current version of `beat.cmdline` only supports `atnt/5`, I pulled that db tried to update all the experiment's datasets by selecting the `idiap_test_eyepos (atnt/5)` protocol option. It flipped the dev/test datasets when assigning
![image](/uploads/d3911ac58df31633c60fdf8d7d05150f/image.png)https://gitlab.idiap.ch/beat/beat.editor/-/issues/60If toolchain is empty, start at 0,02018-03-13T11:16:25ZJaden DIEFENBAUGHIf toolchain is empty, start at 0,0https://gitlab.idiap.ch/beat/beat.editor/-/issues/65When deleting a toolchain, delete experiments that used it2018-03-13T10:25:55ZJaden DIEFENBAUGHWhen deleting a toolchain, delete experiments that used it(also provide a popup window confirming?)(also provide a popup window confirming?)https://gitlab.idiap.ch/beat/beat.editor/-/issues/63Safely create/cast objects using the respective editor's `getValidObject` func2018-03-09T15:40:14ZJaden DIEFENBAUGHSafely create/cast objects using the respective editor's `getValidObject` funcInspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.Inspired by all the work I have to do to handle malformed objects.
Instead of trusting the objects, use the editor getObject funcs to cast objs in `selectors.jsx`.https://gitlab.idiap.ch/beat/beat.core/-/issues/63`scripts/before_test.sh` has functionality that is required beyond this package2019-02-19T10:40:06ZAndré Anjos`scripts/before_test.sh` has functionality that is required beyond this packageThis script is responsible for 2 actions:
- pulling images for running tests
- ~~compiling c++-backend algorithms for testing~~
An equivalent script exists in beat.cmdline. This script is also called inside beat.web.
To align with a ...This script is responsible for 2 actions:
- pulling images for running tests
- ~~compiling c++-backend algorithms for testing~~
An equivalent script exists in beat.cmdline. This script is also called inside beat.web.
To align with a better DRY policy, the functionality of this script should be python-ified and provided as a service to callers. This problem relates to having a saner implementation beat/beat.web#510.
At this point, it may be desirable to update docker-py and related dependencies on our CI.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/56There is no way to make a clean prefix directory structure with only trusted ...2018-12-21T14:52:06ZZohreh MOSTAANIThere is no way to make a clean prefix directory structure with only trusted system files.In the ALLIES meeting one of the points that was raised was that how to get a clean prefix directory structure, with databases, dataformats, etc in place. With only data from the system not other users, and not to go through copying a pr...In the ALLIES meeting one of the points that was raised was that how to get a clean prefix directory structure, with databases, dataformats, etc in place. With only data from the system not other users, and not to go through copying a prefix from another git repository.
It may be possible to use command line to make such a directory.https://gitlab.idiap.ch/beat/beat.editor/-/issues/56More help text in the editors2018-05-03T10:19:36ZJaden DIEFENBAUGHMore help text in the editorsE.g.:
- Explaining what the template names/view names are in the db editorE.g.:
- Explaining what the template names/view names are in the db editorhttps://gitlab.idiap.ch/beat/beat.core/-/issues/64Database schema and runtime improvements2021-01-29T09:46:59ZAndré AnjosDatabase schema and runtime improvementsDatabases were originally designed monolithically, assuming the environment where packages necessary to read their contents is fixed (and does not change), and the location of files to be used for the readout is fixed. As an after thoug...Databases were originally designed monolithically, assuming the environment where packages necessary to read their contents is fixed (and does not change), and the location of files to be used for the readout is fixed. As an after thought, templates were introduced without a proper formalisation and, as a consequence, templates with the same names may appear in various database JSON declarations, w/o necessarily being the same. This issue supersedes #25 and gathers all changes required for a revamp in this area:
- [x] Protocol and set templates should be separated from the database view declaration to avoid repetition and centralise "task-related" declarations. This will effectively simplify the declaration of new datasets
- [ ] The `root_db` parameter (maybe misspelled here) needs to be externalised as a runtime parameter during the run, as it is currently the case for other runtime prefixes such as algorithm caches. Currently, if one downloads the database view, they need to change this parameter by hand
- [x] The environment required to run the database view to provide the data for the experiment needs to be configured and have an entry on the database JSON declaration. This ensures that changes in the environment (docker image), will imply in new caches being generated at all times. As of today, it can happen that hashes are not regenerated even if the environment changes completely.
- [x] A default db env docker image (possibly named `beat.env.databases`) should be provided on docker hub. This avoids conflicts in future because when using multiple databases in one experiment, only one image can be used.
- [ ] The prototypes in `beat.core` should come configured to use this image.
- [ ] This new JSON entry must be documented in `beat/docs` and users should be recommended to use this image.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/57Not compatible with newest bob-devel version2019-03-09T09:20:51ZJaden DIEFENBAUGHNot compatible with newest bob-devel versionSee beat.editor#202 for how I found this & a hack to fix it
Using the default conda environment creation config, `beat.cmdline` can't be installed to the same environment as `bob-devel=2019.2.11`. This also pops up when trying to create...See beat.editor#202 for how I found this & a hack to fix it
Using the default conda environment creation config, `beat.cmdline` can't be installed to the same environment as `bob-devel=2019.2.11`. This also pops up when trying to create an environment for `beat.web` using `conda env create -f dev.yml`:
```
Collecting package metadata: done
Solving environment: failed
UnsatisfiableError: The following specifications were found to be in conflict:
- beat.cmdline
- bob-devel=2019.02.11
Use "conda search <package> --info" to see the dependencies for each package.
```
This marks the third place this issue has shown up, and so I'm opening an issue in this package. I'll mark it as `critical` because this is an issue in the CI as well.