beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2020-05-28T10:57:29Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/239Library editor forces a dump of an optional key "uses:{}" for the available l...2020-05-28T10:57:29ZFlavio TARSETTILibrary 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 editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/100Backend/scheduler administration page improvements2020-08-03T08:41:33ZAndré AnjosBackend/scheduler administration page improvementsA small list of improvements for the backend/scheduler page:
1. The worker listing takes too much space and does not allow for the visualisation of important information. It would be better to transform it into a table, in which each ...A small list of improvements for the backend/scheduler page:
1. The worker listing takes too much space and does not allow for the visualisation of important information. It would be better to transform it into a table, in which each line corresponds to a host and each column shows the following information: IP address, cores (in-use/available), memory (in-use/available), beat.scheduler version. The color of the line can be color coded: light green means 100% free, light read means 100% occupied, light yellow means partially occupied.
2. The total number of cores affected to a queue should be displayed
3. The queue listing should also become a table with more compact information displayed.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/240ParameterWidget needs better size handling2019-07-02T08:56:34ZSamuel GAISTParameterWidget needs better size handlingSummary
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 editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/231CodeMirror update and goodies2015-07-29T09:07:30ZAndré AnjosCodeMirror update and goodiesThe newest versions of CodeMirror should allow for us to automatically replace Tab by 4 spaces on any editor, following a quick recipe: http://stackoverflow.com/questions/15183494/codemirror-tabs-to-spaces
It would be good if we could...The newest versions of CodeMirror should allow for us to automatically replace Tab by 4 spaces on any editor, following a quick recipe: http://stackoverflow.com/questions/15183494/codemirror-tabs-to-spaces
It would be good if we could also:
- [ ] Visualize/Differentiate Tabs and Spaces
- [ ] Visualize trailing whitespaces
BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/241Make the size of the dialogue boxes changable2020-02-26T11:01:22ZZohreh MOSTAANIMake the size of the dialogue boxes changableWhen 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 TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/64Possibility to reset a failed experiment2014-12-02T11:54:03ZAndré AnjosPossibility to reset a failed experimentIt would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. Fo...It would be nice to be able to "reset" failed experiment, from the experiment result page. There are situations where you make wrong choices of parameters or queues for an experiment and you want to fix this - not fork the experiment. For those situations, the user may reset the experiment, which would take him to the configuration page again.
The experiment model class in our Django app already supports the "reset()" functionality, which is successfuly used in the admin page already. This ticket is only about hooking in the possibility to reset from the result page itself.Second BEAT ReviewPhilip ABBETPhilip ABBEThttps://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).https://gitlab.idiap.ch/beat/beat.web/-/issues/291[experiments] Experiment was shared, together with toolchain, but configurato...2015-09-08T01:51:44ZAndré Anjos[experiments] Experiment was shared, together with toolchain, but configurator refuses to use itFor example, this experiment was shared with the team system/administrators:
https://www.beat-eu.org/platform/experiments/setup/chichan/chichan/full_mlbphs/1/MLBPH_comp7/
As you can see, if you try to fill-in the label and then pre...For example, this experiment was shared with the team system/administrators:
https://www.beat-eu.org/platform/experiments/setup/chichan/chichan/full_mlbphs/1/MLBPH_comp7/
As you can see, if you try to fill-in the label and then press the Go button, the configurator refuses to submit the experiment saying the toolchain is not public.
The expected behaviour is that it allows us to run the experiment, given the toolchain is also shared with us:
https://www.beat-eu.org/platform/admin/toolchains/toolchain/213/?_changelist_filters=q%3Dchichan
BTAS TutorialSamuel GAISTSamuel GAISThttps://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.web/-/issues/104Public algorithms are not being listed2015-04-10T10:08:24ZAndré AnjosPublic algorithms are not being listedIn the user microsite, the others' public algorithms available are not being displayed. Need a fix.In the user microsite, the others' public algorithms available are not being displayed. Need a fix.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/244Improve plotter new creation handling2019-10-04T15:12:49ZSamuel GAISTImprove plotter new creation handlingSummary
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 editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/179Search: Display multiple tables for experiments with multiple analyzers2015-06-16T13:44:36ZPhilip ABBETSearch: Display multiple tables for experiments with multiple analyzersDepends on #178
Depends on #178
BTAS TutorialPhilip ABBETPhilip ABBEThttps://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.web/-/issues/52Failed experiment scheduling from user page results in "private" icon being s...2014-10-20T09:08:33ZAndré AnjosFailed experiment scheduling from user page results in "private" icon being shownIf I try to start an experiment from the user micro-site, by clicking on the "play" button on any pending experiment and, at this time, the scheduler is not available for running the experiment, a window pops-up telling me the reason of ...If I try to start an experiment from the user micro-site, by clicking on the "play" button on any pending experiment and, at this time, the scheduler is not available for running the experiment, a window pops-up telling me the reason of the failure. All this is good, the problem comes after I dismiss the window: the experiment icon goes from the "play" button to the "lock" icon, indicating the experiment is now private. Since the experiment did not run, this should not happen. The play button should remain available so the user can try again later.
Note: Reloading the user micro-site seems to "fix" the problem, making me believe this is just a javascript error.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://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.web/-/issues/38Deleting a connection on a Macbook requires Fn-Delete2017-08-23T11:36:31ZAndré AnjosDeleting a connection on a Macbook requires Fn-DeleteIt would be nice if the Delete button was honoured properly.It would be nice if the Delete button was honoured properly.Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://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.web/-/issues/233Error requesting an attestation2015-07-29T15:25:38ZSébastien MARCELError requesting an attestationI forked the experiment from this attestation
https://www.beat-eu.org/platform/attestations/1839141191/
to
https://www.beat-eu.org/platform/experiments/smarcel/aythamimm/btas15_keystroke_experiments/6/Keystroke_Experiment-rr2/
and fa...I forked the experiment from this attestation
https://www.beat-eu.org/platform/attestations/1839141191/
to
https://www.beat-eu.org/platform/experiments/smarcel/aythamimm/btas15_keystroke_experiments/6/Keystroke_Experiment-rr2/
and failed to request an attestation to this one. I got a popup message "Error: Forbidden" !
BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/248QMenu for push button lifetime issue2019-10-02T12:00:49ZSamuel GAISTQMenu for push button lifetime issueSummary
While doing tests to check whether PySide2 could be used, an issue has been found with the handling of QMenu when used in a helper function to generate a QPushButton, the related QMenu and QActions.
On return of the method, th...Summary
While doing tests to check whether PySide2 could be used, an issue has been found with the handling of QMenu when used in a helper function to generate a QPushButton, the related QMenu and QActions.
On return of the method, the QMenu object is destroyed with PySide2 while not with PyQt5.
This is likely related to the fact that QPushButton::setMenu does not take ownership of the QMenu. So it likely is garbage collected at the end of the method.
Steps to reproduce
```
import sys
from PySide2.QtWidgets import QApplication
from PySide2.QtWidgets import QAction
from PySide2.QtWidgets import QMenu
from PySide2.QtWidgets import QPushButton
def build_button_with_menu():
button = QPushButton("The button")
menu = QMenu("The menu")
button.setMenu(menu)
action = menu.addAction("The action")
return button, action
app = QApplication(sys.argv)
button, action = build_button_with_menu()
action.triggered.connect(app.quit)
sys.exit(app.exec_())
```
What is the current bug behavior?
This will trigger a property error saying that triggered has no connect property.
Checking the action itself will show the correct type but the signal object related methods will be missing.
What is the expected correct behavior?
No error, the connection gets created, the button is shown and when clicking on the action, the application should stop.
Possible fixes
The fix is to give the QMenu a parent, in this case, the button itself, so its lifetime doesn't end with the end of the method.[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/578Removed edition related documentation2020-10-06T09:54:56ZSamuel GAISTRemoved edition related documentationAs part of %"Read-only platform" the documentation related to the online edition of BEAT assets must be removed.As part of %"Read-only platform" the documentation related to the online edition of BEAT assets must be removed.Read-only platformSamuel GAISTSamuel GAIST