beat.cmdline issueshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues2018-05-14T12:20:39Zhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/13Support Python 3.x2018-05-14T12:20:39ZJaden DIEFENBAUGHSupport Python 3.xRight now buildout with python 3.x gives an error when using the `beat`.Right now buildout with python 3.x gives an error when using the `beat`.Gitlab CI Integrationhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/15local execution not working anymore2018-10-15T13:32:30ZJaden DIEFENBAUGHlocal execution not working anymoreNo experiments work anymore. The first block to be processed always throws the same error:
```
Running `user/integers_add/1' for block `echo'
Start the execution of 'user/integers_add/1'
Block did not execute properly - outputs were rese...No experiments work anymore. The first block to be processed always throws the same error:
```
Running `user/integers_add/1' for block `echo'
Start the execution of 'user/integers_add/1'
Block did not execute properly - outputs were reset
Standard output:
Standard error:
Captured user error:
File "/home/jae/code/beat.cmdline/src/beat.backend.python/beat/backend/python/loader.py", line 100, in run
return getattr(obj, method)(*args, **kwargs)
RuntimeError: done() takes exactly 1 argument (2 given)
Captured system error:
```
For reference - I'm using Python 2.7 via a conda environment. All packages are updated, and bob is properly installed. I used this env's python to bootstrap the buildout of `beat.cmdline`. The nosetests pass fine.Zohreh MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/16Add experiment results plot generation command2018-05-15T13:54:56ZJaden DIEFENBAUGHAdd experiment results plot generation commandI don't see a way to generate~visualize results from successfully-ran experiments outside of pushing the experiment to a `beat.web` installation. This feature seems practically necessary for a easy development cycle.
Maybe add a sub-com...I don't see a way to generate~visualize results from successfully-ran experiments outside of pushing the experiment to a `beat.web` installation. This feature seems practically necessary for a easy development cycle.
Maybe add a sub-command to the experiments or plotters command groups?Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/19Fetch environment data from beat.web instances2018-04-13T12:39:53ZJaden DIEFENBAUGHFetch environment data from beat.web instances...using the `/api/v1/backend/environments/` endpoint.
Not sure how this would be stored...probably just dump the JSON in an `environments.json` file in the `.beat` user folder.
Needed for the June 2018 release!...using the `/api/v1/backend/environments/` endpoint.
Not sure how this would be stored...probably just dump the JSON in an `environments.json` file in the `.beat` user folder.
Needed for the June 2018 release!https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/20Format for storing plotterparameters in prefix2018-05-15T13:54:13ZJaden DIEFENBAUGHFormat for storing plotterparameters in prefix@flavio.tarsetti how does the system associate plotters & plotterparameters?
The names aren't associated, as the plotterparameter `plot/det_40x40/1` isn't a similar name to `plot/isoroc/1`. And the plotterparameter content is:
```json
...@flavio.tarsetti how does the system associate plotters & plotterparameters?
The names aren't associated, as the plotterparameter `plot/det_40x40/1` isn't a similar name to `plot/isoroc/1`. And the plotterparameter content is:
```json
{
"grid": true,
"title": "DET ISO/IEC 19795-1:2006",
"title-fontsize": 12,
"det": true,
"legend-loc": "best",
"width": 800,
"height": 600,
"dpi": 120,
"legend-fontsize": 8,
"xlim-left": 0,
"xlim-right": 40,
"ylim-bottom": 0,
"ylim-top": 40,
"axis-fontsize": 10
}
```
How do we associate them?https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/21Add local environment querying support2018-05-15T13:53:51ZJaden DIEFENBAUGHAdd local environment querying support(This is the first part of beat.editor#77)
Right now `beat.core` can tell us about the available local environments available (see [`dock.py`](https://gitlab.idiap.ch/beat/beat.core/blob/a8871304860b9e7c87f3b7ec08c0b308ccd0908a/beat/cor...(This is the first part of beat.editor#77)
Right now `beat.core` can tell us about the available local environments available (see [`dock.py`](https://gitlab.idiap.ch/beat/beat.core/blob/a8871304860b9e7c87f3b7ec08c0b308ccd0908a/beat/core/dock.py#L149)). The goal is to give `beat.editor` access to this info, which means that `beat.cmdline` needs a nice way to supply this info.
I'd add a new beat sub-app, `environment` (with an `env` shortcut) with a `list` command that would give the necessary info. Ideally the environment info would be provided in some machine-parseable format and provide at least:
- environment names & versions
- queues for each environment along with their slot counts
- the environments' packages (names & versions)
Right now I'm thinking to just use JSON of the same format as the beat.web endpoint for environments. [BEAT staging example](http://beatweb-staging.lab.idiap.ch:80/api/v1/backend/environments/):
```json
[
{
"name": "Scientific Python 2.7",
"queues": {
"Default": {
"memory_limit": 5983,
"nb_slots": 2,
"max_slots_per_user": 2,
"nb_cores_per_slot": 1,
"time_limit": 360
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "0.0.4",
"short_description": "Scientific Python 2.7"
},
{
"name": "Scientific Python 2.7",
"queues": {
"Default": {
"memory_limit": 5983,
"nb_slots": 2,
"max_slots_per_user": 2,
"nb_cores_per_slot": 1,
"time_limit": 360
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "1.0.0",
"short_description": "Scientific Python 2.7"
}
]
```
The one thing missing is the package info. There would be a `"packages"` field added to each environment that points to a dict consisting of package names for keys and versions for values:
```json
[
{
"name": "Scientific Python 2.7",
"packages": {
"alabaster": "0.7.6",
"babel": "1.3",
...
},
"queues": {
"Default": {
"memory_limit": 5983,
"nb_slots": 2,
"max_slots_per_user": 2,
"nb_cores_per_slot": 1,
"time_limit": 360
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "0.0.4",
"short_description": "Scientific Python 2.7"
},
{
"name": "Scientific Python 2.7",
"packages": {
"alabaster": "0.7.10",
"Babel": "2.4.0",
...
},
"queues": {
"Default": {
"memory_limit": 5983,
"nb_slots": 2,
"max_slots_per_user": 2,
"nb_cores_per_slot": 1,
"time_limit": 360
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "1.0.0",
"short_description": "Scientific Python 2.7"
}
]
```
This is the same extension proposed in beat.web#495.Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/8[databases] Indexing is broken2018-04-13T08:03:56ZAndré Anjos[databases] Indexing is brokenNot all outputs are being properly indexed. To be checked ASAP.Not all outputs are being properly indexed. To be checked ASAP.Final DocumentationAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/9Un-reproducible bug -- invalid state file at `./.beat/config.json'2018-05-04T10:42:24ZTeodors EGLITISUn-reproducible bug -- invalid state file at `./.beat/config.json'I randomly get this warning:
```
WARNING: invalid state file at `./.beat/config.json' - removing and re-starting...
```
Warning is displayed (and the configuration is reset) randomly after one of these commands:
```
$ ./bin/beat config s...I randomly get this warning:
```
WARNING: invalid state file at `./.beat/config.json' - removing and re-starting...
```
Warning is displayed (and the configuration is reset) randomly after one of these commands:
```
$ ./bin/beat config set platform "http://127.0.0.1:8000/"
$ ./bin/beat config set user "user" token "3"
$ ./bin/beat config set cache "/idiap/temp/teglitis/BEAT-cache/"
$ ./bin/beat config color dark
$ ./bin/beat config list
$ ./bin/beat experiments push teodors/teodors/vein_recognition_only_dev/1/putvein-muira-only-dev-100
```
It seams that warnings aren't raised if the config is modified using single command:
```
$ ./bin/beat config set user "user" token "3" platform "http://127.0.0.1:8000/" cache "/idiap/temp/teglitis/BEAT-cache/"
```
But still this seams to me as a bug.
Teohttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/7[experiments] Add command to checksum data and indexes2018-04-13T08:03:56ZAndré Anjos[experiments] Add command to checksum data and indexesOn ``xp caches``.On ``xp caches``.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/6Pulling a database fails with a token error2018-04-13T08:03:56ZLaurent EL SHAFEYPulling a database fails with a token errorIt's seems that a regular user can't pull databases anymore.
```
$ ./bin/beat --prefix=prefix db pull
retrieving `databases/atnt/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: ...It's seems that a regular user can't pull databases anymore.
```
$ ./bin/beat --prefix=prefix db pull
retrieving `databases/atnt/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/banca/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/casme2/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/cbsr_nir_vis_2/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/cpqd/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/mnist/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/mobio/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/replay/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/utfvp/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/voxforge/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
retrieving `databases/xm2vts/1'...
failed to retrieve database from `https://www.beat-eu.org/platform/' with secret token, reason: Forbidden
```
This also occurs when pulling an experiment, which will try to pull the database used.BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/5Database view is not working properly2018-04-13T08:03:56ZLaurent EL SHAFEYDatabase view is not working properlyWhen trying to view a dataset,
```
./bin/beat --prefix web_dynamic_data db view banca/1/Mc/dev_probes
```
I sometimes get this kind of errors:
```
Traceback (most recent call last):
File "./bin/beat", line 33, in <module>
...When trying to view a dataset,
```
./bin/beat --prefix web_dynamic_data db view banca/1/Mc/dev_probes
```
I sometimes get this kind of errors:
```
Traceback (most recent call last):
File "./bin/beat", line 33, in <module>
sys.exit(beat.cmdline.scripts.beat.main())
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/scripts/beat.py", line 160, in main
return module.process(args)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 402, in process
return view_output(args['config'], args['<set_name>'])
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 355, in view_output
json_data[name] = common.stringify(value)
TypeError: 'str' object does not support item assignment
```
BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/4Pulling an experiment does not pull any experiment but only related toolchain...2018-04-13T08:03:56ZLaurent EL SHAFEYPulling an experiment does not pull any experiment but only related toolchains/dataformats/algorithmsThis looks like API-change related.This looks like API-change related.BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/3Data (algorithms, dataformats, etc.) pulling crashes when non-ascii character...2018-04-13T08:03:57ZLaurent EL SHAFEYData (algorithms, dataformats, etc.) pulling crashes when non-ascii characters are present in a fieldHere is an example:
```bash
lelshafey@futurix08:/idiap/user/lelshafey/work/beat_platform/beat.cmdline$ ./bin/beat algo pull
retrieving `algorithms/siebenkopf/GaborGraphSimilarity/12'...
Traceback (most recent call last):
File "....Here is an example:
```bash
lelshafey@futurix08:/idiap/user/lelshafey/work/beat_platform/beat.cmdline$ ./bin/beat algo pull
retrieving `algorithms/siebenkopf/GaborGraphSimilarity/12'...
Traceback (most recent call last):
File "./bin/beat", line 21, in <module>
sys.exit(beat.cmdline.scripts.beat.main())
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/beat/cmdline/scripts/beat.py", line 160, in main
return module.process(args)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/beat/cmdline/algorithms.py", line 144, in process
args['--force'], 0, {}, {})
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/beat/cmdline/algorithms.py", line 105, in pull
['declaration', 'code', 'description'], force, indentation)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/beat/cmdline/common.py", line 612, in pull
storage.save(**data)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/src/beat.core/beat/core/utils.py", line 262, in save
if description: self.doc.save(description)
File "/remote/idiap.svm/user.active/lelshafey/work/beat_platform/beat.cmdline/src/beat.core/beat/core/utils.py", line 129, in save
with open(self.path, mode) as f: f.write(contents)
UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 622: ordinal not in range(128)
```
This may be a problem with beat.core.BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/2Data (algorithms, dataformats, etc.) listing and pulling is not working any more2018-04-13T08:03:57ZLaurent EL SHAFEYData (algorithms, dataformats, etc.) listing and pulling is not working any moreData (algorithms, dataformats, etc.) listing and pulling is not working any more. The corresponding tests are failing as well.Data (algorithms, dataformats, etc.) listing and pulling is not working any more. The corresponding tests are failing as well.BTAS TutorialLaurent EL SHAFEYLaurent EL SHAFEYhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/1Database indexing and database view are not working anymore2018-04-13T08:03:57ZTiago de Freitas PereiraDatabase indexing and database view are not working anymoreWhen running the `beat` command line utility to perform one of the following operations (indexing or viewing database content), the script crashes with such an error:
```python
./bin/beat --prefix=work db view atnt/1/idiap/train
Tra...When running the `beat` command line utility to perform one of the following operations (indexing or viewing database content), the script crashes with such an error:
```python
./bin/beat --prefix=work db view atnt/1/idiap/train
Traceback (most recent call last):
File "./bin/beat", line 34, in <module>
sys.exit(beat.cmdline.scripts.beat.main())
File "/remote/idiap.svm/user.active/tpereira/BEAT/beat.core/src/beat.cmdline/beat/cmdline/scripts/beat.py", line 160, in main
return module.process(args)
File "/remote/idiap.svm/user.active/tpereira/BEAT/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 400, in process
return view_output(args['config'], args['<set_name>'])
File "/remote/idiap.svm/user.active/tpereira/BEAT/beat.core/src/beat.cmdline/beat/cmdline/databases.py", line 330, in view_output
input_group = view.input_group(exclude_outputs=excluded_outputs)
File "/remote/idiap.svm/user.active/tpereira/BEAT/beat.core/beat/core/database.py", line 146, in input_group
for output in self.outputs:
TypeError: 'NoneType' object is not iterable
```BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/22[CI] issue with docker and zc.buildout2018-04-19T14:08:51ZFlavio TARSETTI[CI] issue with docker and zc.buildoutSeems like the CI is having a strange issue with docker and and zc.buildout (apparently):
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/132525
No hurry @samuel.gaist, it's not blocking for me at the moment, it was just to raise your...Seems like the CI is having a strange issue with docker and and zc.buildout (apparently):
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/132525
No hurry @samuel.gaist, it's not blocking for me at the moment, it was just to raise your attention on this.
Thanks,
Flaviohttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/24Store prefix on configuration file2018-12-12T09:14:17ZAndré AnjosStore prefix on configuration fileIt would be nice to be able to store the prefix on the configuration file.It would be nice to be able to store the prefix on the configuration file.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/26[config] set2018-05-05T22:52:16ZFlavio TARSETTI[config] set@andre.anjos @jdiefenbaugh @samuel.gaist
There's a bug with the config set [options]
it systematically adds a "}" at the end of the local config file or sometimes a new user: "user"} line.
And it breaks everything afterwards.
Needs t...@andre.anjos @jdiefenbaugh @samuel.gaist
There's a bug with the config set [options]
it systematically adds a "}" at the end of the local config file or sometimes a new user: "user"} line.
And it breaks everything afterwards.
Needs to be checked.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/28Local plotting doesn't work2018-05-16T15:43:50ZJaden DIEFENBAUGHLocal plotting doesn't workDidn't have time to try the new plotting code until now...and plotting local experiments doesn't work.
I try to plot an experiment (`beat exp plot test/tutorial/eigenface/1/atnt`) and I get this:
```
retrieving `plotters/plotterparamete...Didn't have time to try the new plotting code until now...and plotting local experiments doesn't work.
I try to plot an experiment (`beat exp plot test/tutorial/eigenface/1/atnt`) and I get this:
```
retrieving `plotters/plotterparameters/plot/isoroc/1'...
findfont: Found a missing font file. Rebuilding cache.
font search path ['/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/matplotlib/mpl-data/fonts/ttf', '/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/matplotlib/mpl-data/fonts/afm', '/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/matplotlib/mpl-data/fonts/pdfcorefonts']
Could not open font file /usr/share/fonts/noto/NotoColorEmoji.ttf
generated new fontManager
Traceback (most recent call last):
File "/home/jae/miniconda3/envs/beat/bin/beat", line 11, in <module>
sys.exit(main())
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/cmdline/scripts/beat.py", line 183, in main
return module.process(args)
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/cmdline/experiments.py", line 620, in process
force, 0, {}, args['--outputfolder'])
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/cmdline/experiments.py", line 550, in plot
data.as_dict()[the_data], output_name, None, indentation + 2, format_cache)
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/cmdline/plotters.py", line 257, in plot
fig = runnable.process(data_to_plot)
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/core/plotter.py", line 95, in process
return loader.run(self.obj, 'process', self.exc, inputs)
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/beat/backend/python/loader.py", line 109, in run
return getattr(obj, method)(*args, **kwargs)
File "/home/jae/code/beat.editor/prefix/plotters/plot/isoroc/1.py", line 143, in process
return super(Plotter, self).encode_figure(fig)
File "/home/jae/code/beat.editor/prefix/libraries/plot/baselib/1.py", line 85, in encode_figure
if self.content_type.endswith('png'): canvas.print_png(sio)
File "/home/jae/miniconda3/envs/beat/lib/python3.6/site-packages/matplotlib/backends/backend_agg.py", line 528, in print_png
self.figure.dpi, metadata=metadata)
TypeError: string argument expected, got 'bytes'
```
Maybe the `plot/baselib/1` library should be updated?https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/29Provide a plugin-based command line mechanism2020-07-21T14:02:10ZAmir MOHAMMADIProvide a plugin-based command line mechanismWhile the `beat` commandline is nice, @andre.anjos pointed out that a plugin-based commandline would be more useful.
I could not find an issue for this, so I'm creating this but feel free to close it if it is not relevant.
This was care...While the `beat` commandline is nice, @andre.anjos pointed out that a plugin-based commandline would be more useful.
I could not find an issue for this, so I'm creating this but feel free to close it if it is not relevant.
This was carefully designed and implemented in bob:
* https://gitlab.idiap.ch/bob/bob.extension/issues/44
* https://gitlab.idiap.ch/bob/bob.extension/merge_requests/64
* https://www.idiap.ch/software/bob/docs/bob/docs/master/bob.extension/doc/framework.html#unified-command-line-mechanism
A similar approach could be taken here as well.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/30[ci] issue with docker2018-05-10T12:13:54ZFlavio TARSETTI[ci] issue with dockerHi @andre.anjos ,
Do you see why docker is causing issues here ?
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/19968
ThanksHi @andre.anjos ,
Do you see why docker is causing issues here ?
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/19968
ThanksAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/31Edit command for all packages2018-10-15T07:53:54ZFlavio TARSETTIEdit command for all packagesAdding the edit command for all packages.
This is related to the discussion here https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/29Adding the edit command for all packages.
This is related to the discussion here https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/29Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/32Plots from different experiments using the same username, toolchain, and anal...2018-05-25T08:12:13ZJaden DIEFENBAUGHPlots from different experiments using the same username, toolchain, and analyzer output names overwrite eachotherSay there are two experiments, `test/test/iris/1/iris` and `test/test/iris/1/means`. The experiment metadata for each of these experiments will be found in the same folder, `test/test/iris/1`. Say that these experiments use the same anal...Say there are two experiments, `test/test/iris/1/iris` and `test/test/iris/1/means`. The experiment metadata for each of these experiments will be found in the same folder, `test/test/iris/1`. Say that these experiments use the same analyzer as well.
If you plot these experiments , the last one to be plotted will overwrite the other experiment's plot files. This is because there is no per-experiment unique key added to the plot image file names - instead the file names are only based off of the output names in the analyzer.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/33`edit` command fails with "File does not exist"2018-05-28T14:56:24ZJaden DIEFENBAUGH`edit` command fails with "File does not exist"I wanted to update my slides to use the new `edit` subcommand, but trying to use `beat <entity> edit <name>` fails for everything I've tried.
I tried
```
beat exp edit test/test/iris/1/iris
```
and I get:
```
File does not exist: /hom...I wanted to update my slides to use the new `edit` subcommand, but trying to use `beat <entity> edit <name>` fails for everything I've tried.
I tried
```
beat exp edit test/test/iris/1/iris
```
and I get:
```
File does not exist: /home/jae/code/beat.editor/prefix/experiments/test/test/iris/1/iris.json
```
However, `cat`ing that absolute path works:
```
cat /home/jae/code/beat.editor/prefix/experiments/test/test/iris/1/iris.json
```
prints the file contents.
Same thing with `beat alg edit test/iris_analyzer/1`, giving:
```
File does not exist: /home/jae/code/beat.editor/prefix/algorithms/test/iris_analyzer/1.py
```
and `beat lib edit plot/baselib/1` giving:
```
File does not exist: /home/jae/code/beat.editor/prefix/libraries/plot/baselib/1.py
```
All of these files do actually exist and `cat`ing them using that given file path works.
@flavio.tarsetti @samuel.gaisthttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/34`beat caches view` doesn't work2018-12-12T09:14:17ZJaden DIEFENBAUGH`beat caches view` doesn't workI get the following:
```
path: e4/fb/dc/b2f4751a65179e51b472c4b8c1efbec86441e61194bc02442971ae3405
dataformat: tutorial/linear_machine/1
Traceback (most recent call last):
File "/home/jae/miniconda3/envs/beatedit/bin/beat", line 11, ...I get the following:
```
path: e4/fb/dc/b2f4751a65179e51b472c4b8c1efbec86441e61194bc02442971ae3405
dataformat: tutorial/linear_machine/1
Traceback (most recent call last):
File "/home/jae/miniconda3/envs/beatedit/bin/beat", line 11, in <module>
sys.exit(main())
File "/home/jae/miniconda3/envs/beatedit/lib/python3.6/site-packages/beat/cmdline/scripts/beat.py", line 186, in main
return module.process(args)
File "/home/jae/miniconda3/envs/beatedit/lib/python3.6/site-packages/beat/cmdline/cache.py", line 191, in process
return view(args['config'], args['<path>'], start, end)
File "/home/jae/miniconda3/envs/beatedit/lib/python3.6/site-packages/beat/cmdline/cache.py", line 164, in view
cls=NumpyJSONEncoder).\
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/__init__.py", line 397, in dumps
**kw).encode(obj)
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/encoder.py", line 293, in encode
chunks = list(chunks)
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/encoder.py", line 677, in _iterencode
for chunk in _iterencode_dict(o, _current_indent_level):
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/encoder.py", line 634, in _iterencode_dict
for chunk in chunks:
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/encoder.py", line 697, in _iterencode
o = _default(o)
File "/home/jae/miniconda3/envs/beatedit/lib/python3.6/site-packages/beat/backend/python/utils.py", line 354, in default
return simplejson.JSONEncoder.default(self, obj)
File "/home/jae/.local/lib/python3.6/site-packages/simplejson/encoder.py", line 268, in default
raise TypeError(repr(o) + " is not JSON serializable")
TypeError: <map object at 0x7f1b3d54a4e0> is not JSON serializable
```
This happens with any cache I've tried. Does it work for anyone?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/38Offline plotting support is shaky2020-05-26T15:19:19ZJaden DIEFENBAUGHOffline plotting support is shakyIf the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an inter...If the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an internet connection and couldn't plot because `beat.cmdline` was trying to fetch stuff from beat.web even though the plotter objects and default parameters existed.Samuel GAISTSamuel GAISThttps://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/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.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.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.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/45The script `beat.py` should be gone2018-08-27T15:37:08ZAndré AnjosThe script `beat.py` should be goneAfter replacing it by `main_cli.py`, I think this is now duplicated code which serves no purpose. @flavio.tarsetti, please check and make an MR which removes this file (https://gitlab.idiap.ch/beat/beat.cmdline/blob/1.4.x/beat/cmdline/sc...After replacing it by `main_cli.py`, I think this is now duplicated code which serves no purpose. @flavio.tarsetti, please check and make an MR which removes this file (https://gitlab.idiap.ch/beat/beat.cmdline/blob/1.4.x/beat/cmdline/scripts/beat.py).Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/47Change license to BSD 3-clause2019-03-13T14:44:15ZAndré AnjosChange license to BSD 3-clauseAs discussed in earlier weekly meetings (see action points from week02/2018 till week09/2018), the prospective re-use of BEAT core components to re-implement some Bob frameworks would require a shift in the licensing terms for some core ...As discussed in earlier weekly meetings (see action points from week02/2018 till week09/2018), the prospective re-use of BEAT core components to re-implement some Bob frameworks would require a shift in the licensing terms for some core BEAT packages.
@samuel.gaist: could you please do that *before* the release? The idea is to go from AGPLv3 to BSD 3-clause (as the rest of Bob) for all packages up to beat.cmdline. We exclude beat.web from this, leaving it as AGPLv3.
We should do the following, in details:
1. Remove the file `LICENSE.AGPL`
2. Create a new file called `LICENSE` the contains the stock BSD 3-clause text (see info here: https://gitlab.idiap.ch/bob/bob.admin/tree/master/templates)
3. Modify the file `MANIFEST.in` to include `LICENSE` instead of `LICENSE.AGPL`
4. Modify the file `setup.py` to list the license correctly on the classifier list (replace license key by `License :: OSI Approved :: BSD License`)
5. Modify the file `conda/meta.yaml` to set the license appropriately. Should read `license: BSD 3-Clause` and `license_family: BSD` on the `about` section, replacing the current AGPL stuff.
6. Double-check all headers from `.py` files - @flavio.tarsetti may have a script to do this.
Please consult with @philip.abbet since I think rechecked, by then, the feasibility of this move and found no issues against doing this.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/48[ci] issue merge request2018-10-15T06:35:52ZFlavio TARSETTI[ci] issue merge requestOn this pipeline:
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/24234
One of the job output:
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/150275
it fails all the time.
any idea why ? @zmostaani @samuel.gaist @andre.anjosOn this pipeline:
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/24234
One of the job output:
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/150275
it fails all the time.
any idea why ? @zmostaani @samuel.gaist @andre.anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/49The necessary blocks are not properly checked before pushing an experiment to...2019-10-23T18:29:09ZZohreh MOSTAANIThe necessary blocks are not properly checked before pushing an experiment to the platformI tried to push an experiment to the platform but it was giving the error that certain algorithms do not exist. I had to push each algorithm manually. Also the version number of the algorithm in my local system was 2 but when it was uplo...I tried to push an experiment to the platform but it was giving the error that certain algorithms do not exist. I had to push each algorithm manually. Also the version number of the algorithm in my local system was 2 but when it was uploaded to the platform it changed to one, therefore I got error again and I had to edit my local experiment to use version one so that I be able to upload the whole experiment.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/50Pushing experiments to the platform is very tricky without informative warnin...2019-10-23T18:29:10ZZohreh MOSTAANIPushing experiments to the platform is very tricky without informative warnings or errors!The assumption is that you can pull an experiment from the platform, edit the necessary blocks (which means debugging the blocks without going through the pain of making new versions or forks for each block) and then push back to the pla...The assumption is that you can pull an experiment from the platform, edit the necessary blocks (which means debugging the blocks without going through the pain of making new versions or forks for each block) and then push back to the platform.
The issue is that in each experiment the user can use toolchains, or algorithms, etc that are public from other users and when they are pulled they are organized in folders with similar usernames in the user's local prefix folder.
With current setup if users want to edit some algorithm they **should** first copy them to their own name space.
If you do not make new algorithms under your own name space two scenarios may happen:
- You just edited the file from original user (not a good idea). `beat push` command in this situation does not push anything since it already exists on the platform.
- you made new version form the same algorithm which goes under the category of the original user. `beat push` command will create a new algorithm with the same name under your username with version number one without any warnings and it shows on the command line that the algorithm under the original username has been created.
The problem is since there is no error or warnings in such situations and nothing mentioned in the documentation it is tricky to find out where the problem comes from. It might be very confusing for the normal user to interact with beat.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/52About Walkthrough section in the documentation.2018-12-06T09:50:13ZZohreh MOSTAANIAbout Walkthrough section in the documentation.I do not understand what is the purpose of the section Walkthrough in the documentation of beat.cmdline. Is it for developing the beat platform locally? Is it only for running the platform locally? Or is it for developing the beat.cmdlin...I do not understand what is the purpose of the section Walkthrough in the documentation of beat.cmdline. Is it for developing the beat platform locally? Is it only for running the platform locally? Or is it for developing the beat.cmdline itself? In the first line of this documentation it is written:
This page gives an overview on setting up an environment to develop BEAT **experiments** locally.https://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.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.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.cmdline/-/issues/58Add BEAT classifier to setup.py2019-04-11T08:58:40ZSamuel GAISTAdd BEAT classifier to setup.pyThe classifier has been added to Pypi so it now can be used.
See beat/beat.backend.python#19The classifier has been added to Pypi so it now can be used.
See beat/beat.backend.python#19https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/61Make Plotterparameter properly supported2019-05-08T08:54:29ZSamuel GAISTMake Plotterparameter properly supportedPlotterparameter also has a storage supporting it.
Update beat.cmdline to properly support it.Plotterparameter also has a storage supporting it.
Update beat.cmdline to properly support it.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/62Add support for remote experiments execution handling2019-09-16T17:30:12ZSamuel GAISTAdd support for remote experiments execution handlingCurrently, beat/beat.cmdline> only offers to run experiment locally.
This issue tracks the implementation of the commands needed to start, cancel and monitor a remote experiment.
The current monitoring implementation in beat/beat.web> ...Currently, beat/beat.cmdline> only offers to run experiment locally.
This issue tracks the implementation of the commands needed to start, cancel and monitor a remote experiment.
The current monitoring implementation in beat/beat.web> is based on a 5 second timer which, on timeout, will fetch the running experiment and, based on the content returned, update the information panel and toolchain representation.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/63LICENSE file location in conda recipe is wrong2019-11-14T15:59:01ZAndré AnjosLICENSE file location in conda recipe is wrongIt should read `LICENSE` instead of `../LICENSE`.
The same should be propagated to all relevant packages.
See: bob/bob.devtools#44It should read `LICENSE` instead of `../LICENSE`.
The same should be propagated to all relevant packages.
See: bob/bob.devtools#44Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/64Do not make the environment listing failed if platform is unavailable2020-01-29T13:16:11ZSamuel GAISTDo not make the environment listing failed if platform is unavailableAs implemented, the environment listing should not fail for local docker environment but it is currently not the case for listing the remote environment.
Both should behave the same. Therefore, if any error happens when contacting the p...As implemented, the environment listing should not fail for local docker environment but it is currently not the case for listing the remote environment.
Both should behave the same. Therefore, if any error happens when contacting the platform, it should be logged and the command continue showing an empty set of environment coming from there.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/65Improve dependency check tests2020-03-16T17:16:29ZFlavio TARSETTIImprove dependency check testsTests are missing.
Related to https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/86Tests are missing.
Related to https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/86Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/66Experiment monitor command is broken2020-03-18T12:07:14ZSamuel GAISTExperiment monitor command is brokenThe experiment monitor command does not work anymore following the cleanup of the webapi module.
The get is still handled old style.The experiment monitor command does not work anymore following the cleanup of the webapi module.
The get is still handled old style.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/67Version information missing on push2020-04-14T14:43:26ZSamuel GAISTVersion information missing on pushWhen creating a new version of an algorithm or a fork, the version information is not pushed with the data.
It is currently not used by beat/beat.web> but this is about to change because the current way new version creation is handled i...When creating a new version of an algorithm or a fork, the version information is not pushed with the data.
It is currently not used by beat/beat.web> but this is about to change because the current way new version creation is handled is suboptimal. If for some reasons a new version is created manually rather than through "beat <asset_type> version`, the missing history version will trigger the creation of a new "version 1" asset or at least an attempt to do that.
See beat/beat.web#547Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/70Cannot specify plotterparmeters when calling `beat exp plot`2020-07-28T14:57:58ZAmir MOHAMMADICannot specify plotterparmeters when calling `beat exp plot`I was thinking that we can fix this by providing the plotterparams using click optiona and also loading from rc.I was thinking that we can fix this by providing the plotterparams using click optiona and also loading from rc.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/71Make the experiment plotting less rigid2020-06-04T13:35:57ZSamuel GAISTMake the experiment plotting less rigidWith the old code and the part kept after the refactoring, the output format for the plotting the result of an experiment is locked to `image/png` if nothing is provided in the default plotter parameters.
This does not allow for people ...With the old code and the part kept after the refactoring, the output format for the plotting the result of an experiment is locked to `image/png` if nothing is provided in the default plotter parameters.
This does not allow for people to work on custom plotter that might output something else or use a different output type if nothing is provided as default parameter.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/73Cannot push a C++ algorithm2020-07-23T12:24:14ZAmir MOHAMMADICannot push a C++ algorithmLooks like when pushing a C++ algorithm, the code fails with:
```
lib/python3.7/site-packages/click/core.py(829)__call__()
828 """Alias for :meth:`main`."""
--> 829 return self.main(*args, **kwargs)
830
lib/...Looks like when pushing a C++ algorithm, the code fails with:
```
lib/python3.7/site-packages/click/core.py(829)__call__()
828 """Alias for :meth:`main`."""
--> 829 return self.main(*args, **kwargs)
830
lib/python3.7/site-packages/click/core.py(782)main()
781 with self.make_context(prog_name, args, **extra) as ctx:
--> 782 rv = self.invoke(ctx)
783 if not standalone_mode:
lib/python3.7/site-packages/click/core.py(1259)invoke()
1258 with sub_ctx:
-> 1259 return _process_result(sub_ctx.command.invoke(sub_ctx))
1260
lib/python3.7/site-packages/click/core.py(1259)invoke()
1258 with sub_ctx:
-> 1259 return _process_result(sub_ctx.command.invoke(sub_ctx))
1260
lib/python3.7/site-packages/beat/cmdline/click_helper.py(121)invoke()
119
120 ctx.meta["asset_info"] = self.asset_info
--> 121 return super().invoke(ctx)
lib/python3.7/site-packages/click/core.py(1066)invoke()
1065 if self.callback is not None:
-> 1066 return ctx.invoke(self.callback, **ctx.params)
1067
lib/python3.7/site-packages/click/core.py(610)invoke()
609 with ctx:
--> 610 return callback(*args, **kwargs)
611
lib/python3.7/site-packages/click/decorators.py(21)new_func()
20 def new_func(*args, **kwargs):
---> 21 return f(get_current_context(), *args, **kwargs)
22
lib/python3.7/site-packages/beat/cmdline/decorators.py(94)_decorator()
93 def _decorator(*args, **kwargs):
---> 94 value = view_func(*args, **kwargs)
95 if value not in [None, 0]:
lib/python3.7/site-packages/beat/cmdline/commands.py(321)push_impl()
320 dry_run=dry_run,
--> 321 indentation=0,
322 )
lib/python3.7/site-packages/beat/cmdline/common.py(1486)push()
1485 try:
-> 1486 webapi.post(url, data=message)
1487 except RuntimeError as e:
> lib/python3.7/site-packages/beat/cmdline/webapi.py(104)post()
103 url = self.__build_url(path)
--> 104 answer = requests.post(url, json=data, headers=self._make_headers())
105
lib/python3.7/site-packages/requests/api.py(119)post()
118
--> 119 return request('post', url, data=data, json=json, **kwargs)
120
lib/python3.7/site-packages/requests/api.py(61)request()
60 with sessions.Session() as session:
---> 61 return session.request(method=method, url=url, **kwargs)
62
lib/python3.7/site-packages/requests/sessions.py(516)request()
515 )
--> 516 prep = self.prepare_request(req)
517
lib/python3.7/site-packages/requests/sessions.py(459)prepare_request()
458 cookies=merged_cookies,
--> 459 hooks=merge_hooks(request.hooks, self.hooks),
460 )
lib/python3.7/site-packages/requests/models.py(317)prepare()
316 self.prepare_cookies(cookies)
--> 317 self.prepare_body(data, files, json)
318 self.prepare_auth(auth, url)
lib/python3.7/site-packages/requests/models.py(467)prepare_body()
466 content_type = 'application/json'
--> 467 body = complexjson.dumps(json)
468 if not isinstance(body, bytes):
lib/python3.7/site-packages/simplejson/__init__.py(395)dumps()
394 ):
--> 395 return _default_encoder.encode(obj)
396 if cls is None:
lib/python3.7/site-packages/simplejson/encoder.py(296)encode()
295 # equivalent to the PySequence_Fast that ''.join() would do.
--> 296 chunks = self.iterencode(o, _one_shot=True)
297 if not isinstance(chunks, (list, tuple)):
lib/python3.7/site-packages/simplejson/encoder.py(378)iterencode()
377 try:
--> 378 return _iterencode(o, 0)
379 finally:
```
I will not attach the binary the `.so` file (can be found in https://filesender.switch.ch/filesender/?vid=59e1dbc9-04e4-67c8-2bb1-00007d77b3bb but you don't need that)
Steps to reproduce:
* create an algorithm with this .json file [1.json](/uploads/d625814e021f43f4543060e5b3045b55/1.json)
* generate a random binary file for this alg and save it as `1.so` for example this: [1.so](/uploads/d7507a1afdff15ed1c07c1b6de9403d7/1.so)
* push it to the online platformSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/76Implement support for database sharing2020-11-12T15:02:19ZSamuel GAISTImplement support for database sharingSee beat/beat.core#103See beat/beat.core#103Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/77CXX algorithm cannot be correctly downloaded2020-11-10T16:42:45ZSamuel GAISTCXX algorithm cannot be correctly downloadedThe way the URL is built is wrong, it hardcodes the current use as the author which is not necessarily true.The way the URL is built is wrong, it hardcodes the current use as the author which is not necessarily true.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/78Database index generated files belongs to docker daemon user2020-11-10T16:47:14ZSamuel GAISTDatabase index generated files belongs to docker daemon userWhich makes them belonging to root currently which is wrong.
It should be the user which currently runs the indexing or a specific UID.Which makes them belonging to root currently which is wrong.
It should be the user which currently runs the indexing or a specific UID.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/79Remove database sharing explicit option2020-11-16T14:34:22ZSamuel GAISTRemove database sharing explicit optionFollowing the discussion on beat/beat.web!410, the database raw data sharing implementation was change and its definition moved to the database declaration.
beat/beat.core!132 implements that.
Therefore remove the explicit database sha...Following the discussion on beat/beat.web!410, the database raw data sharing implementation was change and its definition moved to the database declaration.
beat/beat.core!132 implements that.
Therefore remove the explicit database sharing option here as it is not used anymore.Samuel GAISTSamuel GAIST