beat.editor issueshttps://gitlab.idiap.ch/beat/beat.editor/-/issues2020-10-20T08:18:02Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/281Reports editor2020-10-20T08:18:02ZSamuel GAISTReports editorThis issue tracks the implementation of the reports feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to create reports from the editor as well as manage the different related actions from the...This issue tracks the implementation of the reports feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to create reports from the editor as well as manage the different related actions from there.
See beat/beat.web%"Read-only platform"Online feature editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/280Attestation editor2020-10-20T08:18:08ZSamuel GAISTAttestation editorThis issue tracks the implementation of the attestation feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to directly manage attestations from the editor.
See beat/beat.web%"Read-only platform"This issue tracks the implementation of the attestation feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to directly manage attestations from the editor.
See beat/beat.web%"Read-only platform"Online feature editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/279Search editor2020-10-20T08:18:16ZSamuel GAISTSearch editorThis issue tracks the implementation of the search feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to directly manage searches from the editor and manipulate them there.
See beat/beat.web%...This issue tracks the implementation of the search feature of the platform inside beat/beat.editor>.
The goal of this feature is to allow people to directly manage searches from the editor and manipulate them there.
See beat/beat.web%"Read-only platform"Online feature editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/274Keep a history of selected Algorithms and datasets around in the toolchain2022-03-04T09:39:05ZAmir MOHAMMADIKeep a history of selected Algorithms and datasets around in the toolchainSummary
With the new editor, it's only possible to add blocks based on available datasets, algorithms, and analyzers. Which might be a good thing according to #265.
Also, once blocks are added (according to the algorithm or dataset it w...Summary
With the new editor, it's only possible to add blocks based on available datasets, algorithms, and analyzers. Which might be a good thing according to #265.
Also, once blocks are added (according to the algorithm or dataset it was selected from), it is no longer associated with the block that it was chosen from.
This makes sense because as far as the toolchain is concerned, this association is irrelevant and this association is kept around in the experiment definition.
However, I think it makes sense to keep association around in the toolchain. Doing so can let us:
- Provide hints to the user (reminding them what algorithm that block was) so that they have to memorize less when designing the toolchain.
- Automatically figure out the channel of blocks as disccussed in #272.
On the other hand, we want to merge the toolchain/experiment definitions per https://gitlab.idiap.ch/beat/beat.core/-/issues/88
So maybe this issue must be looked at when that works is already done?!https://gitlab.idiap.ch/beat/beat.editor/-/issues/273Right-click actions on the blocks in the toolchain editor2022-03-04T09:38:51ZAmir MOHAMMADIRight-click actions on the blocks in the toolchain editorHere is my suggestion:
* Upon right clicking on the blocks, provide a list of actions.
* A `Delete` action
* A `Edit` or `Properties` action that does the same thing as double clickingHere is my suggestion:
* Upon right clicking on the blocks, provide a list of actions.
* A `Delete` action
* A `Edit` or `Properties` action that does the same thing as double clickinghttps://gitlab.idiap.ch/beat/beat.editor/-/issues/272Automatic inference of synchronization channels when drawing the toolchain2022-03-04T09:38:31ZAmir MOHAMMADIAutomatic inference of synchronization channels when drawing the toolchainSummary
When drawing several blocks in the toolchain and connecting inputs and outputs, the (synchronization) channel for blocks are not automatically determined even though most of the time there is only one option.
See the video below...Summary
When drawing several blocks in the toolchain and connecting inputs and outputs, the (synchronization) channel for blocks are not automatically determined even though most of the time there is only one option.
See the video below where I have to select the channel in all blocks before getting a valid toolchain:
![synchronization_channels_not_selected_automatically](/uploads/75d3cce295e08c2515f69ace8c2810b8/synchronization_channels_not_selected_automatically.webm)
It would be beneficial if the toolchain editor would infer and select the channel for me as I edit along.
Why is it needed ?
It would make editing toolchains simpler as I will not have to go into each block and edit them one by one.https://gitlab.idiap.ch/beat/beat.editor/-/issues/228Feature request: Be able to have multi window open2020-02-12T12:42:39ZZohreh MOSTAANIFeature request: Be able to have multi window openIt would be nice if you are able to have multiple assets open at the same time, since sometimes you may need it.
There are to options here:
1. Having multiple windows open in the same instance of editor. Kind of just splitting the edit...It would be nice if you are able to have multiple assets open at the same time, since sometimes you may need it.
There are to options here:
1. Having multiple windows open in the same instance of editor. Kind of just splitting the editor window.
2. Having a new instance of editor opened from terminal. In this case there might be complications with the log info shown in the terminal. The question is are they useful for user or not?https://gitlab.idiap.ch/beat/beat.editor/-/issues/217Update editor needing complex type support2020-02-12T13:15:12ZSamuel GAISTUpdate editor needing complex type supportThe latest version of beat/beat.core> following beat/beat.core!65 doesn't contain complex types anymore as they are specific to the Dataformat asset.
The DataformatEditor must be updated to handle that change.The latest version of beat/beat.core> following beat/beat.core!65 doesn't contain complex types anymore as they are specific to the Dataformat asset.
The DataformatEditor must be updated to handle that change.[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/216Update basetype getter2020-02-12T13:14:31ZSamuel GAISTUpdate basetype getterbeat/beat.core!65 modifies heavily the schema to be more accurate.
The basetype definition changes in that regards and the current setter doesn't support it yet.beat/beat.core!65 modifies heavily the schema to be more accurate.
The basetype definition changes in that regards and the current setter doesn't support it yet.[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/196rearrange the inputs in a toolchain block2020-06-16T16:03:32ZZohreh MOSTAANIrearrange the inputs in a toolchain blockIt would be very useful if the user is able to reorder the inputs when they are defined in a block. Sometimes you may just make a block with the inputs but it will be easier to connect them to other blocks if they were in another order. ...It would be very useful if the user is able to reorder the inputs when they are defined in a block. Sometimes you may just make a block with the inputs but it will be easier to connect them to other blocks if they were in another order. This is different from renaming though.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/193breaking connections in a toolchain to by pass the blocks2020-02-12T12:52:21ZZohreh MOSTAANIbreaking connections in a toolchain to by pass the blocksI think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even tho...I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even though it is more convenient while making a toolchain to just connect an output to an input it is very difficult to understand what is going on when you look at an experiment using that toolchain, specially when the experiments get bigger and the connections are crossing each other. Even if there was a mechanism to highlight a chosen connection in the experiment page can be really helpful. This mechanism is already there when making a toolchain but not when you look at the experiment.[v2] 2 - Toolchain editor