beat issues
https://gitlab.idiap.ch/groups/beat/-/issues
2018-05-15T09:27:04Z
https://gitlab.idiap.ch/beat/beat.editor/-/issues/102
Fix toolchain connection bug
2018-05-15T09:27:04Z
Jaden DIEFENBAUGH
Fix toolchain connection bug
Basically creating connections is apparently pretty funky
Basically creating connections is apparently pretty funky
2018-05-18
https://gitlab.idiap.ch/beat/beat.editor/-/issues/103
Fix toolchain insertion into toolchain
2018-05-15T08:07:02Z
Jaden DIEFENBAUGH
Fix toolchain insertion into toolchain
It broke with recent changes somehow
It broke with recent changes somehow
2018-05-18
https://gitlab.idiap.ch/beat/beat.editor/-/issues/106
Dont clear history on save
2018-05-15T08:49:44Z
Jaden DIEFENBAUGH
Dont clear history on save
When a toolchain's redux model updates, still save the history
"should" be an easy fix
When a toolchain's redux model updates, still save the history
"should" be an easy fix
https://gitlab.idiap.ch/beat/beat.editor/-/issues/105
Only 1 save button
2018-05-15T08:49:44Z
Jaden DIEFENBAUGH
Only 1 save button
It's confusing enough without having to deal with two save buttons!
For now just have the one in the editors
It's confusing enough without having to deal with two save buttons!
For now just have the one in the editors
https://gitlab.idiap.ch/beat/beat.core/-/issues/103
Allow mounting of datasets folder on the algorithm container.
2020-11-12T16:47:35Z
Samuel GAIST
Allow mounting of datasets folder on the algorithm container.
In the context of the learn-real project, the training of robot related models requires the use of a very high number of images which can only be optimally loaded using PyTorch iterators.
This cannot be done currently as all data goes t...
In the context of the learn-real project, the training of robot related models requires the use of a very high number of images which can only be optimally loaded using PyTorch iterators.
This cannot be done currently as all data goes through the database paradigm which cannot be used directly by PyTorch iterators.
Using the standard BEAT approach would lead to overly complex and inefficient implementation.
The solution proposed is that a new property can be inserted in the block configuration so that the root path of the database is also mounted on the algorithm container.
This will only work on algorithm containers that are connected to a database.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/114
Make virtualbox image (using packer)
2018-06-04T07:27:25Z
Jaden DIEFENBAUGH
Make virtualbox image (using packer)
See:
- https://gitlab.idiap.ch/fspr/virtual-image/blob/master/image.json
- https://www.serverlab.ca/tutorials/dev-ops/automation/how-to-use-packer-to-create-ubuntu-18-04-vagrant-boxes/
See:
- https://gitlab.idiap.ch/fspr/virtual-image/blob/master/image.json
- https://www.serverlab.ca/tutorials/dev-ops/automation/how-to-use-packer-to-create-ubuntu-18-04-vagrant-boxes/
https://gitlab.idiap.ch/beat/beat.editor/-/issues/116
Bug with creating toolchain in tutorial - says it's invalid even though it lo...
2018-06-04T07:29:12Z
Jaden DIEFENBAUGH
Bug with creating toolchain in tutorial - says it's invalid even though it looks valid
See the VM from the HES-SO tutorial
See the VM from the HES-SO tutorial
https://gitlab.idiap.ch/beat/beat.editor/-/issues/90
Separate cloning & versioning functionality in list views
2018-05-18T14:29:39Z
Jaden DIEFENBAUGH
Separate cloning & versioning functionality in list views
Right now there's only a "clone" button that does double duty.
There should be a "clone" button that requires a new object name and pins the version to "1"
There should be a "new version" button that pins the name and ups the version b...
Right now there's only a "clone" button that does double duty.
There should be a "clone" button that requires a new object name and pins the version to "1"
There should be a "new version" button that pins the name and ups the version by one
https://gitlab.idiap.ch/beat/beat.editor/-/issues/107
Throttle clicking on blocks in tc editor so doubleclicks dont open/close the ...
2018-05-15T09:54:42Z
Jaden DIEFENBAUGH
Throttle clicking on blocks in tc editor so doubleclicks dont open/close the modal really fast
https://gitlab.idiap.ch/beat/beat.core/-/issues/104
Experiment global properties regex is wrong for algorithms name
2020-11-12T12:20:40Z
Samuel GAIST
Experiment global properties regex is wrong for algorithms name
The `patternProperties` definition for algorithm related properties is missing `-` for the author part of the regex so it forbids creating experiments using valid algorithms.
The `patternProperties` definition for algorithm related properties is missing `-` for the author part of the regex so it forbids creating experiments using valid algorithms.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.core/-/issues/105
Refactor database sharing
2020-11-17T12:09:23Z
Samuel GAIST
Refactor database sharing
Following discussion on beat/beat.web!410, the database sharing feature will be refactored with the following:
- Add a new `direct_rawdata_access` optional field to the database schema
- Use that in place of the optional "share_databases...
Following discussion on beat/beat.web!410, the database sharing feature will be refactored with the following:
- Add a new `direct_rawdata_access` optional field to the database schema
- Use that in place of the optional "share_databases" external field
- The field will apply to both v1 and v2 Database schema
- Support for optional field allows to keep the current databases working
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.core/-/issues/106
ROS specific needs
2020-11-30T08:50:02Z
Samuel GAIST
ROS specific needs
Requirement
===========
In the scope of the learn-real project, ROS is one of the possible system used however it needs to write some files (pids, small logs, etc.) in order to run properly however these can be discarded when the run en...
Requirement
===========
In the scope of the learn-real project, ROS is one of the possible system used however it needs to write some files (pids, small logs, etc.) in order to run properly however these can be discarded when the run ends.
The current estimation done by @cazinn for the space needed is about 10Mb.
The ROS main folder is `~.ros` by default and that can be changed using the [ROS_HOME environment variable](http://wiki.ros.org/ROS/EnvironmentVariables#System_Data_Environment_Variables).
Current situation
=================
For security reasons, our containers are run in read-only mode with two small read/write tmpfs mounted on the containers: /tmp and /var. Each of which is allocated 500kb which is enough for the use of BEAT.
We do have support for adding temporary volumes in place as well as setting custom environment variables.
Possible solutions
==================
In order to run Docker containers that can execute ROS, we have several possibilities:
1) Mount a tmpfs volume on the default ROS home folder
2) Make either the `/tmp` or `/var` volumes bigger and point `ROS_HOME` in a subfolder in them
3) Add a new tmpfs volume in a separated known folder and point `ROS_HOME` to it
`ROS_HOME` can either be hardcoded during the image creation process or dynamically set when running the container.
Main questions
==============
For solution 1, from where should the information about the size of the target folder come from as well as the target location ?
For solution 2, `ROS_HOME` can be hardcoded as part of the image creation
For solution 3, same questions as for solution 1 with the possibility of hardcoding the environment variable as in solution 2.
André Anjos
André Anjos
https://gitlab.idiap.ch/beat/beat.core/-/issues/107
Error on docker client creation
2021-04-13T12:14:32Z
Samuel GAIST
Error on docker client creation
At least on macOS when the daemon is not running, the client creation may fail and thus lead to an exception.
This is a case that is not yet handled like the others that follows when looking up for images.
Related to beat/beat.editor#282
At least on macOS when the daemon is not running, the client creation may fail and thus lead to an exception.
This is a case that is not yet handled like the others that follows when looking up for images.
Related to beat/beat.editor#282
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/112
NPM registry slowdown causing 404s in CI
2018-05-22T09:52:46Z
Jaden DIEFENBAUGH
NPM registry slowdown causing 404s in CI
See https://status.npmjs.org/
Currently the registry is slow enough to give 404s for this one package, `@babel/code-frame`.
They're trying to fix it so hopefully it'll be up soon...because without it, we can't run the CI.
See https://status.npmjs.org/
Currently the registry is slow enough to give 404s for this one package, `@babel/code-frame`.
They're trying to fix it so hopefully it'll be up soon...because without it, we can't run the CI.
https://gitlab.idiap.ch/beat/beat.editor/-/issues/137
Move the `beateditor` command to beat.cmdline's Click framework
2018-09-05T06:41:52Z
Jaden DIEFENBAUGH
Move the `beateditor` command to beat.cmdline's Click framework
Add another command to `beat.cmdline` via the click framework, moving:
```
$ beateditor
```
to:
```
$ beat editor
```
Add another command to `beat.cmdline` via the click framework, moving:
```
$ beateditor
```
to:
```
$ beat editor
```
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/138
Can we use Conda's Node.js version?
2019-01-28T04:37:00Z
Jaden DIEFENBAUGH
Can 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.
https://gitlab.idiap.ch/beat/beat.editor/-/issues/139
Add Jinja2 template for plotter editor
2018-10-02T12:13:23Z
Jaden DIEFENBAUGH
Add Jinja2 template for plotter editor
Turns out, the plotter editor doesn't have a template file!
@flavio.tarsetti this would be a great intro issue to see & work with the whole system
Turns out, the plotter editor doesn't have a template file!
@flavio.tarsetti this would be a great intro issue to see & work with the whole system
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/141
[branch] cross-tab-sync pending branch still alive ?
2018-08-07T17:55:21Z
Flavio TARSETTI
[branch] cross-tab-sync pending branch still alive ?
@jdiefenbaugh I see this dangling branch "cross-tab-sync" you have created months ago - seems quite old, but you added some commits in there. (maybe some important commits)
What do we need to do with this one ? Could you have a check an...
@jdiefenbaugh I see this dangling branch "cross-tab-sync" you have created months ago - seems quite old, but you added some commits in there. (maybe some important commits)
What do we need to do with this one ? Could you have a check and let me know ? Thanks
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/146
The page refreshes everytime I try to change the name of a block in a toolchain
2018-08-22T06:50:08Z
Zohreh MOSTAANI
The page refreshes everytime I try to change the name of a block in a toolchain
I am trying to make a new toolchain. When I want to change the name of the block the small box for adjusting the inputs and outputs of block refreshes. It closes and opens again in a split second. It happens only when changing the name o...
I am trying to make a new toolchain. When I want to change the name of the block the small box for adjusting the inputs and outputs of block refreshes. It closes and opens again in a split second. It happens only when changing the name of the block but not when changing the inputs and outputs name and it happens by writing or deleting each letter. Very annoying! I would really appreciate if you could give a temporary solution to me if it will take time to fix this issue. Please let me know if you need any information.
https://gitlab.idiap.ch/beat/beat.editor/-/issues/147
database name does not check validity if the name is not matching the pattern...
2018-08-24T22:52:16Z
Zohreh MOSTAANI
database name does not check validity if the name is not matching the pattern rule
I made a new database with name "replay-me" and it was valid. I assumed that if the name has a problem the editor will tell me. So I made an experiment using this database and it was invalid no matter what I did. Finally I ran the invali...
I made a new database with name "replay-me" and it was valid. I assumed that if the name has a problem the editor will tell me. So I made an experiment using this database and it was invalid no matter what I did. Finally I ran the invalid experiment and I get:
```
Failed to load the experiment `zmostaani/zmostaani/sbhatta-iqm-face-antispoofing-test/2/newantispoofing':
* /datasets/dev_probes/database: 'replay-me/1' does not match '^[a-zA-Z_][a-zA-Z0-9_]*/[0-9]+$' (rule: /properties/datasets/patternProperties/^[a-zA-Z_][a-zA-Z0-9_-]*$/properties/database/
pattern)
* /datasets/test_probes/database: 'replay-me/1' does not match '^[a-zA-Z_][a-zA-Z0-9_]*/[0-9]+$' (rule: /properties/datasets/patternProperties/^[a-zA-Z_][a-zA-Z0-9_-]*$/properties/database
/pattern)
* /datasets/train/database: 'replay-me/1' does not match '^[a-zA-Z_][a-zA-Z0-9_]*/[0-9]+$' (rule: /properties/datasets/patternProperties/^[a-zA-Z_][a-zA-Z0-9_-]*$/properties/database/patte
rn)
Error: Error occured
```
I changed the name of the database to "replayme" and the experiment was valid afterwards. I think these patterns should be considered when checking the name chosen for the database.