beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-01-18T18:01:51Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/162[algorithm] a "warning" for algorithms2019-01-18T18:01:51ZFlavio TARSETTI[algorithm] a "warning" for algorithmsA strange warning appears when loading algorithms in the interface:
```
Warning: Failed prop type: Invalid prop `children` supplied to `Form`, expected a ReactNode.
in Form (created by AlgorithmEditor)
in AlgorithmEditor (create...A strange warning appears when loading algorithms in the interface:
```
Warning: Failed prop type: Invalid prop `children` supplied to `Form`, expected a ReactNode.
in Form (created by AlgorithmEditor)
in AlgorithmEditor (created by Connect(AlgorithmEditor))
in Connect(AlgorithmEditor) (created by EntityDetail)
in div (created by TabPane)
in TabPane (created by EntityDetail)
in div (created by TabContent)
in TabContent (created by EntityDetail)
in div (created by Col)
in Col (created by EntityDetail)
in div (created by Row)
in Row (created by EntityDetail)
in div (created by Container)
in Container (created by EntityDetail)
in EntityDetail (created by Connect(EntityDetail))
in Connect(EntityDetail) (created by Route)
in Route (created by EntityHome)
in Switch (created by EntityHome)
in EntityHome (created by MainContent)
in div (created by MainContent)
in MainContent (created by Route)
in Route (created by App)
in Switch (created by App)
in div (created by Container)
in Container (created by App)
in Router (created by HashRouter)
in HashRouter (created by App)
in App (created by HotExportedApp)
in AppContainer (created by HotExportedApp)
in HotExportedApp
in Provider
printWarning @ checkPropTypes.js:19
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1300
createElementWithValidation @ react.development.js:1388
React$$1.createElement @ react-hot-loader.development.js:964
AlgorithmEditor.render @ AlgorithmEditor.jsx:566
finishClassComponent @ react-dom.development.js:13193
updateClassComponent @ react-dom.development.js:13155
beginWork @ react-dom.development.js:13824
performUnitOfWork @ react-dom.development.js:15863
workLoop @ react-dom.development.js:15902
renderRoot @ react-dom.development.js:15942
performWorkOnRoot @ react-dom.development.js:16560
performWork @ react-dom.development.js:16482
performSyncWork @ react-dom.development.js:16454
interactiveUpdates$1 @ react-dom.development.js:16719
interactiveUpdates @ react-dom.development.js:2150
dispatchInteractiveEvent @ react-dom.development.js:4532
```Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/161[validation] types and values for parameters not properly checked in editor/ ...2020-02-12T12:23:03ZFlavio TARSETTI[validation] types and values for parameters not properly checked in editor/ second issue old value saved@jdiefenbaugh : The editor presents some validation bugs
The editor seems to have unexpected behavior for validation of parameters.
A `string value` could be saved in a `int8`, and this is valid and could be saved in the `json` file.
...@jdiefenbaugh : The editor presents some validation bugs
The editor seems to have unexpected behavior for validation of parameters.
A `string value` could be saved in a `int8`, and this is valid and could be saved in the `json` file.
A second issue comes from the fact that all parameters have their old value saved somewhere in the props or state history.
For example if we suddenly decide to change the parameter type from `"string"` to `"int"`, the value `"helloworld"` will be kept as the value for the `"int"`Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/160[ci] issue with conda-build2018-10-12T05:58:03ZFlavio TARSETTI[ci] issue with conda-build@amohammadi @tiago.pereira :
Seems like there's an issue with the linux CI again:
`https://gitlab.idiap.ch/beat/beat.editor/-/jobs/149048`
I have launched a couple of times since yesterday but it seems to fail with the same conda issu...@amohammadi @tiago.pereira :
Seems like there's an issue with the linux CI again:
`https://gitlab.idiap.ch/beat/beat.editor/-/jobs/149048`
I have launched a couple of times since yesterday but it seems to fail with the same conda issue.
Could you please help ?https://gitlab.idiap.ch/beat/beat.editor/-/issues/159Discussion: Question (used libs)2019-01-09T18:04:25ZFlavio TARSETTIDiscussion: Question (used libs)@jdiefenbaugh :
Could you explain to me this part please ?
```javascript
renderLibraries = () => (
<TabPane tabId='2'>
<Row>
<Col sm='12'>
...@jdiefenbaugh :
Could you explain to me this part please ?
```javascript
renderLibraries = () => (
<TabPane tabId='2'>
<Row>
<Col sm='12'>
{
// loop through all the used libs
(Object.entries(this.props.data.contents.uses): [string, any][])
.map(([name, lib], i, lEntries) => (
<TypedField
key={i}
name={name}
type={lib}
types={this.props.libraries.map(l => l.name)}
existingFields={lEntries.map(([n, v]) => n)}
nameUpdateFunc={str => {
// update the alias
this.changeContentsVal('uses',
changeObjFieldName(
this.props.data.contents.uses,
name,
str
)
);
}}
typeUpdateFunc={str => {
// update the chosen library for the alias
const libs = {
...this.props.data.contents.uses,
[name]: str
};
this.changeContentsVal('uses', libs);
}}
deleteFunc={() => {
const libs = { ...this.props.data.contents.uses };
delete libs[name];
this.changeContentsVal('uses', libs);
}}
/>
))
}
</Col>
</Row>
<Button outline block
id='newLibraryBtn'
onClick={() => {
const newKey = generateNewKey('library', Object.keys(this.props.data.contents.uses));
this.changeContentsVal('uses',
{
...this.props.data.contents.uses,
[newKey]: ''
}
);
}}
>
New Library
</Button>
</TabPane>
);
```
What actually interests me is what is inside the loop (// loop through all the used libs)
Could you explain to me a bit please and point me to some documentation you read to write this kind of stuff?
Thankshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/158[ci] linux builds not working2018-09-19T14:06:56ZFlavio TARSETTI[ci] linux builds not working@tiago.pereira @amohammadi @andre.anjos :
I guess the Linux ci's are down. Could you fix that please ?
Linux 27:
* `https://gitlab.idiap.ch/beat/beat.editor/-/jobs/148670`
Linux 36:
* `https://gitlab.idiap.ch/beat/beat.editor/-/jobs/1...@tiago.pereira @amohammadi @andre.anjos :
I guess the Linux ci's are down. Could you fix that please ?
Linux 27:
* `https://gitlab.idiap.ch/beat/beat.editor/-/jobs/148670`
Linux 36:
* `https://gitlab.idiap.ch/beat/beat.editor/-/jobs/148684`
Linux browser 36:
* `https://gitlab.idiap.ch/beat/beat.editor/-/jobs/148682`https://gitlab.idiap.ch/beat/beat.editor/-/issues/157Disable Python 2 builds on mac2018-10-02T07:38:21ZSamuel GAISTDisable Python 2 builds on macSince the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
...Since the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
See https://gitlab.idiap.ch/bob/bob.admin/merge_requests/105Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/issues/61Remove macOS Python 2 build2018-10-01T08:58:38ZSamuel GAISTRemove macOS Python 2 buildSince the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
...Since the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
See https://gitlab.idiap.ch/bob/bob.admin/merge_requests/105Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/18Remove macOS Python 2 build2018-09-28T10:06:05ZSamuel GAISTRemove macOS Python 2 buildSince the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
...Since the BOB infrastructure is used to build the BEAT conda packages and it is planned to drop Python 2 support by the end of the year, the macOS builds are already planned to be removed shortly, therefore remove it from this package.
See https://gitlab.idiap.ch/bob/bob.admin/merge_requests/105Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/156[conda] issue unable to install beat.editor2018-09-20T08:12:49ZFlavio TARSETTI[conda] issue unable to install beat.editor@tiago.pereira @amohammadi :
We are having an issue with `conda install` of `beat` packages:
Our partner on `allies` is having the same issue on his `osx` machine. I first thought it was a problem with his system,
but I am having the s...@tiago.pereira @amohammadi :
We are having an issue with `conda install` of `beat` packages:
Our partner on `allies` is having the same issue on his `osx` machine. I first thought it was a problem with his system,
but I am having the same issue here on my `linux` machine
Have a look at this strange output:
the search finds the package `beat.editor` from the channel `https://www.idiap.ch/software/beat/conda/label/beta` but unable to install it.
Could you please help ? Thanks.
```
conda create -n beat_editor_new_test
Solving environment: done
## Package Plan ##
environment location: <path>/miniconda3/envs/beat_editor_new_test
Proceed ([y]/n)? y
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
#
# To activate this environment, use
#
# $ conda activate beat_editor_new_test
#
# To deactivate an active environment, use
#
# $ conda deactivate
~$ conda activate beat_editor_new_test
(beat_editor_new_test) ~$ conda search beat.editor
Loading channels: done
PackagesNotFoundError: The following packages are not available from current channels:
- beat.editor
Current channels:
- https://repo.anaconda.com/pkgs/main/linux-64
- https://repo.anaconda.com/pkgs/main/noarch
- https://repo.anaconda.com/pkgs/free/linux-64
- https://repo.anaconda.com/pkgs/free/noarch
- https://repo.anaconda.com/pkgs/r/linux-64
- https://repo.anaconda.com/pkgs/r/noarch
- https://repo.anaconda.com/pkgs/pro/linux-64
- https://repo.anaconda.com/pkgs/pro/noarch
To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page.
(beat_editor_new_test) ~$ conda config --env --add channels https://www.idiap.ch/software/beat/conda/label/beta
(beat_editor_new_test) ~$ conda search beat.editor
Loading channels: done
# Name Version Build Channel
beat.editor 1.0.0b0 py27h551ffd9_13 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h551ffd9_14 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h551ffd9_15 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h551ffd9_16 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h551ffd9_17 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h551ffd9_18 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_19 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_20 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_21 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_22 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_23 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27h9b23768_24 software/beat/conda/label/beta
beat.editor 1.0.0b0 py27hdf2c03f_12 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_13 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_14 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_15 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_16 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_17 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h551ffd9_18 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_19 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_20 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_21 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_22 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_23 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36h9b23768_24 software/beat/conda/label/beta
beat.editor 1.0.0b0 py36hdf2c03f_12 software/beat/conda/label/beta
(beat_editor_new_test) ~$ conda install beat.editor
Solving environment: failed
PackagesNotFoundError: The following packages are not available from current channels:
- beat.editor
- beat.cmdline
- beat.core
- docker-py
- beat.editor
- beat.cmdline
- oset
- beat.editor
- flask-restful
Current channels:
- https://www.idiap.ch/software/beat/conda/label/beta/linux-64
- https://www.idiap.ch/software/beat/conda/label/beta/noarch
- https://repo.anaconda.com/pkgs/main/linux-64
- https://repo.anaconda.com/pkgs/main/noarch
- https://repo.anaconda.com/pkgs/free/linux-64
- https://repo.anaconda.com/pkgs/free/noarch
- https://repo.anaconda.com/pkgs/r/linux-64
- https://repo.anaconda.com/pkgs/r/noarch
- https://repo.anaconda.com/pkgs/pro/linux-64
- https://repo.anaconda.com/pkgs/pro/noarch
To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page.
```
ping @andre.anjos @zmostaani @jdiefenbaugh @samuel.gaist to keep you updatedFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/155Change license to BSD 3-clause2020-02-13T09:52:10ZAndré 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.
@jdiefenbaugh: 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 source 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.https://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.core/-/issues/60Change license to BSD 3-clause2019-03-13T15:00:24ZAndré 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.
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.backend.python/-/issues/17Change license to BSD 3-clause2019-03-13T08:19:09ZAndré 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.
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.editor/-/issues/154A few issues with the Plotter editor2018-10-31T13:05:05ZJaden DIEFENBAUGHA few issues with the Plotter editor- The dataformat select by default shows the first available plotter dataformat as selected, but it should really show a "blank" selection, prompting the user to choose a dataformat
- The default value for (only `bool`-type?) parameters ...- The dataformat select by default shows the first available plotter dataformat as selected, but it should really show a "blank" selection, prompting the user to choose a dataformat
- The default value for (only `bool`-type?) parameters arent saved to the metadata
- There's no way to add libraries to the plotter!Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/153Add a way to delete multiple conns at once2020-02-13T09:55:42ZJaden DIEFENBAUGHAdd a way to delete multiple conns at onceSee #152 for the exact request.
This issue was fixed in https://gitlab.idiap.ch/beat/beat.editor/merge_requests/117See #152 for the exact request.
This issue was fixed in https://gitlab.idiap.ch/beat/beat.editor/merge_requests/117[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/152Some suggestions for beat editor2019-01-28T10:11:31ZZohreh MOSTAANISome suggestions for beat editorHi,
Here are some ideas that I got while using beat editor. You might find them useful.
* I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and...Hi,
Here are some ideas that I got while using beat editor. You might find them useful.
* I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even though it is more convenient while making a toolchain to just connect an output to an input it is very difficult to understand what is going on when you look at an experiment using that toolchain, specially when the experiments get bigger and the connections are crossing each other. Even if there was a mechanism to highlight a chosen connection in the experiment page can be really helpful. This mechanism is already there when making a toolchain but not when you look at the experiment.
* It would be good if the user can assign a colour to a channel of data while making the toolchain. As far as I tried the channel colours are chosen by the system and in many times they are visually close to each other. I sometimes had difficulty distinguishing between them.
* It would be nice that user can change the name of groups while defining the algorithms. This is not the case as far as I experienced.
* It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
* It would be nice if the user can choose several connections and delete them altogether. Even if there was a button like "delete all connections" might be useful. I had painful experiences trying to remove all the connections but not the blocks. :)
I might be wrong about any of these points and the features may already be there. Please let me know if that is the case. :)https://gitlab.idiap.ch/beat/beat.editor/-/issues/151need to manually access the web interface using `beat editor serve ` command2018-09-10T16:00:51ZZohreh MOSTAANIneed to manually access the web interface using `beat editor serve ` commandHi,
I got the new version of beat editor and now when I run the command `beat editor serve` the firfox window does not pop up. I have to access it manually.Hi,
I got the new version of beat editor and now when I run the command `beat editor serve` the firfox window does not pop up. I have to access it manually.https://gitlab.idiap.ch/beat/beat.editor/-/issues/150Specify the `june-allies` branch of `beat.tutorial` in documentation2018-12-19T19:02:44ZJaden DIEFENBAUGHSpecify the `june-allies` branch of `beat.tutorial` in documentationhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/149beateditor is completely down for me2018-12-06T09:49:29ZZohreh MOSTAANIbeateditor is completely down for meHi,
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.editor/-/issues/148packer_scripts does not exist, while it is mentioned in the documentation of ...2018-11-26T02:45:09ZZohreh MOSTAANIpacker_scripts does not exist, while it is mentioned in the documentation of Method 1 for installationThere is no packer_scripts in `https://gitlab.idiap.ch/beat/beat.tutorial.git`.There is no packer_scripts in `https://gitlab.idiap.ch/beat/beat.tutorial.git`.