beat.core merge requestshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests2019-07-31T12:41:21Zhttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/84Loop synchronized read2019-07-31T12:41:21ZSamuel GAISTLoop synchronized readThis merge request updates beat/beat.core> to be able
to validate and run experiment using the new synchronized
input reading for loop blocks.
Fixes #85This merge request updates beat/beat.core> to be able
to validate and run experiment using the new synchronized
input reading for loop blocks.
Fixes #85Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/83Loop block output2019-07-31T12:41:21ZSamuel GAISTLoop block outputThis merge request implements support for output of the loop block.
This feature requires a refactor of the toolchain and experiment
changes done to support the loop feature.
Requires beat/beat.backend.python!54
Fixes #84This merge request implements support for output of the loop block.
This feature requires a refactor of the toolchain and experiment
changes done to support the loop feature.
Requires beat/beat.backend.python!54
Fixes #84Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/82Update algorithm for loop user new types2019-07-15T08:51:27ZSamuel GAISTUpdate algorithm for loop user new typesThis merge request updates the algorithm schema
to properly handle the two types of loop user
algorithm.
It also fixes dataformats parsing when loading
an algorithm following the same work done in
beat/beat.backend.python!56
It...This merge request updates the algorithm schema
to properly handle the two types of loop user
algorithm.
It also fixes dataformats parsing when loading
an algorithm following the same work done in
beat/beat.backend.python!56
It also updates the prefix to improve testing.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/81Move all API v1 algorithms in test prefix to their own folder2019-07-02T08:19:46ZSamuel GAISTMove all API v1 algorithms in test prefix to their own folderThis implies update of tests using them as well as
experiments.
This will allow clean separation with API v2 algorithms
and will make testing other elements of the platform
easier.This implies update of tests using them as well as
experiments.
This will allow clean separation with API v2 algorithms
and will make testing other elements of the platform
easier.Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/78Duplicate key handling2019-06-19T05:13:47ZSamuel GAISTDuplicate key handlingThis merge request add support for duplicate key handling.
It also fixes an issue with wrong handling of the absence of "uses" field in algorithms.
Requires beat/beat.backend.python!51
Fixes #82This merge request add support for duplicate key handling.
It also fixes an issue with wrong handling of the absence of "uses" field in algorithms.
Requires beat/beat.backend.python!51
Fixes #82Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/77Add dummy documentation to valid assets in prefix2019-06-04T13:52:12ZSamuel GAISTAdd dummy documentation to valid assets in prefixThis will allow to do more tests in for example
beat/beat.editor>This will allow to do more tests in for example
beat/beat.editor>Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/76Reorganize error related prefix content2019-05-29T14:02:27ZSamuel GAISTReorganize error related prefix contentThis merge request reorganizes the test prefix content
to make it easier to:
- find error related assets
- write error condition based tests
- write correct condition based tests
The last two points not only concern this package but
al...This merge request reorganizes the test prefix content
to make it easier to:
- find error related assets
- write error condition based tests
- write correct condition based tests
The last two points not only concern this package but
also others relying on the beat.core prefix to provide
test data like beat/beat.editor>
It also fixes issues found in some experiment as well
as add new version of some assets for future tests.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/75Add missing class variables to plotter storage2019-05-15T10:31:30ZSamuel GAISTAdd missing class variables to plotter storageFixes the plotter storage class by adding missing class member variables.
The miss went unnoticed because the CodeStorage base class is not a subclass of Storage.Fixes the plotter storage class by adding missing class member variables.
The miss went unnoticed because the CodeStorage base class is not a subclass of Storage.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/74Implement missing prototypes handling2019-05-07T10:47:47ZSamuel GAISTImplement missing prototypes handlingThis merge request adds the missing handling for the database and experiment assets.
**WARNING**: The experiment asset doesn't provide a prototype as it must be filled
based on the toolchain it is create from and the content of the pref...This merge request adds the missing handling for the database and experiment assets.
**WARNING**: The experiment asset doesn't provide a prototype as it must be filled
based on the toolchain it is create from and the content of the prefix.
Fixes #79Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/73Fix plotterparameter writing2019-05-06T13:35:08ZSamuel GAISTFix plotterparameter writingThe write method was wrong as well as there were missing
pieces in the class for it to work properly.
This merge request fixes all these points.
Fixes #78The write method was wrong as well as there were missing
pieces in the class for it to work properly.
This merge request fixes all these points.
Fixes #78Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/72Improve asset information2019-05-06T13:10:38ZSamuel GAISTImprove asset informationFollowing beat/beat.backend.python!46, this merge request add additional information to the storage classes in this module.Following beat/beat.backend.python!46, this merge request add additional information to the storage classes in this module.Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/71Implement support for protocol template prototype2019-05-03T12:32:56ZSamuel GAISTImplement support for protocol template prototypeThis merge request adds the support for creating a default protocol template
Part of #64This merge request adds the support for creating a default protocol template
Part of #64Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/70Add db migration scripts to installed commands2019-05-06T07:22:35ZSamuel GAISTAdd db migration scripts to installed commandsThis merge request adds the database migration script as command on installation.This merge request adds the database migration script as command on installation.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/68Fix simple/2 database code2019-04-18T07:29:40ZSamuel GAISTFix simple/2 database codeThe migration script didn't properly copy the code.
Part of #64The migration script didn't properly copy the code.
Part of #64Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/67Protocol template2019-05-03T12:32:55ZSamuel GAISTProtocol templateThis merge request implements the support for protocol templates.
Part of #64This merge request implements the support for protocol templates.
Part of #64Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/47Implement loop with input test2018-12-17T14:02:23ZSamuel GAISTImplement loop with input testThis set of patch implements a test that can be re-used as example for a loop enabled experiment.This set of patch implements a test that can be re-used as example for a loop enabled experiment.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/43Soft loop2018-12-11T10:51:12ZSamuel GAISTSoft loopThis merge request implements the execution of soft loop blocks.
All currently used runners are implemented.
Requires beat.backend.python >= 1.6.0 (https://gitlab.idiap.ch/beat/beat.backend.python/merge_requests/27)
Fixes #59This merge request implements the execution of soft loop blocks.
All currently used runners are implemented.
Requires beat.backend.python >= 1.6.0 (https://gitlab.idiap.ch/beat/beat.backend.python/merge_requests/27)
Fixes #59Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/60ZMQ architecture documentation2019-03-14T14:32:54ZSamuel GAISTZMQ architecture documentationThis patch adds documentation about the new ZMQ architecture wrt to the scheduler/worker design.
It also updates the API part of the ZMQ communication since it changed with V2.
Fixes #70This patch adds documentation about the new ZMQ architecture wrt to the scheduler/worker design.
It also updates the API part of the ZMQ communication since it changed with V2.
Fixes #70ZMQ resilience improvementAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/58Worker: decode recieved job data if python older than 3.62019-03-15T09:24:23ZSamuel GAISTWorker: decode recieved job data if python older than 3.6Prior to 3.6 the json module handles only str types. After that
more types are supported out of the box.Prior to 3.6 the json module handles only str types. After that
more types are supported out of the box.ZMQ resilience improvementSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/merge_requests/53Zmq refactoring2019-02-26T07:55:37ZSamuel GAISTZmq refactoringThis merge request refactors the ZMQ part of beat.core. |
It improves the reliability of the system at the cost of making it slightly
more complex.
However, the new implementation should avoid connection los...This merge request refactors the ZMQ part of beat.core. |
It improves the reliability of the system at the cost of making it slightly
more complex.
However, the new implementation should avoid connection loss due to inactivity
on the connection. Situation that can happen depending on the network setup
which might kill a connection if no activity is detected.
Fixes #68 ZMQ resilience improvementAndré AnjosAndré Anjos