Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.editor
beat.editor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.editorbeat.editor
  • Issues
  • #274

Closed
Open
Opened Jun 24, 2020 by Amir MOHAMMADI@amohammadi
  • Report abuse
  • New issue
Report abuse New issue

Keep a history of selected Algorithms and datasets around in the toolchain

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 (closed). 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?!

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
2
Labels
enhancement suggestion
Assign labels
  • View project labels
Reference: beat/beat.editor#274