beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-11-14T15:58:26Zhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/28License file location is wrong in conda recipe2019-11-14T15:58:26ZAndré AnjosLicense file location is wrong in conda recipeIt should read `LICENSE` instead of `../LICENSE`.
The same should be propagated to all relevant packages.It should read `LICENSE` instead of `../LICENSE`.
The same should be propagated to all relevant packages.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/538Moving cronjobs in beat.web to systemd2020-05-13T15:23:23ZAndré AnjosMoving cronjobs in beat.web to systemdI get repeated e-mails every day concerning our BEAT jobs in beat.web. After more than a year, these scripts are pretty stable and it would be nice if we managed to make them **not** report unless there is a problem (exit status != 0).
...I get repeated e-mails every day concerning our BEAT jobs in beat.web. After more than a year, these scripts are pretty stable and it would be nice if we managed to make them **not** report unless there is a problem (exit status != 0).
In our internal webserver, I managed to implement this using systemd (report on failure only).
Could we do the same here? That would avoid the continuous torrent of "successful run" e-mails.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/249Nightlies are failing because of this package's tests2019-11-08T09:20:47ZAndré AnjosNightlies are failing because of this package's testsBoth linux builds are stuck and will stay like this until the timeout:
https://gitlab.idiap.ch/beat/beat.nightlies/pipelines/34701
@flavio.tarsetti: could you please check?Both linux builds are stuck and will stay like this until the timeout:
https://gitlab.idiap.ch/beat/beat.nightlies/pipelines/34701
@flavio.tarsetti: could you please check?Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/issues/90Execute experiment in different environment2019-10-07T13:31:09ZSamuel GAISTExecute experiment in different environmentCurrently, when executing an experiment on a local machine, the current environment is used and therefor must contain all the packages needed.
This is sub-optimal as several different experiences might required different sets of package...Currently, when executing an experiment on a local machine, the current environment is used and therefor must contain all the packages needed.
This is sub-optimal as several different experiences might required different sets of packages.
While this can't be done with the local executor, it can be implemented using the subprocess executor.
The subprocess executor makes call to the scripts needed to run the algorithms/databases processes as would be with the docker executor. This fact can be used to run the scripts from another environment and thus will use the packages available there.
This will also simplify the creation of new execution environment and their transition do docker images.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/27Improve loop evaluator synchronized write2019-10-01T10:08:15ZSamuel GAISTImprove loop evaluator synchronized writeThe loop evaluator write method is call once per output write. However, a processor block may have several outputs which means that the evaluator write method will be called as many times as an output is written. So in the case of a sequ...The loop evaluator write method is call once per output write. However, a processor block may have several outputs which means that the evaluator write method will be called as many times as an output is written. So in the case of a sequential processor algorithm with 2 outputs and 3 input data, the evaluator write method will be call 6 times.
After talking with @andre.anjos, the current solution proposed is to add the output name written to as a parameter of the evaluator write method so that the developer can chose on which one he wants to "synchronize" the evaluator output.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/26Validation fails with utf-8 error2019-09-25T09:25:30ZSamuel GAISTValidation fails with utf-8 errorUnder some circumstances the values sent for validation may trigger an "utf-8" decoding error.
This comes from the fact that all zmq packets received are decoded before being passed to the callbacks corresponding to the received command...Under some circumstances the values sent for validation may trigger an "utf-8" decoding error.
This comes from the fact that all zmq packets received are decoded before being passed to the callbacks corresponding to the received command.
The solution here is to pass the received data as is to the callbacks and they are responsible for decoding the data if needed.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/89Improve output error messages2019-10-04T08:44:08ZSamuel GAISTImprove output error messagesWhen 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/537Implement experiment reset API2019-09-09T16:21:29ZSamuel GAISTImplement experiment reset APICurrently, 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#62Currently, 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#62Samuel 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.web/-/issues/535Sphinxcontrib-openapi does not render response json objects for api in the do...2019-09-05T12:39:23ZZohreh MOSTAANISphinxcontrib-openapi does not render response json objects for api in the documentationThe 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 MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/534Needs beat-devel update2019-08-29T13:39:14ZAndré AnjosNeeds beat-devel updateCould 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 GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/87Remove parameters from analyzer block2019-08-19T19:15:28ZSamuel GAISTRemove parameters from analyzer blockCurrently 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 definitionSoft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/247Sphinx errors during nightly builds2019-08-12T07:13:09ZAndré AnjosSphinx errors during nightly buildsThe 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 TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/issues/86Loop parts name2019-07-31T08:30:04ZSamuel GAISTLoop parts nameBased 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 loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/85Synchronised input for loop blocks2019-07-30T12:56:03ZSamuel GAISTSynchronised input for loop blocksCurrently 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 loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/84Implement output for loop block2019-07-30T07:15:14ZSamuel GAISTImplement output for loop blockCurrently 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 loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/246Correct base types management in AssetModel2020-08-10T08:39:27ZSamuel GAISTCorrect base types management in AssetModelSummary
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 editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/245Improve error handling2019-12-11T09:57:48ZSamuel GAISTImprove error handlingSummary
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 editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/243There is no way to close an asset without opening another one.2020-08-10T15:27:51ZZohreh MOSTAANIThere 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/242Delete button does not ask for confirmation if you are deleting an asset that...2019-10-04T15:12:53ZZohreh MOSTAANIDelete 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).