beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-12-20T18:24:38Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/513Release 1.4.1 through bob-release-scripts2018-12-20T18:24:38ZAndré AnjosRelease 1.4.1 through bob-release-scripts@samuel.gaist: may you please release version 1.4.1 of this package by tagging it with bob release scripts? You have everything in place now to go through the same workflow as for other packages.
If I look at the beat-eu.org/platform w...@samuel.gaist: may you please release version 1.4.1 of this package by tagging it with bob release scripts? You have everything in place now to go through the same workflow as for other packages.
If I look at the beat-eu.org/platform website, it unfortunately looks like version 1.3.1rc1 is deployed. You can see this by looking down on any webpage or by clicking on the user documentation. What I think happened is that you tagged the release w/o updating the value of the version inside `setup.py`.
The other issue is that there are not release notes for version 1.4.0 (https://gitlab.idiap.ch/beat/beat.web/tags/v1.4.0), so difficult to see what went on - which I'm sure was a lot of work. If you have the time, please update this.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/186v2/PyQt Infrastructure2019-04-25T10:37:07ZJaden DIEFENBAUGHv2/PyQt InfrastructureHere's a tracking issue for the non-editor work we'll need in V2.
- [x] Project layout (including Conda setup)
- [x] FS management
- [x] Network management
- [x] `beat.cmdline` integration (including layout stuff)
- [x] `beat.core` inte...Here's a tracking issue for the non-editor work we'll need in V2.
- [x] Project layout (including Conda setup)
- [x] FS management
- [x] Network management
- [x] `beat.cmdline` integration (including layout stuff)
- [x] `beat.core` integration (including Docker stuff)
- [x] PyQt app framework
- [x] Running example
- [x] Navigation
- [x] State management backend (see notes below)
- [x] Testing setup including example
- [x] Documentation setup if different than v1
- [x] CI integration
State management is all about providing a idiomatic interface to the various resources we work with (the prefix, APIs, docker images, graphviz, network, etc.):
- Lets the user undo/redo things
- Lets the app index & transform BEAT objects quickly
- Easy MapReduce-like operations on data
- Querying docker containers
- Querying Graphviz
- Lets us mock the resources easily for testing[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/185Experiment Editor2020-08-10T12:44:08ZJaden DIEFENBAUGHExperiment EditorThis issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] S...This issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] Smart filtering
Unlike all other BEAT assets, creating a new experiment requires an additional step therefore, a dedicated task is needed with regard to the creation of such a new asset:
* [x] Add support for new experiment creation to asset dialog[v2] 3 - Experiment editorSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/184Toolchain Editor2020-06-17T08:28:24ZJaden DIEFENBAUGHToolchain Editor[v2] 2 - Toolchain editorFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/183Database Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHDatabase Editor[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/182Plotterparameter Editor2019-10-04T15:12:26ZJaden DIEFENBAUGHPlotterparameter Editor[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/181Plotter Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHPlotter Editor[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/180Algorithm Editor2019-07-08T07:11:14ZJaden DIEFENBAUGHAlgorithm Editor[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://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/178Library Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHLibrary Editor[v2] 1 - Edition/Visualization for small editorshttps://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/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/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/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.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/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/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.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/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.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 DIEFENBAUGH