beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-05-28T14:45:18Zhttps://gitlab.idiap.ch/beat/beat.examples/-/issues/14Wrong algorithm V1 parameters value in declaration2019-05-28T14:45:18ZSamuel GAISTWrong algorithm V1 parameters value in declarationFollowing the development of beat/beat.core!65, it has been discovered that part of the v1 algorithms provided by this repository have an issue: some of their numerical parameters have their default value stored as string rather than num...Following the development of beat/beat.core!65, it has been discovered that part of the v1 algorithms provided by this repository have an issue: some of their numerical parameters have their default value stored as string rather than number.
This was fixed by !19 and !20 however, taking into account that the live platform has already some experiment that ran using these algorithm, updating them will break the cache (which in itself is not an issue) but also would require to re-run certified experiment which is a no-go.
The decided course of action is the following:
- Reverse !19
- Reverse the last fixes done in !20
- Implement a fully self-contained algorithm version 1 schema (done in beat/beat.core!65)
This will allow to have algorithm using still using the V1 left untouched while enforcing the correct data types for newer algorithms.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/524[reports] Text toggle source view required ?2019-05-20T13:48:42ZFlavio TARSETTI[reports] Text toggle source view required ?***Issue explanation:***
In a locked report
![image](/uploads/56aee3a68defa18eb0fd79431b541966/image.png)
Why is it possible to toggle the source view of the text ?
***Expected behavior:***
The toggle for the text shouldn't be there...***Issue explanation:***
In a locked report
![image](/uploads/56aee3a68defa18eb0fd79431b541966/image.png)
Why is it possible to toggle the source view of the text ?
***Expected behavior:***
The toggle for the text shouldn't be there.
I understand that for the table above we wanted to give the opportunity to toggle the csv view so a `reviewer` can easily get his data from there, but for the text data, I don't understand the purpose.
Was it something you asked for @andre.anjos ?https://gitlab.idiap.ch/beat/beat.web/-/issues/522[reports] Wrong URL when adding experiments to reports on the production plat...2019-05-17T12:52:47ZFlavio TARSETTI[reports] Wrong URL when adding experiments to reports on the production platform***Issue explanation:***
When going to the experiments page and adding experiments to a report from there:
The pop-up asks if we wish to go to the report with a button `View Report`
When clicking on that button, we are then sent to th...***Issue explanation:***
When going to the experiments page and adding experiments to a report from there:
The pop-up asks if we wish to go to the report with a button `View Report`
When clicking on that button, we are then sent to the page `https://www.beat-eu.org/platform/platform/reports/<username>/<report>/`
- gives a *404* page not found
- we have one extra platform in it.
***Expected behavior:***
We should be sent to `https://www.beat-eu.org/platform/reports/<username>/<report>/`Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/523[reports] Figure name is wrong2019-05-15T06:01:49ZFlavio TARSETTI[reports] Figure name is wrong***Issue explanation:***
When downloading a figure (png, jpg, pdf) from a report, the naming is wrong. This issue was introduced with the `group` done last year:
The name of the figure is:
* `groupname_plot_0-plot_0`
***Expected behavi...***Issue explanation:***
When downloading a figure (png, jpg, pdf) from a report, the naming is wrong. This issue was introduced with the `group` done last year:
The name of the figure is:
* `groupname_plot_0-plot_0`
***Expected behavior:***
Why is it doubled ? Whe should have `groupname-plot_0` onlyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/24Assert usage cleanup2019-05-10T08:16:51ZSamuel GAISTAssert usage cleanupFollowing bandit warning about usage of assert in code, this issue is used to track down the cleanup of these statements found in beat.backend.python.
Relates to beat/beat.core#72Following bandit warning about usage of assert in code, this issue is used to track down the cleanup of these statements found in beat.backend.python.
Relates to beat/beat.core#72Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/10infinite scrolling2019-05-09T12:54:27ZJaden DIEFENBAUGHinfinite scrollinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/199Project Bandit settings & assert statements2019-05-09T12:52:53ZJaden DIEFENBAUGHProject Bandit settings & assert statementsShould we not be using assert statements to make runtime checks to make sure things are working properly behind the scenes? From what I understood, that's what we were supposed to use in Python, but the current settings for python-bandit...Should we not be using assert statements to make runtime checks to make sure things are working properly behind the scenes? From what I understood, that's what we were supposed to use in Python, but the current settings for python-bandit flags all assert statements ([B101](https://docs.openstack.org/bandit/latest/plugins/b101_assert_used.html) is active)Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/210Protocol Template Editor2019-05-09T12:25:48ZSamuel GAISTProtocol Template EditorThis issue tracks the progress on the Protocol Template editorThis issue tracks the progress on the Protocol Template editor[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/61Make Plotterparameter properly supported2019-05-08T08:54:29ZSamuel GAISTMake Plotterparameter properly supportedPlotterparameter also has a storage supporting it.
Update beat.cmdline to properly support it.Plotterparameter also has a storage supporting it.
Update beat.cmdline to properly support it.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/23Improve storage classes2019-05-08T08:53:02ZSamuel GAISTImprove storage classesThe Storage and CodeStorage classes share a parallel goals, part of their code is exactly the same yet they are two distinct classes.
Fix this by creating a common base class so they share the configuration member variable and their check.The Storage and CodeStorage classes share a parallel goals, part of their code is exactly the same yet they are two distinct classes.
Fix this by creating a common base class so they share the configuration member variable and their check.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/81Nightlies are failing because of this package2019-05-07T14:33:40ZAndré AnjosNightlies are failing because of this packageThere are tests in the nightlies that are currently failing. Not sure these are due to the update of jsonschema to 3.0.1 (may be enforcing something that was not enforced before?)
@samuel.gaist: could you please have a look?
Examples:...There are tests in the nightlies that are currently failing. Not sure these are due to the update of jsonschema to 3.0.1 (may be enforcing something that was not enforced before?)
@samuel.gaist: could you please have a look?
Examples:
https://gitlab.idiap.ch/beat/beat.nightlies/pipelines/29971Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/79Implement missing prototypes2019-05-07T10:47:47ZSamuel GAISTImplement missing prototypesSome assets currently don't have prototypes and therefor cannot be created from scratch.
This issue tracks the implementation for them.
Currently needed:
- [x] Database
- [x] Experiment
Note that experiment can't be created from scrat...Some assets currently don't have prototypes and therefor cannot be created from scratch.
This issue tracks the implementation for them.
Currently needed:
- [x] Database
- [x] Experiment
Note that experiment can't be created from scratch so this use case is unsupported and should properly triggers an exception.
An experiment is based on a toolchain. Therefor providing a "prototype" doesn't make sense as its content would depend on what is available in the prefix. Also the person getting that "prototype" would first have to clear everything before it can start configuring the experiment as they would like.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/80`jsonschema` & `beat-devel` version conflicts2019-05-07T08:40:22ZJaden DIEFENBAUGH`jsonschema` & `beat-devel` version conflictsI might have figured out the CI issues...specifying the new `jsonschema` version requirement in `conda/meta.yaml` conflicts with `beat-devel`:
```
UnsatisfiableError: The following specifications were found to be in conflict:
- beat-de...I might have figured out the CI issues...specifying the new `jsonschema` version requirement in `conda/meta.yaml` conflicts with `beat-devel`:
```
UnsatisfiableError: The following specifications were found to be in conflict:
- beat-devel=2019.04.30 -> jsonschema==2.6.0=py36h006f8b5_0
- jsonschema[version='>=3.0.0']
```
Do we need to restrict `jsonschema` to 2.6.0 in beat-devel, or can we bump it to 3.x?André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/78Plotterparameter saving is not operational2019-05-06T13:35:08ZSamuel GAISTPlotterparameter saving is not operationalCurrently the implementation of the writing of a Plotterparameter can succeed.
The implementation is wrong and there are elements of the class that are missing.Currently the implementation of the writing of a Plotterparameter can succeed.
The implementation is wrong and there are elements of the class that are missing.Soft loopsSamuel 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/211Larger uint32 types spin boxes2019-04-25T10:25:21ZFlavio TARSETTILarger uint32 types spin boxesQt doesn't provide spin boxes for types like uint32.
The beat.editor needs them for example for algorithm parameters.
This issue is to track the advancement on this.Qt doesn't provide spin boxes for types like uint32.
The beat.editor needs them for example for algorithm parameters.
This issue is to track the advancement on this.[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/22Update schema tests to conform to beat.core!652019-04-25T07:08:43ZJaden DIEFENBAUGHUpdate schema tests to conform to beat.core!65The algorithm/plotter schemas have been refined in beat.core!65 to more closely reflect the actual restrictions of these object types. This means that some valid metadata tests are now invalid, and needs to be updated.
This is blocking ...The algorithm/plotter schemas have been refined in beat.core!65 to more closely reflect the actual restrictions of these object types. This means that some valid metadata tests are now invalid, and needs to be updated.
This is blocking beat.core!65 (see the [note about the failing test](https://gitlab.idiap.ch/beat/beat.core/merge_requests/65#note_41115) for info on how this was found)Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.core/-/issues/66The plotterparameter type doesn't have a JSON schema file2019-04-18T22:25:57ZJaden DIEFENBAUGHThe plotterparameter type doesn't have a JSON schema fileNot sure what happened but we need one, right?
I found this out by working on https://gitlab.idiap.ch/beat/beat.editor/issues/161Not sure what happened but we need one, right?
I found this out by working on https://gitlab.idiap.ch/beat/beat.editor/issues/161Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/20Implement protocol templates2019-04-18T09:59:31ZSamuel GAISTImplement protocol templatesFollowing beat/beat.core#64 this issue tracks the implementation here for the support of the ProtocolTemplate object which will represent a database template.
The end goal is to make protocol template re-usable objects to avoid duplicat...Following beat/beat.core#64 this issue tracks the implementation here for the support of the ProtocolTemplate object which will represent a database template.
The end goal is to make protocol template re-usable objects to avoid duplication and therefore potential errors in the database definitions.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/521Add BEAT classifier to setup.py2019-04-11T08:58:54ZSamuel GAISTAdd BEAT classifier to setup.pyThe classifier has been added to Pypi so it now can be used.
See beat/beat.backend.python#19The classifier has been added to Pypi so it now can be used.
See beat/beat.backend.python#19