beat issues
https://gitlab.idiap.ch/groups/beat/-/issues
2019-10-04T08:44:08Z
https://gitlab.idiap.ch/beat/beat.core/-/issues/89
Improve output error messages
2019-10-04T08:44:08Z
Samuel GAIST
Improve output error messages
When not enough data is written on an output, the related cache will be cleaned.
An error message must be shown to the user so he knows what is happening.
When not enough data is written on an output, the related cache will be cleaned.
An error message must be shown to the user so he knows what is happening.
https://gitlab.idiap.ch/beat/beat.web/-/issues/537
Implement experiment reset API
2019-09-09T16:21:29Z
Samuel GAIST
Implement experiment reset API
Currently, resetting an experiment can only be done on the experiment result page.
Add the necessary API so that it can also be done through the API.
Relates to beat/beat.cmdline#62
Currently, resetting an experiment can only be done on the experiment result page.
Add the necessary API so that it can also be done through the API.
Relates to beat/beat.cmdline#62
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/62
Add support for remote experiments execution handling
2019-09-16T17:30:12Z
Samuel GAIST
Add support for remote experiments execution handling
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> ...
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 GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/536
Some of the Models defined in django are not well documented
2019-09-05T11:36:57Z
Zohreh MOSTAANI
Some of the Models defined in django are not well documented
The "swagger.yaml" file that includes the beat.web api information that can be rendered into the sphinx documentation does not include complete information for all the models included in a response object. Some of the basic ones are show...
The "swagger.yaml" file that includes the beat.web api information that can be rendered into the sphinx documentation does not include complete information for all the models included in a response object. Some of the basic ones are shown though which means that the package produces this yaml file is working as expected.
It seems that those objects which are not shown, are not well documented in the code and because there are several layers of inheritance for each class, it is difficult to find where exactly the problem lies.
With a brief discussion with @samuel.gaist we tried something fast but it did not work. It required a deeper dive into the implementation.
https://gitlab.idiap.ch/beat/beat.web/-/issues/535
Sphinxcontrib-openapi does not render response json objects for api in the do...
2019-09-05T12:39:23Z
Zohreh MOSTAANI
Sphinxcontrib-openapi does not render response json objects for api in the documentation
The sphinxcontrib-openapi cannot render the response objects defined in the swagger.yaml file.
The sphinxcontrib-openapi cannot render the response objects defined in the swagger.yaml file.
Zohreh MOSTAANI
Zohreh MOSTAANI
https://gitlab.idiap.ch/beat/beat.web/-/issues/534
Needs beat-devel update
2019-08-29T13:39:14Z
André Anjos
Needs beat-devel update
Could you please update beat-devel to the latest?
We need to keep-up with the base software updates.
So far, this is done manually for this package.
Could you please update beat-devel to the latest?
We need to keep-up with the base software updates.
So far, this is done manually for this package.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/533
Strange behaviour concerning a POST method that needed to be GET.
2019-08-22T15:38:08Z
Zohreh MOSTAANI
Strange behaviour concerning a POST method that needed to be GET.
In the `api.py` file for `report`, there are two classes that have POST methods which in fact should have been GET.
`ReportRSTCompileView` and `ReportRSTCompileAnonView`. The definitions are here:
https://gitlab.idiap.ch/beat/beat.web/b...
In the `api.py` file for `report`, there are two classes that have POST methods which in fact should have been GET.
`ReportRSTCompileView` and `ReportRSTCompileAnonView`. The definitions are here:
https://gitlab.idiap.ch/beat/beat.web/blob/master/beat/web/reports/api.py
Both of the mentioned classes are using another method `compileTextItem` defined in `models.py`. This function is not readable and it raises an exception error `"Error in ReportRSTCompileView: The Python docutils library isn't installed."` which does not seem to belong here. The definition is here:
https://gitlab.idiap.ch/beat/beat.web/blob/master/beat/web/reports/models.py
https://gitlab.idiap.ch/beat/beat.core/-/issues/87
Remove parameters from analyzer block
2019-08-19T19:15:28Z
Samuel GAIST
Remove parameters from analyzer block
Currently analyzer blocks are treated mostly like normal algorithm blocks except the handling of the output.
This means that they can also have parameters. After several discussions, it has been concluded that having the possibility to ...
Currently analyzer blocks are treated mostly like normal algorithm blocks except the handling of the output.
This means that they can also have parameters. After several discussions, it has been concluded that having the possibility to parametrize an analyzer would bring an unwelcomed level of complexity especially when creating reports.
If an analyzer should provide different outputs, then it should come in several versions to make it clear from the start what it will provide and how the analysis is done.
The following decisions have been made:
- Keep the current few analyzers that do have parameters as they are
- Remove the parameters field from the V2 algorithm schema for the analyzer definition
Soft loops
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/247
Sphinx errors during nightly builds
2019-08-12T07:13:09Z
André Anjos
Sphinx errors during nightly builds
The version of Sphinx was updated to 2.x on the base software stack and, with that, there is a new error on the documentation (actually a warning, but it is in pedantic mode). For this reason, the building of the editor v1 failed, and s...
The version of Sphinx was updated to 2.x on the base software stack and, with that, there is a new error on the documentation (actually a warning, but it is in pedantic mode). For this reason, the building of the editor v1 failed, and so did the nightlies.
To get a green nightly, we need to fix this.
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.core/-/issues/86
Loop parts name
2019-07-31T08:30:04Z
Samuel GAIST
Loop parts name
Based on experience and discussions, the loop parts name are not really clear.
They will be changed to the following to make things clearer:
- XXX_loop_user -> XXX_loop_processor
- XXX_loop -> XXX_loop_evaluator
This will require upda...
Based on experience and discussions, the loop parts name are not really clear.
They will be changed to the following to make things clearer:
- XXX_loop_user -> XXX_loop_processor
- XXX_loop -> XXX_loop_evaluator
This will require updates to the corresponding algorithms.
Soft loops
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.core/-/issues/85
Synchronised input for loop blocks
2019-07-30T12:56:03Z
Samuel GAIST
Synchronised input for loop blocks
Currently the two algorithm making a loop macro block are not synchronized input wise.
This is required in sequential mode so the validating part of the loop knows it uses
the same data as the current processing part.
This issue tracks...
Currently the two algorithm making a loop macro block are not synchronized input wise.
This is required in sequential mode so the validating part of the loop knows it uses
the same data as the current processing part.
This issue tracks that input synchronization.
Soft loops
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.core/-/issues/84
Implement output for loop block
2019-07-30T07:15:14Z
Samuel GAIST
Implement output for loop block
Currently the loop blocks don't have any outputs.
This issue tracks the implementation of this feature in the loop block.
One requested constraint for these outputs is that the write to them should happen when a write occurs in the out...
Currently the loop blocks don't have any outputs.
This issue tracks the implementation of this feature in the loop block.
One requested constraint for these outputs is that the write to them should happen when a write occurs in the output of a loop user block.
Soft loops
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/246
Correct base types management in AssetModel
2020-08-10T08:39:27Z
Samuel GAIST
Correct base types management in AssetModel
Summary
The DataFormat base types provided through AssetModel shall not be used everywhere a DataFormat is used.
An analysis must be done to determine where exactly it make sense to have them and also if they must be made availble toge...
Summary
The DataFormat base types provided through AssetModel shall not be used everywhere a DataFormat is used.
An analysis must be done to determine where exactly it make sense to have them and also if they must be made availble together with the other Dataformats provided by the prefix.
AssetModel shall be purged from these types and a dedicated subclass created if it makes sense to provide them all in one or more places in the code.
Depending also on whether these base types should be the only type used, another model might be created or [QStringListModel](https://doc.qt.io/qt-5/qstringlistmodel.html) used directly in these cases.
[v2] 1 - Edition/Visualization for small editors
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/245
Improve error handling
2019-12-11T09:57:48Z
Samuel GAIST
Improve error handling
Summary
Currently, there's lot of code triggering a RuntimeError which in turn will make beat.editor stop.
Most of these situations should be gracefully handled. If possible, a fix should be proposed to the user so he can continue work...
Summary
Currently, there's lot of code triggering a RuntimeError which in turn will make beat.editor stop.
Most of these situations should be gracefully handled. If possible, a fix should be proposed to the user so he can continue working.
Steps to reproduce
1) Create a new Plotter
2) Load the plotter
This will make beat.editor crash as the new Plotter will be based on the prototype that contains an invalid entry.
This situation is already reported in #244
What is the current bug behavior?
beat.editor will end there
What is the expected correct behavior?
beat.editor should not stop
Possible fixes
The user should get a message about what is going wrong. If possible a fix should be proposed and applied if accepted.
In any case, the editor should continue working.
[v2] 1 - Edition/Visualization for small editors
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/244
Improve plotter new creation handling
2019-10-04T15:12:49Z
Samuel GAIST
Improve plotter new creation handling
Summary
Currently when creating a new Plotter, the prototype contains "plot/unknown/1".
This has problematic implications:
- The editor will fail to load it
- Test will fail because the editor can't load that dataformat
Steps to repr...
Summary
Currently when creating a new Plotter, the prototype contains "plot/unknown/1".
This has problematic implications:
- The editor will fail to load it
- Test will fail because the editor can't load that dataformat
Steps to reproduce
1) Click on new
2) Select Plotter
3) Try to edit the plotter created
What is the current bug behavior?
An error is raised and it make the application fail
What is the expected correct behavior?
Either:
- Show a dialog asking to select a dataformat to use.
- Select a suitable dataformat from the prefix. Maybe a simple default like for the algorithm prototype.
Possible fixes
One possibility could be to have a method called after the dialog has been closed that can be re-implemented in sub-classes to do whatever is needed for the newly created object.
Another would be to move the dialog logic in its own method so re-implementing _createNewAsset would be easier.
Note that this affects beat/beat.editor!101
[v2] 1 - Edition/Visualization for small editors
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/243
There is no way to close an asset without opening another one.
2020-08-10T15:27:51Z
Zohreh MOSTAANI
There is no way to close an asset without opening another one.
At the moment at all the times there should be one asset opened (except for when the editor starts).
It might be useful to add a button to close an asset without opening a new one. It might also be useful in the future if multiple insta...
At the moment at all the times there should be one asset opened (except for when the editor starts).
It might be useful to add a button to close an asset without opening a new one. It might also be useful in the future if multiple instances/windows of editor are open.
https://gitlab.idiap.ch/beat/beat.editor/-/issues/242
Delete button does not ask for confirmation if you are deleting an asset that...
2019-10-04T15:12:53Z
Zohreh MOSTAANI
Delete button does not ask for confirmation if you are deleting an asset that is not being edited at the time.
If you are editing an asset and delete the same asset the dialogue box says something like "you are about to delete the asset you are editing currently, are you sure", but if you try to delete another asset while you are still editing an...
If you are editing an asset and delete the same asset the dialogue box says something like "you are about to delete the asset you are editing currently, are you sure", but if you try to delete another asset while you are still editing another asset (This is possible because you are able to borrows the files on the left of the editor window), it just deletes the asset without asking any confirmation. This is not good since users can delete some files by accident and there is no way to recover them from the editor at the moment (there is no undo).
https://gitlab.idiap.ch/beat/beat.editor/-/issues/241
Make the size of the dialogue boxes changable
2020-02-26T11:01:22Z
Zohreh MOSTAANI
Make the size of the dialogue boxes changable
When you are saving an asset the name of the asset being saved is written on the top of the dialogue box in the format <username>/<asset_name>/<version> , which usually is a long string but the size of the dialogue box is very small and ...
When you are saving an asset the name of the asset being saved is written on the top of the dialogue box in the format <username>/<asset_name>/<version> , which usually is a long string but the size of the dialogue box is very small and this string is not readable. Also the user cannot change the size of the box as well which means cannot read the name of the asset being saved. This can be problematic as explained in #230 (closed bug).
The dialogue box for deleting an asset is also fixed in size. At the moment there is no name on the top of the dialogue box but it may become necessary in the future.
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/240
ParameterWidget needs better size handling
2019-07-02T08:56:34Z
Samuel GAIST
ParameterWidget needs better size handling
Summary
ParameterWidget has way too much white space when showing "small" editors
Steps to reproduce
Open a plotter and look at the parameters
What is the current bug behavior?
Depending on the type of parameter and it's setup, th...
Summary
ParameterWidget has way too much white space when showing "small" editors
Steps to reproduce
Open a plotter and look at the parameters
What is the current bug behavior?
Depending on the type of parameter and it's setup, there's too much vertical
space.
What is the expected correct behavior?
We should have the editor take just the height needed.
Possible fixes
The widget should be resized when the current editor changes
[v2] 1 - Edition/Visualization for small editors
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/239
Library editor forces a dump of an optional key "uses:{}" for the available l...
2020-05-28T10:57:29Z
Flavio TARSETTI
Library editor forces a dump of an optional key "uses:{}" for the available libraries when the field is empty
#### Summary
The library editor requires fixing. The key "uses" is set mandatory during the dump when it should actually be an optional field
#### Steps to reproduce
The bug is identified here:
https://gitlab.idiap.ch/beat/beat.edito...
#### Summary
The library editor requires fixing. The key "uses" is set mandatory during the dump when it should actually be an optional field
#### Steps to reproduce
The bug is identified here:
https://gitlab.idiap.ch/beat/beat.editor/blob/v2/beat/editor/test/test_libraryeditor.py#L40
and explained in detail: https://gitlab.idiap.ch/beat/beat.core/merge_requests/79
#### What is the current bug behavior?
The current behavior forces the library to have a dump "uses" key
#### What is the expected correct behavior?
The schema of the library is explicit about it being an optional field. So if empty we should not get a "uses:{}" at the dump
The test needs to be fixed accordingly
#### Relevant code:
https://gitlab.idiap.ch/beat/beat.editor/blob/v2/beat/editor/test/test_libraryeditor.py#L40
[v2] 1 - Edition/Visualization for small editors
Samuel GAIST
Samuel GAIST