beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-05-17T12:52:47Zhttps://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.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/214Documentation contribute.rst for local dependencies and running unit tests ag...2019-10-04T15:12:53ZFlavio TARSETTIDocumentation contribute.rst for local dependencies and running unit tests against themSummary
The documentation does not provide the steps to build local dependencies and run the tests against themSummary
The documentation does not provide the steps to build local dependencies and run the tests against them[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://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.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.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/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/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.cmdline/-/issues/60Add support for protocol template2019-05-08T09:45:49ZSamuel GAISTAdd support for protocol templateFor database v2, the new protocol template object has been created (see beat/beat.core#64, beat/beat.core!67, and beat/beat.core!71).
This issue tracks adding support for it in beat/beat.cmdline>
Todo:
- [x] Local support
- [ ] Remote ...For database v2, the new protocol template object has been created (see beat/beat.core#64, beat/beat.core!67, and beat/beat.core!71).
This issue tracks adding support for it in beat/beat.cmdline>
Todo:
- [x] Local support
- [ ] Remote supportSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/213Plotter Parameter issue on creation2019-06-25T09:28:05ZFlavio TARSETTIPlotter Parameter issue on creation**Summary**
The plotterparameter editor on beat.editor is not consistent with the behavior we have on the web platform. It doesn't save the changes but all the fields from the plotter it targets.
**Steps to reproduce**
When creating a...**Summary**
The plotterparameter editor on beat.editor is not consistent with the behavior we have on the web platform. It doesn't save the changes but all the fields from the plotter it targets.
**Steps to reproduce**
When creating a new plotter parameter, **ONLY** the updated parameters from the plotter should be saved in the `json`, **not everything**.
Each time an entry is modified, it's added to the json data of the plotterparameter. Unchanged values shouldn't be updated and saved if they were never touched.
**What is the current bug behavior?**
All parameters from the plotter get saved to the newly created plotterparameter.
**What is the expected correct behavior?**
They should be shown visually without being saved in the json data file
**Relevant logs and/or screenshots**
Please have a look on the beat web platform for a better understanding of the problem
`This is what is shown on screen after creation and during edition:`
![plotterparameter_test_shown_1](/uploads/170dbbf47a4825da12d183dbb611d580/plotterparameter_test_shown_1.png)
![plotterparameter_test_shown_2](/uploads/c22520078288c6e2fd89b386d4e5a9c3/plotterparameter_test_shown_2.png)
`This is what is saved after update on one field:`
![plotterparameter_test](/uploads/634b95fc785b1cf9655c0045d58f1f26/plotterparameter_test.png)
`This is what we have after creation or small update on one field on beat.editor:`
![plotterparameter_beat_editor](/uploads/215b46102267f5a9278504f71de9feab/plotterparameter_beat_editor.png)
**Possible fixes**
Having a signal that checks which parameter field has been updated[v1] Ongoing patching until [v2] is readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/212Generic Spinbox targetting int/uint (8,16,32,64) and float (32,64) numpy types2019-10-04T15:12:53ZFlavio TARSETTIGeneric Spinbox targetting int/uint (8,16,32,64) and float (32,64) numpy typesThis issue tracks the progress on the Generic Spinbox targetting int/uint (8,16,32,64) and float (32,64) numpy typesThis issue tracks the progress on the Generic Spinbox targetting int/uint (8,16,32,64) and float (32,64) numpy typesFlavio TARSETTIFlavio TARSETTIhttps://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.core/-/issues/76Clean up the schemas2019-06-02T02:18:24ZJaden DIEFENBAUGHClean up the schemas(@samuel.gaist this is the issue for our email discussion)
Both !55 and !65 showed that there were places to improve the schema. This issue expands on those MRs' work by using the v6/v7 json schema features (where appropriate) and addin...(@samuel.gaist this is the issue for our email discussion)
Both !55 and !65 showed that there were places to improve the schema. This issue expands on those MRs' work by using the v6/v7 json schema features (where appropriate) and adding tests to complicated parts of the schema. Right now I know of a couple of things that need to be done:
- [x] Use the `const` schema keyword instead of the `enum` with only one choice. This issue is documented in the schema, e.g. in beat.core/beat/core/schema/algorithm/3.json:
```json
115- "type": {
116: "$comment": "Change enum to const when tools allow v6 json schema",
117- "type": "string",
118- "enum": ["loop_user"]
119- }
--
144- "type": {
145: "$comment": "Change enum to const when tools allow v6 json schema",
146- "type": "string",
147- "enum": ["loop"]
148- }
```
- [ ] Use the `if`/`then`/`else` keywords from json schema v7 to represent more complex logic (e.g. the changes to algorithm parameters in !65)
- As found in !65, there are parts of the schema that aren't tested thoroughly. This is nebulous issue, however, so @flavio.tarsetti @samuel.gaist could you maybe specify what I should do here, so I don't go off the rails?
(As other issues are isolated, I'll add them to the list)Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://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.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#19https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/58Add BEAT classifier to setup.py2019-04-11T08:58:40ZSamuel 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#19https://gitlab.idiap.ch/beat/beat.core/-/issues/75Add BEAT classifier to setup.py2019-04-11T07:39:47ZSamuel 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#19https://gitlab.idiap.ch/beat/beat.backend.python/-/issues/21Add BEAT classifier to setup.py2019-04-11T08:58:17ZSamuel GAISTAdd BEAT classifier to setup.pyThe classifier has been added to Pypi so it now can be used.
See #19The classifier has been added to Pypi so it now can be used.
See #19https://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 GAIST