beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-12-19T19:02:44Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/135Algorithms made with a group & no group names!2018-12-19T19:02:44ZJaden DIEFENBAUGHAlgorithms made with a group & no group names!The group names shouldnt be shown/editable by usersThe group names shouldnt be shown/editable by usersMiscellaneous Editor-specific Improvementshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/134Implement cache (save/cancel options) for block editor2018-12-19T19:02:44ZJaden DIEFENBAUGHImplement cache (save/cancel options) for block editorToolchain Editor: UX Improvementshttps://gitlab.idiap.ch/beat/beat.core/-/issues/59Tight "soft-loops" controlling algorithmic training2020-11-04T17:09:18ZAndré AnjosTight "soft-loops" controlling algorithmic trainingIn the context of the ALLIES project, a so-far-avoided requirement has popped up again the meeting: block loops.
I created this bug to differentiate from #29, because the requirements here are a bit different: in the use-case to be cons...In the context of the ALLIES project, a so-far-avoided requirement has popped up again the meeting: block loops.
I created this bug to differentiate from #29, because the requirements here are a bit different: in the use-case to be considered, platform users need to be able to train a model depending on the output of another block. The main research question of the project needs to answer is: is it possible to implement life-long learning systems (LLLS) that can be taught by a human and improve over time? The outcome of the project must be reproducible (therefore our involvement).
In order to simulate this, partners provided the following diagram:
![modes](/uploads/a4e1aa953cd2bced7fa834da5d300e63/modes.png)
On the left, you'll see conventional ways to "adapt" statistical models from new input data. Given the model and more data, the model can be adapted to new incoming information (a.k.a. "source" in these diagrams).
In the context of ALLIES, partners want to have reproducible toolchains that allow third-parties to create the training system on the right of this image. In this context, the yellow boxes under the "training" (cyan) boxes simulate a human-user interaction with the system. E.g.: it could be a human telling a machine translation system the translation of a sentence (or paragraph) needs to be corrected, alongside with the correction, or it could be a human telling a speaker diarization system that a certain segment belongs to a different speaker. Because humans have limited ability to provide corrections, the consortium wants to control the implementation and limits of the "yellow" boxes, while third-parties implement the "trainers" that go into the cyan boxes.
It is possible to "unroll" these loops for practical scenarios, but in order to test limits of LLLS, one can envisage hundreds if not thousand iterations which is not very practical to code in BEAT as of today.
One of the key questions while considering #29 was that of the cache: a system that loops will issue multiply different cache outputs which, using the current architecture, would have to be kept. In this new use-case, such a caching requirement is not present. Partners only want to ensure that the code in "yellow" boxes can be properly tagged by the consortium and that they can conduct searches and build leaderboards on experiments using those (and only those). This prevents implementors of the "cyan" training boxes to misinterpret the role and data from the simulated human (yellow boxes). As a consequence, **no caching is required within this loop**.Soft loopshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/133tell the user why objects are invalid2020-02-12T13:06:14ZJaden DIEFENBAUGHtell the user why objects are invalidthis is super hazy and possibly very complicatedthis is super hazy and possibly very complicatedhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/132graphviz dot: require space between blocks2018-12-19T19:02:44ZJaden DIEFENBAUGHgraphviz dot: require space between blocksThey can be touching - not goodThey can be touching - not goodToolchain Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/131Weird edgecases with toolchain validity2018-12-19T19:02:44ZJaden DIEFENBAUGHWeird edgecases with toolchain validityRarely it seems that a toolchain is valid but somehow it's not...
will hopefully probably be fixed by the refactoring & test fixingRarely it seems that a toolchain is valid but somehow it's not...
will hopefully probably be fixed by the refactoring & test fixingToolchain Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/130Don't allow dashes in names2018-12-19T19:02:44ZJaden DIEFENBAUGHDon't allow dashes in namesIt breaks alot of stuffIt breaks alot of stuffToolchain Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/129Block editor should allow switching inputs2018-12-19T19:02:44ZJaden DIEFENBAUGHBlock editor should allow switching inputsThis is a little tricky - say you have two inputs, `input1` and `input2`. Trying to change the first name to `input2` will fail obviously since there's already an `input2`. But you want to switch them. The only solution now is using a 3r...This is a little tricky - say you have two inputs, `input1` and `input2`. Trying to change the first name to `input2` will fail obviously since there's already an `input2`. But you want to switch them. The only solution now is using a 3rd name to switch, but this isn't super logical...
not sure how to fix this.Toolchain Editor: UX Improvementshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/128Dataset blocks should hide/show the same as other blocks2018-12-19T19:02:44ZJaden DIEFENBAUGHDataset blocks should hide/show the same as other blocksDataset blocks always exist at the bottom of the exp editor - they should only pop up if you click a dataset block. But if you click one dataset block, all of them should pop upDataset blocks always exist at the bottom of the exp editor - they should only pop up if you click a dataset block. But if you click one dataset block, all of them should pop upExperiment Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/127Don't remove type inference after an algorithm has been selected for a block2018-12-19T19:02:44ZJaden DIEFENBAUGHDon't remove type inference after an algorithm has been selected for a blockBefore an algorithm is selected, the dropdown menu for algs is filtered via type-inference as it should be. But, after you select an alg and go to select a different one, the type inference filtering is dropped.
Pretty sure I added this...Before an algorithm is selected, the dropdown menu for algs is filtered via type-inference as it should be. But, after you select an alg and go to select a different one, the type inference filtering is dropped.
Pretty sure I added this as a feature but now it's a bug :')Experiment Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/38Offline plotting support is shaky2020-05-26T15:19:19ZJaden DIEFENBAUGHOffline plotting support is shakyIf the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an inter...If the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an internet connection and couldn't plot because `beat.cmdline` was trying to fetch stuff from beat.web even though the plotter objects and default parameters existed.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/126Fix exp editor assigning datasets wrongly when choosing protocol2018-11-20T19:14:16ZJaden DIEFENBAUGHFix exp editor assigning datasets wrongly when choosing protocolWhen creating an iris experiment, training & testing were assigned wrongly (why???)When creating an iris experiment, training & testing were assigned wrongly (why???)Experiment Editor: Fixeshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/125Update & expand toolchain editor help menu popup thingy2018-12-19T19:02:44ZJaden DIEFENBAUGHUpdate & expand toolchain editor help menu popup thingyEspecially after the UX passEspecially after the UX passToolchain Editor: UX Improvementshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/124State management refactoring2018-07-26T17:52:14ZJaden DIEFENBAUGHState management refactoringThought we already had an issue open for this but I guess not.
Right now the object editors are using a `cache` state field to hold the unsaved changed. These changes aren't propogated to the redux store until the user clicks 'save', wh...Thought we already had an issue open for this but I guess not.
Right now the object editors are using a `cache` state field to hold the unsaved changed. These changes aren't propogated to the redux store until the user clicks 'save', which will *also* save to the prefix. There's no reason to have a state cache and the redux store anymore.
Instead of using the editors' states' cache fields to store unsaved changes, just use the redux store!State Management Refactoringhttps://gitlab.idiap.ch/beat/docs/-/issues/3doc - pipeline stuck2018-06-05T09:22:20ZFlavio TARSETTIdoc - pipeline stuck@andre.anjos @samuel.gaist :
Could someone explain to me why I get this ?
https://gitlab.idiap.ch/beat/docs/-/jobs/138995
`This job is stuck, because you don't have any active runners online with any of these tags assigned to them: do...@andre.anjos @samuel.gaist :
Could someone explain to me why I get this ?
https://gitlab.idiap.ch/beat/docs/-/jobs/138995
`This job is stuck, because you don't have any active runners online with any of these tags assigned to them: docker
Go to Runners page`
On the Runners page do I need to configure something ?
Thanks for your helphttps://gitlab.idiap.ch/beat/beat.tutorial.prefix/-/issues/1Can't push to master2018-06-05T09:07:29ZJaden DIEFENBAUGHCan't push to master@samuel.gaist @andre.anjos I need to update this prefix but I apparently don't have permissions?@samuel.gaist @andre.anjos I need to update this prefix but I apparently don't have permissions?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/docs/-/issues/2Official platform link for beat documentation (aggregated)2018-12-17T21:55:32ZFlavio TARSETTIOfficial platform link for beat documentation (aggregated)@andre.anjos :
On the platform: https://www.idiap.ch/software/beat/ I see the link https://www.idiap.ch/software/beat/docs/beat/docs/stable/ (currently not working). Could you let me know how will this get updated or is it something you ...@andre.anjos :
On the platform: https://www.idiap.ch/software/beat/ I see the link https://www.idiap.ch/software/beat/docs/beat/docs/stable/ (currently not working). Could you let me know how will this get updated or is it something you will have to do manually to point to the proper documentation?André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/123[doc] missing documentation2018-07-19T16:47:13ZFlavio TARSETTI[doc] missing documentation@jdiefenbaugh and @andre.anjos
I see here that this package is "conda ready" however I don't see any documentation...
I am currently working on the merge of documentation. Is this something you plan to fix before the tutorial or shoul...@jdiefenbaugh and @andre.anjos
I see here that this package is "conda ready" however I don't see any documentation...
I am currently working on the merge of documentation. Is this something you plan to fix before the tutorial or should I omit beat.editor in the merged documents for now?DocsJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/122Clickable toolchain link in exp names in exp editor2018-12-19T19:02:44ZJaden DIEFENBAUGHClickable toolchain link in exp names in exp editorMiscellaneous Editor-specific Improvementshttps://gitlab.idiap.ch/beat/beat.core/-/issues/58Local executor doesnt capture user stdout2018-05-30T14:29:40ZJaden DIEFENBAUGHLocal executor doesnt capture user stdoutAdding a print statement to an algorithm prints it alongside the platform's messages, not under the captured user stdout sectionAdding a print statement to an algorithm prints it alongside the platform's messages, not under the captured user stdout section