beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-08-21T12:59:20Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/500Create docker environment with GPU support2018-08-21T12:59:20ZSamuel GAISTCreate docker environment with GPU supportCreate an environment that provides a GPU enabled python environment.
To get started, support for Pytorch is planned.Create an environment that provides a GPU enabled python environment.
To get started, support for Pytorch is planned.GPU backendSamuel GAISTSamuel GAIST2018-08-31https://gitlab.idiap.ch/beat/beat.web/-/issues/499Request GPU enabled virtual machine2018-08-21T12:54:09ZSamuel GAISTRequest GPU enabled virtual machineRequest hardware with GPU capabilitiesRequest hardware with GPU capabilitiesGPU backendSamuel GAISTSamuel GAIST2018-07-26https://gitlab.idiap.ch/beat/beat.editor/-/issues/146The page refreshes everytime I try to change the name of a block in a toolchain2018-08-22T06:50:08ZZohreh MOSTAANIThe page refreshes everytime I try to change the name of a block in a toolchainI 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/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.editor/-/issues/144fix connection line ids prepending '#' to id name2018-12-19T19:02:44ZJaden DIEFENBAUGHfix connection line ids prepending '#' to id nameObviously my wires crossed at some point - the `line`s in `ToolchainConnections` have ids that start with '#', making it very hard to select a line by id:
```js
document.querySelector('#\\#training_data-measurements-training_alg-measurem...Obviously my wires crossed at some point - the `line`s in `ToolchainConnections` have ids that start with '#', making it very hard to select a line by id:
```js
document.querySelector('#\\#training_data-measurements-training_alg-measurements');
```
Woops!Toolchain Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/143The connection in the toolchain is not being updated properly2018-12-19T19:02:44ZZohreh MOSTAANIThe connection in the toolchain is not being updated properlyI made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then...I made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then I used my toolchain in an experiment but it was not working. It said that the toolchain is not valid because certain connections are wrong. Looking at the json file of the toolchain, it turned out that the correct connections are added to the list of connections without the previous wrong ones being removed from them and therefore the error. I must say that in the beat editor gui everything seemed correct and valid.Toolchain Editor: FixesJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/44The connection in the toolchain is not being updated properly2018-08-08T14:39:24ZZohreh MOSTAANIThe connection in the toolchain is not being updated properlyI made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then...I made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then I used my toolchain in an experiment but it was not working. It said that the toolchain is not valid because certain connections are wrong. Looking at the json file of the toolchain, it turned out that the correct connections are added to the list of connections without the previous wrong ones being removed from them and therefore the error. I must say that in the beat editor gui everything seemed correct and valid.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/43cache should be cleared to run new experiments even if the changes are in the...2018-08-18T04:34:25ZZohreh MOSTAANIcache should be cleared to run new experiments even if the changes are in the database block.from What I understood from the documentation of beat.editor about cache system, it seems that if you change something in a block, beat should rerun that block and all the blocks depending on it. But it is not the case.
I changed the ro...from What I understood from the documentation of beat.editor about cache system, it seems that if you change something in a block, beat should rerun that block and all the blocks depending on it. But it is not the case.
I changed the root folder for the database atnt/5 in the prefix given in beat.tutorial.prefix to run the experiment test/tutorial/eigenface/1/atnt , but I had to clear the cache, otherwise it would still point to the wrong address for the database, even-though the json file was updated immediately.https://gitlab.idiap.ch/beat/beat.editor/-/issues/142cannot unassign an algorithm to a block in the experiment.2018-12-19T19:02:44ZZohreh MOSTAANIcannot unassign an algorithm to a block in the experiment.After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem ...After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem in the toolchain and you want to find out where the problem is it would be a good option to unassign an algorithm without deleting the whole block.Experiment Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/42cannot unassign an algorithm to a block in the experiment.2018-08-07T14:18:05ZZohreh MOSTAANIcannot unassign an algorithm to a block in the experiment.After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem ...After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem in the toolchain and you want to find out where the problem is it would be a good option to unassign an algorithm without deleting the whole block.https://gitlab.idiap.ch/beat/beat.editor/-/issues/141[branch] cross-tab-sync pending branch still alive ?2018-08-07T17:55:21ZFlavio 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 ? ThanksJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/41the plot function does not work properly2018-08-10T09:52:54ZZohreh MOSTAANIthe plot function does not work properlyI am following the documentation on beat.editor (https://www.idiap.ch/software/beat/docs/beat/docs/master/beat.editor/doc/user.html). I have a working conda environment with all the necessary packages and python 3.6 installed. I could ru...I am following the documentation on beat.editor (https://www.idiap.ch/software/beat/docs/beat/docs/master/beat.editor/doc/user.html). I have a working conda environment with all the necessary packages and python 3.6 installed. I could run the experiment in the tutorial but when I wanted to plot the results I got the following error. Any idea what might be the problem? Thanks.
`beat exp plot --show test/test/iris/1/iris`
`Traceback (most recent call last):
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/bin/beat", line 11, in <module>
sys.exit(main())
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 535, in invoke
return callback(*args, **kwargs)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/decorators.py", line 17, in new_func
return f(get_current_context(), *args, **kwargs)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/cmdline/decorators.py", line 75, in _decorator
value = view_func(*args, **kwargs)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/cmdline/experiments.py", line 783, in plot
output_folder
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/cmdline/experiments.py", line 496, in plot_impl
experiments = pull(webapi, configuration.path, [name], force, indentation, format_cache)
File "/idiap/temp/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/click/core.py", line 722, in __call__
return self.main(*args, **kwargs)
TypeError: main() takes from 1 to 5 positional arguments but 7 were given`Flavio TARSETTIFlavio TARSETTIhttps://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/139Add Jinja2 template for plotter editor2018-10-02T12:13:23ZJaden DIEFENBAUGHAdd Jinja2 template for plotter editorTurns 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 systemTurns 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 systemFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/docs/-/issues/6[documentation - day] Proposition2018-12-17T20:55:16ZFlavio TARSETTI[documentation - day] Proposition**List of all the packages on gitlab concerning beat :**
```
beat.tutorial
beat.examples
beat.env.python27
beat.core
beat.deploy
beat.env.web
beat.web
beat.env.develop
beat.cmdline
beat.backend.python
beat.env.backend
beat.env.docker
be...**List of all the packages on gitlab concerning beat :**
```
beat.tutorial
beat.examples
beat.env.python27
beat.core
beat.deploy
beat.env.web
beat.web
beat.env.develop
beat.cmdline
beat.backend.python
beat.env.backend
beat.env.docker
beat.backend.cxx
beat.env.scripts
beat.env.python
beat.env.system.python
beat.env.cxx
beat.env.client
beat.env.db.examples
beat.env.db
beat.env.rankone
beat.editor
weeklies
beat.presentation.technical
ci.env.editor
beat.tutorial.prefix
docs
beat.env.pytorch
```
**List of packages in the aggregated documentation**
```
beat.cmdline
beat.core
beat.backend.python
beat.web
beat.editor
```
From which:
* `beat.core` documentation on _beat.core components_. It's a `User Guide`
* `beat.cmdline` documentation on command-line client. It's a `User Guide`
* `beat.backend.python` documentation on various API aspects. It's an `API Guide`
* `beat.editor` documentation on how to edit _beat objects_. It has an `Installation Guide` and `User Guide` with an additional breakdown on how to edit each objects, and also a `Development Guide`, a possible `API Guide` for the Flask server
* `beat.web` documentation on the platform's architecture. It has an `Administrator Guide` and also an `API Guide` and finally the platform `User Guide`
**Miscellaneous information**
* The information about `how to write algorithms` targets what is now `legacy` and is `not v2 compatible` #5
**Proposition**
* Let's target "ONLY" for now the list of packages from the aggregated documentation (beat.core, beat.cmdline, beat.backend.python, beat.editor, beat.web) with an upper package `beat` which would pin all those packages at a specific version for a proper release.
* We could imagine having a consistent track for each of these packages (I am not sure to what extend this makes sense as beat.cmdline for example doesn't have an API Guide or Development Guide):
* Installation Guide
* User Guide
* API Guide (When required)
* Administrator/Development Guide
**Open questions**
* I was previously in favor of having a `User Guide` for all the packages then an `API Guide` for all of them again, etc. etc. but to what I see this would seem confusing. I would keep the proposition above and we should write more documentation (such as a Development Guide) for all the packages and we should spend time writing a `beat.tutorial` documentation which would regroup all the User Guide of `beat.web`, `beat.cmdline` and `beat.editor` only. Does this make sense ?https://gitlab.idiap.ch/beat/docs/-/issues/5[beat.web] documentation on algorithm2018-12-17T21:50:13ZFlavio TARSETTI[beat.web] documentation on algorithm@andre.anjos:
I think this answers the question:
[8._Algorithms___beat_2018.06.pdf](/uploads/c82a54740e60b9089bb1d5f1f74f9c3e/8._Algorithms___beat_2018.06.pdf)
Please see attached file.
So do we have documentation on how to write algo...@andre.anjos:
I think this answers the question:
[8._Algorithms___beat_2018.06.pdf](/uploads/c82a54740e60b9089bb1d5f1f74f9c3e/8._Algorithms___beat_2018.06.pdf)
Please see attached file.
So do we have documentation on how to write algorithms on beat.web (1.4 branch) ?
From my point of view the answer is yes. Do we agree ?
If yes we can close this issue.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.https://gitlab.idiap.ch/beat/beat.editor/-/issues/137Move the `beateditor` command to beat.cmdline's Click framework2018-09-05T06:41:52ZJaden DIEFENBAUGHMove the `beateditor` command to beat.cmdline's Click frameworkAdd 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 TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/40`list` commands have a default verbosity level above 12018-12-12T09:14:12ZJaden DIEFENBAUGH`list` commands have a default verbosity level above 1I recently updated `beat.cmdline` for writing the documentation examples and it seems that the verbosity level isn't `0` by default. Running `beat exp list` for the `beat.tutorial.prefix` prefix gives me:
```
Loaded configuration file `/...I recently updated `beat.cmdline` for writing the documentation examples and it seems that the verbosity level isn't `0` by default. Running `beat exp list` for the `beat.tutorial.prefix` prefix gives me:
```
Loaded configuration file `/home/jae/.beatrc'
anjos/tutorial/eigenface/1/atnt-eigenfaces-172
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: anjos/tutorial/eigenface/1/atnt-eigenfaces-172
test/tutorial/eigenface/1/atnt
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: test/tutorial/eigenface/1/atnt
test/test/iris_advanced/1/iris
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: test/test/iris_advanced/1/iris
test/test/iris/1/iris
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: test/test/iris/1/iris
test/test/iris/1/error
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: test/test/iris/1/error
test/test/iris/1/means
[05/Jul/2018 15:25:21 - beat.cmdline.common] INFO: test/test/iris/1/means
```
This isn't the correct functionality, right?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/docs/-/issues/4[beat.web] issue when adding the package to the docs2018-07-06T12:40:18ZFlavio TARSETTI[beat.web] issue when adding the package to the docsI am adding beat.web to the docs, I cloned it but after running:
```
../bob.admin/conda/conda-build.sh --python=3 conda
```
I get this error:
`
(14:38:03.372) Error: Command Failed "conda build --no-anaconda-upload --variant-config-fil...I am adding beat.web to the docs, I cloned it but after running:
```
../bob.admin/conda/conda-build.sh --python=3 conda
```
I get this error:
`
(14:38:03.372) Error: Command Failed "conda build --no-anaconda-upload --variant-config-files /home/neo/bob.admin/conda/../gitlab/conda_build_config.yaml --python=3 conda"
`
any idea on this one @samuel.gaist and @andre.anjos ?