beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-10-04T15:12:53Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/178Library Editor2019-10-04T15:12:53ZJaden DIEFENBAUGHLibrary Editor[v2] 1 - Edition/Visualization for small editorshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/161[validation] types and values for parameters not properly checked in editor/ ...2020-02-12T12:23:03ZFlavio TARSETTI[validation] types and values for parameters not properly checked in editor/ second issue old value saved@jdiefenbaugh : The editor presents some validation bugs
The editor seems to have unexpected behavior for validation of parameters.
A `string value` could be saved in a `int8`, and this is valid and could be saved in the `json` file.
...@jdiefenbaugh : The editor presents some validation bugs
The editor seems to have unexpected behavior for validation of parameters.
A `string value` could be saved in a `int8`, and this is valid and could be saved in the `json` file.
A second issue comes from the fact that all parameters have their old value saved somewhere in the props or state history.
For example if we suddenly decide to change the parameter type from `"string"` to `"int"`, the value `"helloworld"` will be kept as the value for the `"int"`Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/192[meta] Naming branches to associate it with an issue2019-02-25T11:34:25ZJaden DIEFENBAUGH[meta] Naming branches to associate it with an issueIn `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressi...In `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressing? So names like the following are fine:
- "issue_20_fix_wrong_index"
- "implement_db_editor_248"
But names like the following aren't okay except in rare cases:
- "fix_wrong_index"
- "implement_db_editor"
I personally find it hard to understand what someone is doing in a branch when they don't reference an existing issue.
_[edit]_:
Final decision: <issue_number>_name_of_the_branchhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/140Update Algorithm schema (and editor?)2019-02-26T18:00:07ZJaden DIEFENBAUGHUpdate 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 readyhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/191Remove v1 artifacts2019-10-04T15:12:54ZJaden DIEFENBAUGHRemove v1 artifactsSummary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does i...Summary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does it provide?
Remove all of the above:
- Remove all the JS stuff from `.gitignore`
- Remove the `beat/editor/js` directory
- Remove most of the the text in `doc/index.rst` and just have it point to `doc/contribute.rst` for now
- Remove `doc/{editor.rst,licenses.rst}`
- Save `doc/{img/,svg/}` as we'll probably want to adapt these later for v2 documentationhttps://gitlab.idiap.ch/beat/beat.web/-/issues/18Avoid particle "it" on experiment buttons2017-08-23T11:36:30ZAndré AnjosAvoid particle "it" on experiment buttonsTo standardize the button labels everywhere, would it be possible to remove the particle "it" from buttons like "fork it" and "cancel it"?
It is implicit from the context that it refers to the currently running experiment.To standardize the button labels everywhere, would it be possible to remove the particle "it" from buttons like "fork it" and "cancel it"?
It is implicit from the context that it refers to the currently running experiment.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/187cross-tab-sync branch still active?2018-12-20T18:45:18ZAndré Anjoscross-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 readyJaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/19The toolchain editor generates invalid toolchains2014-09-04T11:59:49ZTiago de Freitas PereiraThe toolchain editor generates invalid toolchains- [X] Let say that you have 3 blocks A, B and C. The block A is a dataset block and the blocks B and C are regular blocks.
When you create a connection between blocks A and B, the connection uses the synchronization channel from A. Righ...- [X] Let say that you have 3 blocks A, B and C. The block A is a dataset block and the blocks B and C are regular blocks.
When you create a connection between blocks A and B, the connection uses the synchronization channel from A. Right after that, when you try to create a connection between the blocks A and C (using the same field on the "A" side), the synchronization channel is null, which invalidates the toolchain. Additionally, it is not possible to fix it.
- [X] In the same example as above (blocks A,B and C), when you create a connection between the blocks A and B, it is not possible to create a connection between A and C (using the same field in the "A" side). The only possible way is to create a connection between C and A. I know this is the same thing, but it is not intuitive.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/189Package "pre-commit" doesn't exist in conda2019-10-04T15:12:54ZJaden DIEFENBAUGHPackage "pre-commit" doesn't exist in condaSummary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Summary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/20Improve deletion of databases from Django administration page2017-08-23T11:36:30ZLaurent EL SHAFEYImprove deletion of databases from Django administration pageThe current behaviour when deleting a database from Django administration page is as follows:
- Deletion of the 'Database' entry
- Deletion of the 'Database protocol' entries
- Deletion of the 'Database set' entries
Since adding a ...The current behaviour when deleting a database from Django administration page is as follows:
- Deletion of the 'Database' entry
- Deletion of the 'Database protocol' entries
- Deletion of the 'Database set' entries
Since adding a database may also imply adding a 'Database set template' and 'Database output's, it would be better to remove these entries as well, when they are not used by any other databases installed on the platform.Biometrics Center Kickoff Meeting and BEAT Reviewhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/190AssetType Unknown path spelling2019-10-04T15:12:54ZJaden DIEFENBAUGHAssetType Unknown path spellingSummary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd4...Summary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd450167fbf24f39666d86576e43a0b/beat/editor/backend/assetmodel.py#L44Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/21New django action for experiment deletion2017-08-23T11:36:30ZAndré AnjosNew django action for experiment deletionWe should add a new django admin action (https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/) for treating Experiment objects in the BEAT django DB.
In case this action is clicked by the administrator, it allows him/her t...We should add a new django admin action (https://docs.djangoproject.com/en/dev/ref/contrib/admin/actions/) for treating Experiment objects in the BEAT django DB.
In case this action is clicked by the administrator, it allows him/her to:
- Delete the Experiment + all associated results
- Clean-up the cache from the experiment:
* Clean-up local cache entries in the Django DB
* Send a message to the scheduler to delete certain cache files (see biometric/beat.scheduler#10). Notice you don't need to cancel any experiment (in case they are running). The scheduler shall be able to handle this gracefully.
If another experiment shares cache files with the experiment being deleted, then:
1) The cache files of that experiment are also cleaned-up
2) The experiment is marked as "Pending", so the user can re-run it at a later stage (unless the experiment was also running, in which case it will be cancelled by the scheduler automatically).
We understand this is a rather drastic action, but may be required in case of severe cache corruption.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://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 editorhttps://gitlab.idiap.ch/beat/beat.web/-/issues/553toolchain created locally does not show up correctly on beat.web2022-03-04T09:39:11ZAmir MOHAMMADItoolchain created locally does not show up correctly on beat.webThis toolchain [1.json](/uploads/49903eb5d5e5223a6f191a8656049ba8/1.json) also available here: https://www.idiap.ch/software/beat/platform/toolchains/amohammadi/livdet/1/#viewer does not show up correctly in the web platform but looks ok...This toolchain [1.json](/uploads/49903eb5d5e5223a6f191a8656049ba8/1.json) also available here: https://www.idiap.ch/software/beat/platform/toolchains/amohammadi/livdet/1/#viewer does not show up correctly in the web platform but looks ok in beat.editor:
![image](/uploads/dfbfc0c76547e04de4db701dacb356c9/image.png)https://gitlab.idiap.ch/beat/beat.editor/-/issues/194visula distiction between different parameter cathegories on the experiment p...2020-02-12T12:31:57ZZohreh MOSTAANIvisula distiction between different parameter cathegories on the experiment page.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.[v2] 3 - Experiment editorhttps://gitlab.idiap.ch/beat/beat.web/-/issues/554cannot fork an experiment2020-07-21T14:40:56ZAmir MOHAMMADIcannot fork an experimentWhen I try to fork an experiment, https://www.idiap.ch/software/beat/platform/experiments/fork/amohammadi/tutorial/eigenface/1/atnt-eigenfaces-69-comp/ I get this error:
![image](/uploads/a703a2ab2133b08e6ffc2dc4384f635f/image.png)When I try to fork an experiment, https://www.idiap.ch/software/beat/platform/experiments/fork/amohammadi/tutorial/eigenface/1/atnt-eigenfaces-69-comp/ I get this error:
![image](/uploads/a703a2ab2133b08e6ffc2dc4384f635f/image.png)Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/195visual feedback to the user when the save button is pressed2020-02-12T12:32:25ZZohreh MOSTAANIvisual feedback to the user when the save button is pressedWhen I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right ...When I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right now I refresh the whole page to make sure that the changes are done.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.web/-/issues/555Analyzer results are not shown for new experiments2020-08-03T08:33:36ZAmir MOHAMMADIAnalyzer results are not shown for new experimentsWhen a new experiment runs on the platform, its analyzer results are not shown.
For example, I tried running the tutorial atnt eigenfaces experiment:
https://www.idiap.ch/software/beat/platform/experiments/amohammadi/tutorial/eigenface/1...When a new experiment runs on the platform, its analyzer results are not shown.
For example, I tried running the tutorial atnt eigenfaces experiment:
https://www.idiap.ch/software/beat/platform/experiments/amohammadi/tutorial/eigenface/1/atnt-eigenfaces-69-comp/#results
and its results are not showing up.
This has to do with new experiments only I thinkSamuel 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.web/-/issues/217Total number of slots per Queue not correctly displayed on Backend page2015-07-21T14:20:27ZAndré AnjosTotal number of slots per Queue not correctly displayed on Backend pageSomething to be fixed. The current display shows only `--` if you click on the `Queues` tab.Something to be fixed. The current display shows only `--` if you click on the `Queues` tab.BTAS TutorialAndré AnjosAndré Anjos