Issues · vidjil / vidjil · GitLab

Warnings, avoir un nouveau warning si un clone a plusieurs productivité sur différents samples

#4578 · opened Nov 23, 2020 by Thonier Florian !-reflexion bio-productivity client-warning cpp-representative feature server-fuse
- CLOSED
- 1
- 2
updated Dec 09, 2020
Warnings, avoir un nouveau wrning si un clone a plusiuers dénomination sur différents samples

#4566 · opened Nov 20, 2020 by Thonier Florian client-warning feature server-fuse
- CLOSED
- 1
- 6
updated Dec 09, 2020
Warning dans le client et plusieurs samples : simplifier, factoriser

#4032 · opened Nov 05, 2019 by Mikaël Salson !-easy *-go client client-ergonomy client-warning
- CLOSED
- 2
updated Nov 26, 2019
Les warnings ne sont pas produits avec `-c designations`

#3811 · opened Mar 18, 2019 by Mikaël Salson Algo 2020.06 !!-bug !-easy *-go client-warning cpp cpp-finesegmenter
- CLOSED
- 2
- 1
updated Jun 10, 2020
Warning si 2 assignations possibles avec le même score dans `align_against_collection`

#3575 · opened Oct 17, 2018 by Thonier Florian Algo 2018.09 *-go client-warning cpp cpp-dynprog cpp-finesegmenter user-request
- CLOSED
- 1
- 7
updated Oct 19, 2018
vidjil-algo: warning level de W53, similar clone

#3137 · opened Apr 05, 2018 by Mathieu Giraud Algo 2018.04 client-warning cpp cpp-export
- CLOSED
- 1
- 0
updated Jun 12, 2018
Générer les warning levels depuis vidjil-algo

#3136 · opened Apr 05, 2018 by Mathieu Giraud Algo 2018.04 +-working client-warning cpp cpp-export
- CLOSED
- 1
- 0
updated Apr 17, 2018
Différents levels sur les warnings

#3127 · opened Apr 05, 2018 by Mathieu Giraud *-go bio-control client-warning user-request
- CLOSED
- 9
updated Feb 13, 2019
alertes à l'utilisateur en fonction de certaines raisons de non-segmentation

#981 · opened Nov 29, 2016 by Vidjil Team old_tracker bio-control client client-warning cpp-heuristic priority-1-low
- CLOSED
- 1
updated Nov 20, 2018