beat.web issueshttps://gitlab.idiap.ch/beat/beat.web/-/issues2014-09-08T07:19:26Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/30Scheduler (farm status) page2014-09-08T07:19:26ZAndré AnjosScheduler (farm status) pageWe decided to separate the scheduler page from the site statistics, given their purposes is rather different.
The site statistics show the operational history of the platform.
The scheduler pages show the current platform health.
...We decided to separate the scheduler page from the site statistics, given their purposes is rather different.
The site statistics show the operational history of the platform.
The scheduler pages show the current platform health.
We propose to create a URL "PREFIX/status", that, for the time being, shows the results (collapsed) of the scheduler `get-status` call. We'll improve from this point.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/29Experiment results which are marked Done show ERROR on experiment page2017-08-23T11:36:34ZAndré AnjosExperiment results which are marked Done show ERROR on experiment pageExample: https://www.beat-eu.org/platform/experiments/tutorial/full_lbphs/test_tiago
This is probably related to issue #27.Example: https://www.beat-eu.org/platform/experiments/tutorial/full_lbphs/test_tiago
This is probably related to issue #27.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/28If experiment label is too big, "Fork" and "Delete" buttons get page width2014-09-05T13:26:28ZAndré AnjosIf experiment label is too big, "Fork" and "Delete" buttons get page widthExample: https://www.beat-eu.org/platform/experiments/setup/tutorial/private/digit/mnist-mlp-10-hidden-50-iter/Example: https://www.beat-eu.org/platform/experiments/setup/tutorial/private/digit/mnist-mlp-10-hidden-50-iter/RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/27Cannot make experiment public2014-09-05T13:20:45ZAndré AnjosCannot make experiment publicSomehow, we cannot make some of the experiments public. Clicking on the button results in no action.
In some of those, clicking on "request attestation" results in a pop-up with a strange text.
Example: https://www.beat-eu.org/plat...Somehow, we cannot make some of the experiments public. Clicking on the button results in no action.
In some of those, clicking on "request attestation" results in a pop-up with a strange text.
Example: https://www.beat-eu.org/platform/experiments/tutorial/full_lbphs/test_tiago/
This is probably related to issue #29.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/26Cancelling experiment results in User page experiment list to not load2017-08-23T11:36:30ZAndré AnjosCancelling experiment results in User page experiment list to not loadAfter cancellation, the only way to recover into a working state is to manually set the experiment status from "Cancelling" to "Pending".After cancellation, the only way to recover into a working state is to manually set the experiment status from "Cancelling" to "Pending".RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/22Few toolchains cannot be opened with chrome2014-09-05T09:16:23ZLaurent EL SHAFEYFew toolchains cannot be opened with chromeWhen trying to open a toolchain (or the results of an experiment), chrome is hanging:
e.g.:
https://www.beat-eu.org/platform/experiments/tutorial/private/eigenface/delete_me6/
On firefox, it works well.When trying to open a toolchain (or the results of an experiment), chrome is hanging:
e.g.:
https://www.beat-eu.org/platform/experiments/tutorial/private/eigenface/delete_me6/
On firefox, it works well.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://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.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.web/-/issues/6Small fixes to the web interface2014-09-04T13:41:08ZAndré AnjosSmall fixes to the web interfaceThis is a collection of small fixes to the web interface, to make it more coherent. Some of these suggestions are temporary. Feel free to edit this bug and mark items as outdated (use a ~~strikethrough syntax~~), fixed (just put an `x` o...This is a collection of small fixes to the web interface, to make it more coherent. Some of these suggestions are temporary. Feel free to edit this bug and mark items as outdated (use a ~~strikethrough syntax~~), fixed (just put an `x` on its checkbox) or add new items.
- [X] ~~In the user algorithms page, it would be nice for the time being to gray out the "New" button so it is clear the user cannot create a new algorithm from the web just yet.~~ Display a warning about the online edition of algorithms
- [X] Same as above, but for data formats
- [X] If I log-in as user "anjos" and search for "eigenface", the results page show me private results from the user "tutorial". This must be fixed!
- [X] When I add one block and try to edit any information of the block (the name or the connectors), the information only persists if I type <enter>. If I click in any point outside the block, I loose what I typed. The expected behavior should be: if you type and loose focus, whatever you typed persists.
- [X] The save button on the toolchain editor should give the user some feedback that the toolchain has been saved. This relates directly to issue #3. When it is done, it should also be closed.
- [X] When you try to create a second connection in a block (toolchain editor), the channel is automatically null.
- [X] In the edition mode of the toolchain, the "fork it" is enabled and doesn't execute any action
- [X] It is not possible to change the status (private to public, private to public for some users) of a data format
- [X] In a failed experiment, the "Cancel it" button appears instead of a "Delete" button.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/3Toolchain editor - Save modifications of the display of a toolchain2014-09-04T13:40:51ZAndré AnjosToolchain editor - Save modifications of the display of a toolchainThis has now been implemented.
The save button though, could be improved so that it shows when the system last saved the toolchain being edit. This would given the user some feedback.This has now been implemented.
The save button though, could be improved so that it shows when the system last saved the toolchain being edit. This would given the user some feedback.RP Conference, Darmstadt, DEPhilip ABBETPhilip ABBET