beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-03-09T09:20:51Zhttps://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.https://gitlab.idiap.ch/beat/beat.editor/-/issues/203MR pipeline2019-03-09T08:19:14ZFlavio TARSETTIMR pipeline@andre.anjos :
after the fix of bdt with the numpy pinning issue https://gitlab.idiap.ch/bob/bob.conda/merge_requests/403:
Please make sure to re-run this MR pipeline please:
https://gitlab.idiap.ch/beat/beat.editor/pipelines/27862
Thanks@andre.anjos :
after the fix of bdt with the numpy pinning issue https://gitlab.idiap.ch/bob/bob.conda/merge_requests/403:
Please make sure to re-run this MR pipeline please:
https://gitlab.idiap.ch/beat/beat.editor/pipelines/27862
ThanksAndré AnjosAndré Anjoshttps://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/69Errors building with bob.devtools2019-02-28T07:39:40ZJaden DIEFENBAUGHErrors building with bob.devtoolsI need to build it to work on the plotterparameter schema but it didn't work. I ran
```
$ bdt build -vv . --python=3.6
```
The first errors are the following:
```
...
running install_egg_info
Copying beat.core.egg-info to $PREFIX/lib/pyt...I need to build it to work on the plotterparameter schema but it didn't work. I ran
```
$ bdt build -vv . --python=3.6
```
The first errors are the following:
```
...
running install_egg_info
Copying beat.core.egg-info to $PREFIX/lib/python3.6/site-packages/beat.core-1.8.0b0-py3.6.egg-info
File "/home/jae/miniconda3/conda-bld/beat.core_1551291776091/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac
ehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/python3.6/site-packages/beat/core/test/prefix/databases/invalid/1.py", line 28
class View; # <-- syntax error!
^
SyntaxError: invalid syntax
File "/home/jae/miniconda3/conda-bld/beat.core_1551291776091/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac
ehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_pla/lib/python3.6/site-packages/beat/core/test/prefix/algorithms/user/syntax_error/1.py"
, line 29
class Algorithm;
^
SyntaxError: invalid syntax
...
```
Hopefully these errors aren't blocking the build because those syntax errors are actually intentional! The build continues and gets conda `ClobberWarning`s:
```
...
ERROR:conda.stderr:
ClobberWarning: This transaction has incompatible packages due to a shared path.
packages: http://www.idiap.ch/software/bob/conda/label/beta::beat.backend.python-1.6.2b0-py36h3c37dc0_3, file:///home/jae/miniconda3/conda-bld::beat.core-0.0.1-py36h1c6dc61_0
path: 'lib/python3.6/site-packages/beat/__init__.py'
...
```
After that there's alot of errors and exceptions, so I'm attaching the [bdt build log](/uploads/872db60d37880e72435fbc1020201099/bdt_build.log) and my [bdt environment package list](/uploads/32b39df45c96ab133890e5f63944f0c6/bdt_env_list.log).
This is using a python 3.6 conda environment and specifying python 3.6 for building beat.core, but the same-ish thing happens using python 3.7.
Should I not be using bob.devtools to build beat.core yet, or am I missing something?https://gitlab.idiap.ch/beat/beat.editor/-/issues/200Package.json became package.json.template2019-02-27T19:58:34ZJaden DIEFENBAUGHPackage.json became package.json.templateWhat happened? Renaming `package.json` to `package.json.template` breaks *alot* of stuff as everything nodejs-based assumes there's a file called `package.json` at the package root.What happened? Renaming `package.json` to `package.json.template` breaks *alot* of stuff as everything nodejs-based assumes there's a file called `package.json` at the package root.https://gitlab.idiap.ch/beat/beat.editor/-/issues/140Update Algorithm schema (and editor?)2019-02-26T18:00:07ZJaden DIEFENBAUGHUpdate Algorithm schema (and editor?)As of https://gitlab.idiap.ch/beat/beat.core/merge_requests/31#note_33390 , the algorithm schema in beat.core has been updated. Depending on the schema changes, there might need to be editor changes as well...As of https://gitlab.idiap.ch/beat/beat.core/merge_requests/31#note_33390 , the algorithm schema in beat.core has been updated. Depending on the schema changes, there might need to be editor changes as well...[v1] Ongoing patching until [v2] is readyhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/145New algorithms should come with an input & output in the first group2019-02-26T09:51:19ZJaden DIEFENBAUGHNew algorithms should come with an input & output in the first groupPretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the userPretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the user[v1] Ongoing patching until [v2] is readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/516Issues with installing demo data on v1.4.1 and master2019-02-25T18:34:53ZJaden DIEFENBAUGHIssues with installing demo data on v1.4.1 and masterWhen installing the dummy data in a new installation via `./bin/django install`, all the experiments & algorithms aren't installed due to errors (log attached). As I'm working on the reports app, I need at least some data to make reports...When installing the dummy data in a new installation via `./bin/django install`, all the experiments & algorithms aren't installed due to errors (log attached). As I'm working on the reports app, I need at least some data to make reports with.
I tried alot of different things hoping that I was doing something wrong, but I think the test data just hasn't been updated?
Repro:
- Clone beat.web
- Either stay on master or checkout tag `v.1.4.1`
- Run the commands in the README to install beat.web through conda/buildout
- Run `./bin/django install -v1` or `./bin/django install`
Expected:
The example data is installed to the new platform installation successfully and is available when running `./bin/django runserver`.
Actual:
There are only 14 toolchains, 2 libraries, and 10 dataformats available. Nothing else.
Logs:
Log for `./bin/django install`: [install.out](/uploads/8240025bc185d6aeca7d4a6072dafe27/install.out)
Log for `./bin/django install -v1`: [install_v1.out](/uploads/b91feb30aae43465e4a57982e50882d2/install_v1.out)https://gitlab.idiap.ch/beat/beat.editor/-/issues/192[meta] Naming branches to associate it with an issue2019-02-25T11:34:25ZJaden DIEFENBAUGH[meta] Naming branches to associate it with an issueIn `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressi...In `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressing? So names like the following are fine:
- "issue_20_fix_wrong_index"
- "implement_db_editor_248"
But names like the following aren't okay except in rare cases:
- "fix_wrong_index"
- "implement_db_editor"
I personally find it hard to understand what someone is doing in a branch when they don't reference an existing issue.
_[edit]_:
Final decision: <issue_number>_name_of_the_branchhttps://gitlab.idiap.ch/beat/beat.core/-/issues/67Algorithm prototype default dataformat not available on platform installation2019-02-25T08:32:27ZSamuel GAISTAlgorithm prototype default dataformat not available on platform installationThe `integers` dataformat used as default type when loading the algorithm prototype is not available on a default installation of the BEAT platoform.The `integers` dataformat used as default type when loading the algorithm prototype is not available on a default installation of the BEAT platoform.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/65Updates to the algorithm schema2019-02-23T18:21:47ZJaden DIEFENBAUGHUpdates to the algorithm schemaSee the relevant [beat.editor MR](https://gitlab.idiap.ch/beat/beat.editor/merge_requests/46) for how this started.
The algorithm schema is not specific enough, and needs some changing if the JSON schema tech allows it:
- There should b...See the relevant [beat.editor MR](https://gitlab.idiap.ch/beat/beat.editor/merge_requests/46) for how this started.
The algorithm schema is not specific enough, and needs some changing if the JSON schema tech allows it:
- There should be at least 1 output in the algorithm
- Every group should have at least 1 input (otherwise it's an empty group and should be removed)
- Analyzers *maybe* should be required to have at least 1 result
I'm pretty sure they are all possible to encode in the JSON schema.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.editor/-/issues/164What does browser-tests stage in the CI do?2019-02-14T22:12:46ZAndré AnjosWhat does browser-tests stage in the CI do?I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should **not** try to build the manual or check the package components anymore, as that will not fly with the current test strate...I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should **not** try to build the manual or check the package components anymore, as that will not fly with the current test strategy.
I made modifications to beat.cmdline and beat.core to take this into account (check latest MRs on those packages), simply making sure that `sphinx` and `conda` based test lines are only executed during the build and not in test-only phases.
I wanted to do the same for this package, but I wonder what the stage `browser-tests` really do. It seems to be not doing more than what is done during `build`.
Could @flavio.tarsetti clarify, please?Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/188Add port configuration to v1 for ALLIES partners2019-02-12T18:55:52ZJaden DIEFENBAUGHAdd port configuration to v1 for ALLIES partnersSummary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for ...Summary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for querying the API (JS code).
What does it provide?
Port configuration sufficient for the partner.
Relevant links / references
See https://groups.google.com/d/msg/beat-devel/m9vCN1J6I8E/pA9smNcXEgAJhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/88Remove "Documentation" tab, add "Info" & "Code" tabs2019-02-12T18:51:14ZJaden DIEFENBAUGHRemove "Documentation" tab, add "Info" & "Code" tabsInfo tab will have the RST file contents & its file path
Code tab will have the python file contents & its file path
Might eventually add RST rendering and/or in-browser editors
Would also need a "refresh" button on both to refresh fi...Info tab will have the RST file contents & its file path
Code tab will have the python file contents & its file path
Might eventually add RST rendering and/or in-browser editors
Would also need a "refresh" button on both to refresh file contentshttps://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/104Better path to files on the editors2019-02-07T11:53:56ZJaden DIEFENBAUGHBetter path to files on the 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/152Some suggestions for beat editor2019-01-28T10:11:31ZZohreh MOSTAANISome suggestions for beat editorHi,
Here are some ideas that I got while using beat editor. You might find them useful.
* I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and...Hi,
Here are some ideas that I got while using beat editor. You might find them useful.
* I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even though it is more convenient while making a toolchain to just connect an output to an input it is very difficult to understand what is going on when you look at an experiment using that toolchain, specially when the experiments get bigger and the connections are crossing each other. Even if there was a mechanism to highlight a chosen connection in the experiment page can be really helpful. This mechanism is already there when making a toolchain but not when you look at the experiment.
* It would be good if the user can assign a colour to a channel of data while making the toolchain. As far as I tried the channel colours are chosen by the system and in many times they are visually close to each other. I sometimes had difficulty distinguishing between them.
* It would be nice that user can change the name of groups while defining the algorithms. This is not the case as far as I experienced.
* It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
* It would be nice if the user can choose several connections and delete them altogether. Even if there was a button like "delete all connections" might be useful. I had painful experiences trying to remove all the connections but not the blocks. :)
I might be wrong about any of these points and the features may already be there. Please let me know if that is the case. :)https://gitlab.idiap.ch/beat/beat.editor/-/issues/138Can we use Conda's Node.js version?2019-01-28T04:37:00ZJaden DIEFENBAUGHCan we use Conda's Node.js version?Pretty sure we can't, but someone should look into it anyways.Pretty sure we can't, but someone should look into it anyways.