beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2017-08-08T04:40:37Zhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/12Parameter check on Algorithm class is not necessary2017-08-08T04:40:37ZAndré AnjosParameter check on Algorithm class is not necessaryAs soon as possible, remove this check as this is done by the BEAT infrastructure already.As soon as possible, remove this check as this is done by the BEAT infrastructure already.Open-source ReleaseAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/249[beat web broken due to new merge with updated rest_framework]2015-08-12T16:00:01ZFlavio TARSETTI[beat web broken due to new merge with updated rest_framework]Merged a broken branch.
I guess I have some problem in my develop-eggs that links on rest_framework.
@andre.anjos @samuel.gaist
Could you please fix this and let me know what are the steps I need to do.Merged a broken branch.
I guess I have some problem in my develop-eggs that links on rest_framework.
@andre.anjos @samuel.gaist
Could you please fix this and let me know what are the steps I need to do.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/248[plotter] Lacks consistence on sharing behaviour2019-07-04T08:37:02ZFlavio TARSETTI[plotter] Lacks consistence on sharing behaviourCurrently the creation of a plotter is not much consistent.
From our discussion we assume this:
```text
----> dataformat----> plotter 1,...,n and for each plotter ----> plotter parameter 1,...,k
```
It misses a check that each...Currently the creation of a plotter is not much consistent.
From our discussion we assume this:
```text
----> dataformat----> plotter 1,...,n and for each plotter ----> plotter parameter 1,...,k
```
It misses a check that each dataformat has a plotter (i.e. and a default plotter) that is public.
This should be done at the creation of a plotter. The issue is that a person could add experiments to report (the experiment having an accessible dataformat), but he is not able to use the plotters if they are private.
The plotter parameters are not related to any plotters (should this be done ?)
https://gitlab.idiap.ch/beat/beat.web/-/issues/247[reports] Workflow for adding a Table of results is not very intuitive2019-07-04T08:37:03ZAndré Anjos[reports] Workflow for adding a Table of results is not very intuitiveThe current workflow to add a Table of results gets the user through a sequence of clicks up to the point a list with select boxes is shown.
At this point, there is no "set" button or anything that allows the user to dismiss/apply the...The current workflow to add a Table of results gets the user through a sequence of clicks up to the point a list with select boxes is shown.
At this point, there is no "set" button or anything that allows the user to dismiss/apply the options. It is not very automatic that clicking outside the pop-up window makes it apply the options. I'd rather think it should cancel the action...
Anyways, some improvement on this area would be welcome.https://gitlab.idiap.ch/beat/beat.web/-/issues/246[plots] Not working on the staging system2015-08-04T12:29:59ZAndré Anjos[plots] Not working on the staging systemThe plotting is not working on the staging system. Probably related to the experiment label -> name changes.The plotting is not working on the staging system. Probably related to the experiment label -> name changes.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/245[reports] Sharing/locking behaviour2015-08-27T14:43:51ZAndré Anjos[reports] Sharing/locking behaviourHow can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be th...How can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be the workflow to collaboratively create a report or (on a minor scale) an attestation.
Differently than attestations, reports combine displaying features that authors (working remotely) may need to agree while composing an article. IMO, being able to share a report sounds like a good idea.
Attestations don't suffer from this problem because, if you lock them, other people can see it. Reports, on the other end, can only be seen while locked so the user would have to:
1. Lock report
2. Share link with remote party
3. If comments from remote party: unlock report (now not visible anymore to remote party)
4. Modify the report and go back to 1 as many times as necessary
This looks a bit cumbersome - would you agree? In this context, would it make sense to have reports a subclass of "Shareable" as suggested on one of our discussions?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/244[reports] Experiments are not shown on the report page2015-08-13T15:34:00ZAndré Anjos[reports] Experiments are not shown on the report pageDespite the fact I could successfully insert 2 experiments on my report, it is currently not possible to see them (at least a list) through the respective report page.Despite the fact I could successfully insert 2 experiments on my report, it is currently not possible to see them (at least a list) through the respective report page.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/243[reports] Cannot add Table/Figure2015-08-13T15:34:00ZAndré Anjos[reports] Cannot add Table/FigureIt is currently not possible to add a table to an existing report on the staging system. The report in question has a couple of experiments added to it.
Clicking on the any of the entries when the pop-up window appears does not do any...It is currently not possible to add a table to an existing report on the staging system. The report in question has a couple of experiments added to it.
Clicking on the any of the entries when the pop-up window appears does not do anything.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/242[reports] Analyzer hint on experiment lists2015-11-20T11:26:17ZAndré Anjos[reports] Analyzer hint on experiment listsBecause the analyzer plays an important role on the search and on the reports, it would be good if it is also displayed along side experiment tables (e.g., on the user microsite or by the end of a toolchain page). This would help users a...Because the analyzer plays an important role on the search and on the reports, it would be good if it is also displayed along side experiment tables (e.g., on the user microsite or by the end of a toolchain page). This would help users avoid the selection of experiments without matching analyzers and would understand why there are errors when neglecting that piece of information.
Furthermore, when refusing to add experiments, a list of conflicting choices and the reasoning why one can't add an experiment would be welcome, if easy to implement.Final DocumentationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/241[reports] Cannot have spaces on their name, but no validation takes place2015-08-26T15:02:17ZAndré Anjos[reports] Cannot have spaces on their name, but no validation takes placeNo validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1...No validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1. Create a report through the admin site with spaces on its name
2. On the user site search for this report and click on it
Results: Django exception being thrown
Expected result: Either finds the page or has validation implemented so that names with spaces are not allowed.
Note: There is no good reason why reports with spaces should not be allowed. Or is there?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/240[reports] Clicking on "New" Report brings user to the front page2015-08-13T15:34:01ZAndré Anjos[reports] Clicking on "New" Report brings user to the front pageYou can't currently click on the "New" button on the Report's tab at the user micro-site. It gets you to the front page instead.
@flavio.tarsetti: Can you confirm we are missing a new Reports editor?
The only way to create a report...You can't currently click on the "New" button on the Report's tab at the user micro-site. It gets you to the front page instead.
@flavio.tarsetti: Can you confirm we are missing a new Reports editor?
The only way to create a report is currently using the admin panel.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/239New Reports tab causes a second line on some displays2015-08-04T13:52:47ZAndré AnjosNew Reports tab causes a second line on some displaysBecause we have a growing number of tabs, we need to search for a better alternative to display the different functions available in the user micro-site. Currently the display on my monitor looks like this:
![image](https://gitlab.idi...Because we have a growing number of tabs, we need to search for a better alternative to display the different functions available in the user micro-site. Currently the display on my monitor looks like this:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/2a68dc7e626d20647f55b739331b368c/image.png)
@philip.abbet: do you have any cool ideas for this?BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/238Statistics consistency when removing experiments2016-02-04T13:59:54ZLaurent EL SHAFEYStatistics consistency when removing experimentsI have noticed the following issue when removing an experiment.
The deletion of the experiment removes the statistics associated to the blocks which were executed (These statistics are displayed on the right side of the experiment pag...I have noticed the following issue when removing an experiment.
The deletion of the experiment removes the statistics associated to the blocks which were executed (These statistics are displayed on the right side of the experiment page). However, this does not remove the associated cache files.
Therefore, when re-running the same experiment (as the one deleted), this may lead to the block not being re-executed (since the files exist in the cache). However, the statistics have been removed, and they are, hence, not displayed on the right side of the experiment page.Final Documentationhttps://gitlab.idiap.ch/beat/beat.core/-/issues/42[io] Execute externally currently requires twisted (async.run)2017-08-06T11:17:03ZLaurent EL SHAFEY[io] Execute externally currently requires twisted (async.run)With the introduction of the new I/O framework, the execution of a job requires to launch the I/O daemon (that will launch and control the user process). This daemon currently needs twisted (async.run) to be executed, while we would idea...With the introduction of the new I/O framework, the execution of a job requires to launch the I/O daemon (that will launch and control the user process). This daemon currently needs twisted (async.run) to be executed, while we would ideally prefer not to have such a dependency in beat.core.
To fix this, an optimal decapsulation of the communication via pipes from the I/O daemon would be required, as well as its integration into beat.core.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/41[io] Optimization of I/O when using pipes2017-08-06T11:17:03ZLaurent EL SHAFEY[io] Optimization of I/O when using pipesWith the introduction of communication via pipes between the user process and the daemon, it may happen that a chunk of data is decoded from a baseformat and then re-encoded (into a baseformat) to send it through pipe. This is the case, ...With the introduction of communication via pipes between the user process and the daemon, it may happen that a chunk of data is decoded from a baseformat and then re-encoded (into a baseformat) to send it through pipe. This is the case, when next() is called: a chunk of data is then read using a CachedDataSource (that will decode from a baseformat) and then sent through a pipe (and hence will be re-encoded into a baseformat). This is of course suboptimal and may be fixed by specializing the CachedDataSource.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/237Formalize plotter API2019-07-04T08:37:03ZAndré AnjosFormalize plotter APILike `algorithms`, we should make sure we have a formal API to handle `plotters`. Only the `system` user may upload/change objects. All users may download and list `plotters` which are accessible to them.Like `algorithms`, we should make sure we have a formal API to handle `plotters`. Only the `system` user may upload/change objects. All users may download and list `plotters` which are accessible to them.https://gitlab.idiap.ch/beat/beat.backend.python/-/issues/11Create PipeSource/Sink instead of changing Output class2017-08-08T04:40:37ZAndré AnjosCreate PipeSource/Sink instead of changing Output classWe need to revert the design currently available on this package so that it respects the old beat.core design. Instead of overwriting the Input/Output classes, we need to create both a PipeSource and a PipeSink classes that can be used t...We need to revert the design currently available on this package so that it respects the old beat.core design. Instead of overwriting the Input/Output classes, we need to create both a PipeSource and a PipeSink classes that can be used to input and output data for the Input/Output classes respectively.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/10Improve test-ability of this package2017-08-08T04:40:37ZAndré AnjosImprove test-ability of this packageAs of today, it is not very easy to test the user process w/o an I/O daemon. We'd have to figure out a way to build unit tests around this package.As of today, it is not very easy to test the user process w/o an I/O daemon. We'd have to figure out a way to build unit tests around this package.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/40Cleanup of executor/dataformats/algorithms/libraries/schema loading2017-08-06T11:17:03ZAndré AnjosCleanup of executor/dataformats/algorithms/libraries/schema loadingAs of today, we moved the definition of these objects and functions to beat.backend.python. The backend does not need to be able to validate objects, only to load them and instantiate a runner. We should revise and clean-up this relation...As of today, we moved the definition of these objects and functions to beat.backend.python. The backend does not need to be able to validate objects, only to load them and instantiate a runner. We should revise and clean-up this relationship.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/39inputs/outputs cleanup w.r.t beat.backend.python2017-08-06T11:17:03ZAndré Anjosinputs/outputs cleanup w.r.t beat.backend.pythonAs of today there is some functionality of beat.backend.python that is duplicated in this package. We should clean-up and organised it so there is no repetition of code, respecting a good DRY principle.As of today there is some functionality of beat.backend.python that is duplicated in this package. We should clean-up and organised it so there is no repetition of code, respecting a good DRY principle.BTAS TutorialAndré AnjosAndré Anjos