beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2020-02-12T12:35:15Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/198smart color picking for the database blocks of a toolchain so that the close ...2020-02-12T12:35:15ZZohreh MOSTAANIsmart color picking for the database blocks of a toolchain so that the close ones are visually distinct.see #152 for info on this.see #152 for info on this.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/197more information available as comment on the python template produced for dat...2020-02-12T12:34:42ZZohreh MOSTAANImore information available as comment on the python template produced for databases.It would be nice to have the output names and output data types as comment on the python template for a database when you are preparing it using beat editor.It would be nice to have the output names and output data types as comment on the python template for a database when you are preparing it using beat editor.https://gitlab.idiap.ch/beat/beat.editor/-/issues/195visual feedback to the user when the save button is pressed2020-02-12T12:32:25ZZohreh MOSTAANIvisual feedback to the user when the save button is pressedWhen I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right ...When I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right now I refresh the whole page to make sure that the changes are done.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/194visula distiction between different parameter cathegories on the experiment p...2020-02-12T12:31:57ZZohreh MOSTAANIvisula distiction between different parameter cathegories on the experiment page.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.[v2] 3 - Experiment editorhttps://gitlab.idiap.ch/beat/docs/-/issues/11Inter-package documentation links are broken2019-06-28T11:36:28ZAndré AnjosInter-package documentation links are brokenInter-package documentation links are not correct at build time because of dependencies or rather depending on packages that are not dependencies (beat.doc is not a dependency of beat.core). The documentation conf.py file should try to g...Inter-package documentation links are not correct at build time because of dependencies or rather depending on packages that are not dependencies (beat.doc is not a dependency of beat.core). The documentation conf.py file should try to grab information from the package like version and the URL for the final documentation from environment variables.Zohreh MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/192[meta] Naming branches to associate it with an issue2019-02-25T11:34:25ZJaden DIEFENBAUGH[meta] Naming branches to associate it with an issueIn `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressi...In `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressing? So names like the following are fine:
- "issue_20_fix_wrong_index"
- "implement_db_editor_248"
But names like the following aren't okay except in rare cases:
- "fix_wrong_index"
- "implement_db_editor"
I personally find it hard to understand what someone is doing in a branch when they don't reference an existing issue.
_[edit]_:
Final decision: <issue_number>_name_of_the_branchhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/191Remove v1 artifacts2019-10-04T15:12:54ZJaden DIEFENBAUGHRemove v1 artifactsSummary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does i...Summary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does it provide?
Remove all of the above:
- Remove all the JS stuff from `.gitignore`
- Remove the `beat/editor/js` directory
- Remove most of the the text in `doc/index.rst` and just have it point to `doc/contribute.rst` for now
- Remove `doc/{editor.rst,licenses.rst}`
- Save `doc/{img/,svg/}` as we'll probably want to adapt these later for v2 documentationhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/190AssetType Unknown path spelling2019-10-04T15:12:54ZJaden DIEFENBAUGHAssetType Unknown path spellingSummary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd4...Summary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd450167fbf24f39666d86576e43a0b/beat/editor/backend/assetmodel.py#L44Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/189Package "pre-commit" doesn't exist in conda2019-10-04T15:12:54ZJaden DIEFENBAUGHPackage "pre-commit" doesn't exist in condaSummary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Summary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/188Add port configuration to v1 for ALLIES partners2019-02-12T18:55:52ZJaden DIEFENBAUGHAdd port configuration to v1 for ALLIES partnersSummary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for ...Summary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for querying the API (JS code).
What does it provide?
Port configuration sufficient for the partner.
Relevant links / references
See https://groups.google.com/d/msg/beat-devel/m9vCN1J6I8E/pA9smNcXEgAJhttps://gitlab.idiap.ch/beat/beat.web/-/issues/515BEAT website certificate and expiration2020-03-30T14:04:20ZAndré AnjosBEAT website certificate and expirationThe BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time f...The BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time for people to "adapt" to a new address, I propose we start looking for solutions now.
@samuel.gaist: Could you please contact the system group (via a ticket) and ask them which solutions could be setup to host the platform under "idiap.ch".
I thought of 2 options, but I'm not sure whether these are feasible:
1. "https://beat.idiap.ch": The advantage is that swagger docs would start working again...
2. "https://www.idiap.ch/software/beat/platform": This would be the one that makes more sense "structurally"Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/514Frontpage counters should only display numbers of elements that are publicly ...2020-11-17T14:49:38ZAndré AnjosFrontpage counters should only display numbers of elements that are publicly available (if user not logged in)The current front page counters of the BEAT platform display the total number of objects **available** in the platform - not necessarily available to the current user.
We should change this to display what is the total available to the ...The current front page counters of the BEAT platform display the total number of objects **available** in the platform - not necessarily available to the current user.
We should change this to display what is the total available to the current logged in user and, failing that, to the anonymous user.
It is disappointing for the (anonymous) user to see a smaller number of objects when clicking the links.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/187cross-tab-sync branch still active?2018-12-20T18:45:18ZAndré Anjoscross-tab-sync branch still active?This branch is now stale, w/o any further development.
@jdiefenbaugh: please delete it if no longer needed.This branch is now stale, w/o any further development.
@jdiefenbaugh: please delete it if no longer needed.[v1] Ongoing patching until [v2] is readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/513Release 1.4.1 through bob-release-scripts2018-12-20T18:24:38ZAndré AnjosRelease 1.4.1 through bob-release-scripts@samuel.gaist: may you please release version 1.4.1 of this package by tagging it with bob release scripts? You have everything in place now to go through the same workflow as for other packages.
If I look at the beat-eu.org/platform w...@samuel.gaist: may you please release version 1.4.1 of this package by tagging it with bob release scripts? You have everything in place now to go through the same workflow as for other packages.
If I look at the beat-eu.org/platform website, it unfortunately looks like version 1.3.1rc1 is deployed. You can see this by looking down on any webpage or by clicking on the user documentation. What I think happened is that you tagged the release w/o updating the value of the version inside `setup.py`.
The other issue is that there are not release notes for version 1.4.0 (https://gitlab.idiap.ch/beat/beat.web/tags/v1.4.0), so difficult to see what went on - which I'm sure was a lot of work. If you have the time, please update this.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/186v2/PyQt Infrastructure2019-04-25T10:37:07ZJaden DIEFENBAUGHv2/PyQt InfrastructureHere's a tracking issue for the non-editor work we'll need in V2.
- [x] Project layout (including Conda setup)
- [x] FS management
- [x] Network management
- [x] `beat.cmdline` integration (including layout stuff)
- [x] `beat.core` inte...Here's a tracking issue for the non-editor work we'll need in V2.
- [x] Project layout (including Conda setup)
- [x] FS management
- [x] Network management
- [x] `beat.cmdline` integration (including layout stuff)
- [x] `beat.core` integration (including Docker stuff)
- [x] PyQt app framework
- [x] Running example
- [x] Navigation
- [x] State management backend (see notes below)
- [x] Testing setup including example
- [x] Documentation setup if different than v1
- [x] CI integration
State management is all about providing a idiomatic interface to the various resources we work with (the prefix, APIs, docker images, graphviz, network, etc.):
- Lets the user undo/redo things
- Lets the app index & transform BEAT objects quickly
- Easy MapReduce-like operations on data
- Querying docker containers
- Querying Graphviz
- Lets us mock the resources easily for testing[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/185Experiment Editor2020-08-10T12:44:08ZJaden DIEFENBAUGHExperiment EditorThis issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] S...This issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] Smart filtering
Unlike all other BEAT assets, creating a new experiment requires an additional step therefore, a dedicated task is needed with regard to the creation of such a new asset:
* [x] Add support for new experiment creation to asset dialog[v2] 3 - Experiment editorSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/184Toolchain Editor2020-06-17T08:28:24ZJaden DIEFENBAUGHToolchain Editor[v2] 2 - Toolchain editorFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/183Database Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHDatabase Editor[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/182Plotterparameter Editor2019-10-04T15:12:26ZJaden DIEFENBAUGHPlotterparameter Editor[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/181Plotter Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHPlotter Editor[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTI