beat.cmdline issueshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues2020-05-15T12:56:46Zhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/68beat exp fork command is cumbersome to use2020-05-15T12:56:46ZAmir MOHAMMADIbeat exp fork command is cumbersome to useWhen you fork an experiment in the command line, you have to something like:
```sh
$ beat exp fork test/test/iris/1/iris amir/test/iris/1/means
```
but you can only change the username and name of the experiment when you fork.
When usin...When you fork an experiment in the command line, you have to something like:
```sh
$ beat exp fork test/test/iris/1/iris amir/test/iris/1/means
```
but you can only change the username and name of the experiment when you fork.
When using beat.editor 2.0.0, when I fork an experiment, it only asks for the exp name.
Beat.editor somehow decided to put the forked experiment under user `amir` but I don't know
yet how it decided on that.
Shouldn't this command be also similar?
Something like:
```sh
$ beat exp fork test/test/iris/1/iris means
$ beat exp fork --user amir test/test/iris/1/iris means
```https://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/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/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/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/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/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/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/60Add support for protocol template2019-05-08T09:45:49ZSamuel GAISTAdd support for protocol templateFor database v2, the new protocol template object has been created (see beat/beat.core#64, beat/beat.core!67, and beat/beat.core!71).
This issue tracks adding support for it in beat/beat.cmdline>
Todo:
- [x] Local support
- [ ] Remote ...For database v2, the new protocol template object has been created (see beat/beat.core#64, beat/beat.core!67, and beat/beat.core!71).
This issue tracks adding support for it in beat/beat.cmdline>
Todo:
- [x] Local support
- [ ] Remote supportSamuel GAISTSamuel GAISThttps://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/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/56There is no way to make a clean prefix directory structure with only trusted ...2018-12-21T14:52:06ZZohreh MOSTAANIThere is no way to make a clean prefix directory structure with only trusted system files.In the ALLIES meeting one of the points that was raised was that how to get a clean prefix directory structure, with databases, dataformats, etc in place. With only data from the system not other users, and not to go through copying a pr...In the ALLIES meeting one of the points that was raised was that how to get a clean prefix directory structure, with databases, dataformats, etc in place. With only data from the system not other users, and not to go through copying a prefix from another git repository.
It may be possible to use command line to make such a directory.https://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/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/53strange behaviour of beat.cmline when pulling objects from platform results i...2018-12-06T09:53:24ZZohreh MOSTAANIstrange behaviour of beat.cmline when pulling objects from platform results in beat.editor crashing as well.Hi,
Today when I ran beateditor command to edit some experiment, it did not show me anything on the Firefox. It only shows the page for split second and then it is a blank page. I updated beat.editor with conda in case there were some c...Hi,
Today when I ran beateditor command to edit some experiment, it did not show me anything on the Firefox. It only shows the page for split second and then it is a blank page. I updated beat.editor with conda in case there were some changes but the problem is still there.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/51The connections are not pushed to the platform when pushing a toolchain.2018-12-04T15:35:40ZZohreh MOSTAANIThe connections are not pushed to the platform when pushing a toolchain.I pushed a toolchain to the platform with this command:
```
beat toolchains push zmostaani/sbhatta-iqm-face-antispoofing-test/2
```
This is the output:
```
toolchains push zmostaani/sbhatta-iqm-face-antispoofing-test/2
[+] toolchains/tut...I pushed a toolchain to the platform with this command:
```
beat toolchains push zmostaani/sbhatta-iqm-face-antispoofing-test/2
```
This is the output:
```
toolchains push zmostaani/sbhatta-iqm-face-antispoofing-test/2
[+] toolchains/tutorial/eigenface/1 (@2014-08-11T14:27:37)
[l] toolchains/test/iris_advanced_editor/1
[l] toolchains/zmostaani/eigenface-new-error/2
[l] toolchains/tutorial/eigenface-error/1
[l] toolchains/zmostaani/editor-test/1
[l] toolchains/zmostaani/editor-test-2/1
[l] toolchains/zmostaani/eigenface-clone/1
[l] toolchains/zmostaani/eigenface-test/1
[l] toolchains/test/test/1
[l] toolchains/zmostaani/eigenface-new/1
[l] toolchains/zmostaani/sbhatta-iqm-face-antispoofing-test/1
[l] toolchains/test/iris/1
[l] toolchains/zmostaani/sbhatta-iqm-face-antispoofing-test/2
[l] toolchains/test/iris_advanced/1
[l] toolchains/zmostaani/eigenface-new-error/1
pushing toolchains/zmostaani/sbhatta-iqm-face-antispoofing-test/2 [l]
Successfuly created `zmostaani/sbhatta-iqm-face-antispoofing-test/2'
```
I went to check it on the platform. Aside from the problem with version numbering that has been mentioned in issue #49 and #50, when I look at it on the platform there is no connection to any block.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/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/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.anjos