beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-06-19T05:13:48Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/82Improve duplicate key handling2019-06-19T05:13:48ZSamuel GAISTImprove duplicate key handlingThis issue tracks the implementation of duplicated key handling in JSON files used.
In normal situation, the files should be edited and stored using beat/beat.editor> or currently still beat/beat.web> however if one does edit the declar...This issue tracks the implementation of duplicated key handling in JSON files used.
In normal situation, the files should be edited and stored using beat/beat.editor> or currently still beat/beat.web> however if one does edit the declaration file by hand, errors like duplicated key might be introduced which won't be caught as loading a JSON file line by line will result in a dictionary with the last entry being used (which is normal behavior when dealing with dictionary type of containers).
In our case, the system will generate an error so that nothing will run with unexpected values.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/245Improve error handling2019-12-11T09:57:48ZSamuel GAISTImprove error handlingSummary
Currently, there's lot of code triggering a RuntimeError which in turn will make beat.editor stop.
Most of these situations should be gracefully handled. If possible, a fix should be proposed to the user so he can continue work...Summary
Currently, there's lot of code triggering a RuntimeError which in turn will make beat.editor stop.
Most of these situations should be gracefully handled. If possible, a fix should be proposed to the user so he can continue working.
Steps to reproduce
1) Create a new Plotter
2) Load the plotter
This will make beat.editor crash as the new Plotter will be based on the prototype that contains an invalid entry.
This situation is already reported in #244
What is the current bug behavior?
beat.editor will end there
What is the expected correct behavior?
beat.editor should not stop
Possible fixes
The user should get a message about what is going wrong. If possible a fix should be proposed and applied if accepted.
In any case, the editor should continue working.[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/546Improve experiment finished email2020-04-01T09:50:27ZSamuel GAISTImprove experiment finished emailCurrently, the emails sent to platform users for notification about a run success or failure contains a direct link that will end in a 404 error if the user is not logged in.
It would be nice if the link would allow to start the login p...Currently, the emails sent to platform users for notification about a run success or failure contains a direct link that will end in a 404 error if the user is not logged in.
It would be nice if the link would allow to start the login process since it is sent to the author of the experiment.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/27Improve loop evaluator synchronized write2019-10-01T10:08:15ZSamuel GAISTImprove loop evaluator synchronized writeThe loop evaluator write method is call once per output write. However, a processor block may have several outputs which means that the evaluator write method will be called as many times as an output is written. So in the case of a sequ...The loop evaluator write method is call once per output write. However, a processor block may have several outputs which means that the evaluator write method will be called as many times as an output is written. So in the case of a sequential processor algorithm with 2 outputs and 3 input data, the evaluator write method will be call 6 times.
After talking with @andre.anjos, the current solution proposed is to add the output name written to as a parameter of the evaluator write method so that the developer can chose on which one he wants to "synchronize" the evaluator output.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/7Improvements to the beat command-line tool (migrated from github)2015-03-25T07:37:09ZAndré AnjosImprovements to the beat command-line tool (migrated from github)- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes de...- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes detection when running an experiment
- [x] Check user existence in commands like: `beat algorithms pull --user ADHDAHGDGAHSGHDAGHSDGH`. Presently, this is silently ignored.
- [x] While running locally, it would be nice that this package printed out more information about data input and output. It is currently very summarized.
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/547Improve new version push handling2020-04-16T13:15:24ZSamuel GAISTImprove new version push handlingCurrently if a new version of an asset is pushed without history information, there will be an error because the backend will try to create an asset from scratch. This will trigger an error because of an already existing asset.
As a sid...Currently if a new version of an asset is pushed without history information, there will be an error because the backend will try to create an asset from scratch. This will trigger an error because of an already existing asset.
As a side effect, if no asset of a previous version exists, the backbend will create a new one based on the name but with the wrong number.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/89Improve output error messages2019-10-04T08:44:08ZSamuel GAISTImprove output error messagesWhen not enough data is written on an output, the related cache will be cleaned.
An error message must be shown to the user so he knows what is happening.When not enough data is written on an output, the related cache will be cleaned.
An error message must be shown to the user so he knows what is happening.https://gitlab.idiap.ch/beat/beat.editor/-/issues/244Improve plotter new creation handling2019-10-04T15:12:49ZSamuel GAISTImprove plotter new creation handlingSummary
Currently when creating a new Plotter, the prototype contains "plot/unknown/1".
This has problematic implications:
- The editor will fail to load it
- Test will fail because the editor can't load that dataformat
Steps to repr...Summary
Currently when creating a new Plotter, the prototype contains "plot/unknown/1".
This has problematic implications:
- The editor will fail to load it
- Test will fail because the editor can't load that dataformat
Steps to reproduce
1) Click on new
2) Select Plotter
3) Try to edit the plotter created
What is the current bug behavior?
An error is raised and it make the application fail
What is the expected correct behavior?
Either:
- Show a dialog asking to select a dataformat to use.
- Select a suitable dataformat from the prefix. Maybe a simple default like for the algorithm prototype.
Possible fixes
One possibility could be to have a method called after the dialog has been closed that can be re-implemented in sub-classes to do whatever is needed for the newly created object.
Another would be to move the dialog logic in its own method so re-implementing _createNewAsset would be easier.
Note that this affects beat/beat.editor!101[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/237Improve remove/add button visuallization2020-06-19T14:52:24ZZohreh MOSTAANIImprove remove/add button visuallizationIt is not easy to distinguish which add/remove button is for which sub-category when there are many categories in an asset (such as a big confusing dataformat). This problem should be addressed properly. Maybe if we have different shades...It is not easy to distinguish which add/remove button is for which sub-category when there are many categories in an asset (such as a big confusing dataformat). This problem should be addressed properly. Maybe if we have different shades for the editor objects (see #235) This problem is solved automatically but there might be a better way.
Also at the moment the add button in the algorithm object is on the left but in the dataformat objects is on the right. The decision is to move all of them to the right.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/544Improve sign-up form2020-03-16T16:29:31ZAndré AnjosImprove sign-up formCurrently, the sign-up form for supervisors does not indicate that one must use their "institutional" e-mail address. I propose we modify it slightly to indicate this as well as include an URL to the reasoning behind this.
For example:...Currently, the sign-up form for supervisors does not indicate that one must use their "institutional" e-mail address. I propose we modify it slightly to indicate this as well as include an URL to the reasoning behind this.
For example:
* Instead of saying "you hold a position in a research laboratory", we should say "you hold a permanent position in a research laboratory".
* Instead of saying "E-mail" we should say "Institutional E-mail".
* We should add a link to: https://www.idiap.ch/software/beat/docs/beat/docs/stable/beat.web/doc/user/faq.html#what-is-a-supervisor
* In that link, we should specify that e-mail should be institutional.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/23Improve storage classes2019-05-08T08:53:02ZSamuel GAISTImprove storage classesThe Storage and CodeStorage classes share a parallel goals, part of their code is exactly the same yet they are two distinct classes.
Fix this by creating a common base class so they share the configuration member variable and their check.The Storage and CodeStorage classes share a parallel goals, part of their code is exactly the same yet they are two distinct classes.
Fix this by creating a common base class so they share the configuration member variable and their check.Soft loopsSamuel GAISTSamuel GAISThttps://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.web/-/issues/143In an experiment setup: database changes when removing/changing algorithms2015-05-12T17:14:43ZManuel GüntherIn an experiment setup: database changes when removing/changing algorithmsThe is an issue with the experiment editor. After forking an old experiment, and changing an algorithm (for example one for scoring), the database entry is modified, switching to a completely unrelated database, or even becomes empty.
I...The is an issue with the experiment editor. After forking an old experiment, and changing an algorithm (for example one for scoring), the database entry is modified, switching to a completely unrelated database, or even becomes empty.
It seems that the same applies, when a new experiment is created.API DocumentationPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/31Inclined lines on toolchain editor2014-09-15T08:49:58ZAndré AnjosInclined lines on toolchain editorThe toolchain editor, sometimes allows the user to generate inclined lines, whereas it should not.The toolchain editor, sometimes allows the user to generate inclined lines, whereas it should not.Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/54Incorrect experiment links ?2014-10-28T08:18:57ZSébastien MARCELIncorrect experiment links ?pour certaines experiences example:
https://www.beat-eu.org/platform/search/?query=db:banca%20type:results
quand on clique sur le lien il y a un "/" qui manque:
https://www.beat-eu.org/platform/experiments/tpereirafull_isv/1/PERIOCU...pour certaines experiences example:
https://www.beat-eu.org/platform/search/?query=db:banca%20type:results
quand on clique sur le lien il y a un "/" qui manque:
https://www.beat-eu.org/platform/experiments/tpereirafull_isv/1/PERIOCULAR_ISV_bancaP_10/
au lien de
https://www.beat-eu.org/platform/experiments/tpereira/full_isv/1/PERIOCULAR_ISV_bancaP_10/
autre example avec https://www.beat-eu.org/platform/search/?query=spoofing
sur le lien
https://www.beat-eu.org/platform/user/smarcelface-antispoofing/
ou https://www.beat-eu.org/platform/user/ivana7csimple-antispoofing-updated/
Biometrics Center Kickoff Meeting and BEAT ReviewPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/210Incorrect referenced dataformats URL on dataformat webpage2015-07-01T13:39:55ZLaurent EL SHAFEYIncorrect referenced dataformats URL on dataformat webpageThe link contains a duplicate `dataformats`.The link contains a duplicate `dataformats`.BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.web/-/issues/211Incorrect referenced experiments URL on algorithm webpage2015-07-06T11:24:31ZLaurent EL SHAFEYIncorrect referenced experiments URL on algorithm webpageThe first part of the URL (e.g. www.beat-eu.org/platform/ is missing).The first part of the URL (e.g. www.beat-eu.org/platform/ is missing).BTAS Tutorialhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/10infinite scrolling2019-05-09T12:54:27ZJaden DIEFENBAUGHinfinite scrollinghttps://gitlab.idiap.ch/beat/beat.core/-/issues/13Input management2018-11-03T15:23:12ZAndré AnjosInput managementIt would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.It would be interesting to revisit input management on algorithms and analysis blocks and try to factor out code that is repeated everywhere into a simpler interface.
This bug shall be used to track advances on this field.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/24Input/Output/Source/Sink concept redesign?2018-08-02T06:31:05ZAndré AnjosInput/Output/Source/Sink concept redesign?The input/output/source/sink concepts should be re-encoded in order to simplify their relationship. Do we really need separated defintions for Input/Source and Output/Sink?The input/output/source/sink concepts should be re-encoded in order to simplify their relationship. Do we really need separated defintions for Input/Source and Output/Sink?