beat.editor issues
https://gitlab.idiap.ch/beat/beat.editor/-/issues
2019-06-25T09:28:05Z
https://gitlab.idiap.ch/beat/beat.editor/-/issues/213
Plotter Parameter issue on creation
2019-06-25T09:28:05Z
Flavio TARSETTI
Plotter 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 ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/187
cross-tab-sync branch still active?
2018-12-20T18:45:18Z
André Anjos
cross-tab-sync branch still active?
This branch is now stale, w/o any further development.
@jdiefenbaugh: please delete it if no longer needed.
This branch is now stale, w/o any further development.
@jdiefenbaugh: please delete it if no longer needed.
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/176
toolchain naming
2019-02-07T15:06:01Z
Flavio TARSETTI
toolchain naming
During our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect...
During our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect is that adding multiples inputs shouldn't overwrite the previous input names.
@jdiefenbaugh : Can you fix this please? Thanks.
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/174
JSON schema duplication
2019-03-07T21:13:26Z
Samuel GAIST
JSON schema duplication
The files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
-...
The files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
- The folder content is not even a copy of the beat.core content so they are currently different
- New versions of the schema are not available
The only official schemas are the ones from beat.core. Those must be used and not copied.
Relates to #140
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/145
New algorithms should come with an input & output in the first group
2019-02-26T09:51:19Z
Jaden DIEFENBAUGH
New algorithms should come with an input & output in the first group
Pretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the user
Pretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the user
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/140
Update Algorithm schema (and editor?)
2019-02-26T18:00:07Z
Jaden DIEFENBAUGH
Update Algorithm schema (and editor?)
As of https://gitlab.idiap.ch/beat/beat.core/merge_requests/31#note_33390 , the algorithm schema in beat.core has been updated. Depending on the schema changes, there might need to be editor changes as well...
As of https://gitlab.idiap.ch/beat/beat.core/merge_requests/31#note_33390 , the algorithm schema in beat.core has been updated. Depending on the schema changes, there might need to be editor changes as well...
[v1] Ongoing patching until [v2] is ready