beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-11-27T11:19:24Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/171beat editor does not accept api version 2 as valid2018-11-27T11:19:24ZZohreh MOSTAANIbeat editor does not accept api version 2 as validI am trying to test algorithms written with api version 2 that is introduced in the new platform release. beat editor shows them as invalid all the time. The experiments are running and the algorithms are correct.I am trying to test algorithms written with api version 2 that is introduced in the new platform release. beat editor shows them as invalid all the time. The experiments are running and the algorithms are correct.https://gitlab.idiap.ch/beat/beat.web/-/issues/507The documentation is not backed up like other beat packages2018-12-18T07:06:07ZZohreh MOSTAANIThe documentation is not backed up like other beat packagesThe documentation for other beat packages are automatically backed up on https://www.idiap.ch/software/beat//docs/beat/ except for beat.web. This will be problematic since I am going to change the documentation of beat platform.The documentation for other beat packages are automatically backed up on https://www.idiap.ch/software/beat//docs/beat/ except for beat.web. This will be problematic since I am going to change the documentation of beat platform.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/508Password reset is not implemented2019-03-20T10:49:08ZAndré AnjosPassword reset is not implementedCurrently, there exists no way to recover the password from the platform. This is an important feature we need to implement.Currently, there exists no way to recover the password from the platform. This is an important feature we need to implement.https://gitlab.idiap.ch/beat/beat.editor/-/issues/172CI broken - "npm not found"2018-12-06T10:24:07ZJaden DIEFENBAUGHCI broken - "npm not found"See https://gitlab.idiap.ch/beat/beat.editor/-/jobs/152718, specifically the line:
```
/local/builds/beat/beat.editor/miniconda/conda-bld/beat.editor_1543860509476/work/conda_build.sh: line 5: npm: command not found
```
This is in the ...See https://gitlab.idiap.ch/beat/beat.editor/-/jobs/152718, specifically the line:
```
/local/builds/beat/beat.editor/miniconda/conda-bld/beat.editor_1543860509476/work/conda_build.sh: line 5: npm: command not found
```
This is in the build step, so it doesn't concern the testing docker image.https://gitlab.idiap.ch/beat/beat.web/-/issues/510Improve CI to use conda-packages and python 3.62018-12-20T17:32:31ZAndré AnjosImprove CI to use conda-packages and python 3.6Our CI infrastructure for this package still uses Python 2.7!
A list of points we should consider when upgrading this:
- [x] Python 3.6
- [x] Use the latest beat-devel to install things like sphinx, nose, coverage and other required ba...Our CI infrastructure for this package still uses Python 2.7!
A list of points we should consider when upgrading this:
- [x] Python 3.6
- [x] Use the latest beat-devel to install things like sphinx, nose, coverage and other required base infrastructure
- [x] Install beat.cmdline, core and backend.python from our conda channel (beta) - if that is not possible, ensure this package only tests against the "master" branches of each of those
- [x] Reduce specific package pinning to the minimal required
- [x] buildout phase should not install anything - the file `dev.yml` should contain all dependencies - except, perhaps, the javascript stuff
- [x] the scripts to build .so files on beat.core is being called from this package - maybe we should consider to distribute pre-built binaries with beat.core for such a purpose? In particular, inside `buildout.cfg` we call these - need to figure out a solution...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.web/-/issues/511Unable to build the doumentation2018-12-18T10:09:22ZZohreh MOSTAANIUnable to build the doumentationUntil now I was building the documentation of beat.docs that checks out the beat.web package and it is building the documentation. But when I try to build only the documentation of beat.web separately I get this error.
```
pkg_resources...Until now I was building the documentation of beat.docs that checks out the beat.web package and it is building the documentation. But when I try to build only the documentation of beat.web separately I get this error.
```
pkg_resources.DistributionNotFound: The 'beat.web' distribution was not found and is required by the application
```
Any ideas?https://gitlab.idiap.ch/beat/beat.editor/-/issues/173[CI] tests are failing2018-12-15T15:30:54ZZohreh MOSTAANI[CI] tests are failingMy pipelines are failing with ``npm`` errors. @jdiefenbaugh could you please take a look?My pipelines are failing with ``npm`` errors. @jdiefenbaugh could you please take a look?Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://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/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.editor/-/issues/174JSON schema duplication2019-03-07T21:13:26ZSamuel GAISTJSON schema duplicationThe files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
-...The files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
- The folder content is not even a copy of the beat.core content so they are currently different
- New versions of the schema are not available
The only official schemas are the ones from beat.core. Those must be used and not copied.
Relates to #140 [v1] Ongoing patching until [v2] is readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://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.web/-/issues/512Documentation still mentions "Biometrics"2019-11-04T08:35:20ZAndré AnjosDocumentation still mentions "Biometrics"We should remove this from the docs.We should remove this from the docs.Zohreh MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/docs/-/issues/8Various documentation warnings2019-07-02T10:29:31ZAndré AnjosVarious documentation warningsThere are some various documentation warnings being emitted with the current aggregated documentation. While some are OK-ish, others are not. We need to go through all of these and correct them ASAP.There are some various documentation warnings being emitted with the current aggregated documentation. While some are OK-ish, others are not. We need to go through all of these and correct them ASAP.Zohreh MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/175[v2] Coding Guidelines2019-01-23T08:46:31ZFlavio TARSETTI[v2] Coding GuidelinesThe following document proposes the guidelines to be followed for the implementation beat.editor version 2.
- all features need mandatory tests to be validated
- code should be well written and documented to be validated
- usage of *bl...The following document proposes the guidelines to be followed for the implementation beat.editor version 2.
- all features need mandatory tests to be validated
- code should be well written and documented to be validated
- usage of *black for python* and other tools to standardize the code
- we will be updating a set of guidelines to follow for the new version
- 1 merge request per feature and bug fix only
- only *atomic* commits
- clean commit messages (i.e.: [plotter] added plotter lines generation. Fixes #xx)
- A nose testable editor or we could look at pytest-qt too[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/176toolchain naming2019-02-07T15:06:01ZFlavio TARSETTItoolchain namingDuring our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect...During our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect is that adding multiples inputs shouldn't overwrite the previous input names.
@jdiefenbaugh : Can you fix this please? Thanks.[v1] Ongoing patching until [v2] is readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/177[v2] Mockups2019-01-28T18:52:11ZFlavio TARSETTI[v2] MockupsHere are the mockups of the application:
A) The mockup of the new version of the application:
![beat_editor_mockup](/uploads/985dead99bd192aa277455c609fbeb31/beat_editor_mockup.png)
B) The mockup of the menus editor:
![beat_editor_me...Here are the mockups of the application:
A) The mockup of the new version of the application:
![beat_editor_mockup](/uploads/985dead99bd192aa277455c609fbeb31/beat_editor_mockup.png)
B) The mockup of the menus editor:
![beat_editor_menus](/uploads/eab010c6104d5b95370b839d15cbc786/beat_editor_menus.png)[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/178Library Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHLibrary Editor[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/179Dataformat Editor2019-04-02T19:15:51ZJaden DIEFENBAUGHDataformat Editor[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/180Algorithm Editor2019-07-08T07:11:14ZJaden DIEFENBAUGHAlgorithm Editor[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAIST