beat.backend.python merge requestshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests2018-11-23T14:43:43Zhttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/26Refactor execution2018-11-23T14:43:43ZSamuel GAISTRefactor executionThis patch set moves the execution related classes in their own sub-package.
This makes the "core" parts and the "execution" parts more cleanly separated.This patch set moves the execution related classes in their own sub-package.
This makes the "core" parts and the "execution" parts more cleanly separated.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/27Soft loop2018-11-27T10:40:11ZSamuel GAISTSoft loopImplement soft loop
Part of https://gitlab.idiap.ch/beat/beat.core/issues/59Implement soft loop
Part of https://gitlab.idiap.ch/beat/beat.core/issues/59Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/29Give loop full access to input content in prepare2018-12-12T14:09:11ZSamuel GAISTGive loop full access to input content in prepareUnlike other autonomous algorithm, loop must have access to
everything directly in the prepare method so it can properly setup
everything for validation.Unlike other autonomous algorithm, loop must have access to
everything directly in the prepare method so it can properly setup
everything for validation.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/31Add parameter to specify configuration section to load for databases_provider2018-12-14T08:06:54ZSamuel GAISTAdd parameter to specify configuration section to load for databases_providerWith the current implementation, the configuration of the
execution process may contain two entries:
1) Main algorithm
2) Loop algorithm
The way the databases provider works will only load the main
entry which means that it will use the...With the current implementation, the configuration of the
execution process may contain two entries:
1) Main algorithm
2) Loop algorithm
The way the databases provider works will only load the main
entry which means that it will use the wrong configuration
for the loop algorithm. This new parameter allows to set
which entry should be used to configure the database. The
default is None so the default behaviour doesn't change.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/36Fix handling of string when packing2018-12-19T10:16:53ZSamuel GAISTFix handling of string when packingThe size used for packing the string was wrong because it used the
original string lenght rather than the encoded.The size used for packing the string was wrong because it used the
original string lenght rather than the encoded.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/41Template protocol2019-04-18T12:51:30ZSamuel GAISTTemplate protocolThis merge request implements the support for database V2 with protocol details moved into the ProtocolTemplate object.
This allows for reuse of these templates that were previously duplicate for each entry in the database definition....This merge request implements the support for database V2 with protocol details moved into the ProtocolTemplate object.
This allows for reuse of these templates that were previously duplicate for each entry in the database definition.
Fixes #20
Related to beat/beat.core#64Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/42Use format for string formatting2019-04-16T09:50:41ZSamuel GAISTUse format for string formattingThis package is still compatible and used with Python 2.7
processing environments.
It's also used in production which is running Python 3.5.
This makes the use of the new "fast" string notation not yet
possible.This package is still compatible and used with Python 2.7
processing environments.
It's also used in production which is running Python 3.5.
This makes the use of the new "fast" string notation not yet
possible.Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/43Cleanup handling of database schema version2019-04-18T12:51:46ZSamuel GAISTCleanup handling of database schema versionThis way beat/beat.core> doesn't depend on updating the
is_v1 flag.
part of #20
Related to beat/beat.core#64This way beat/beat.core> doesn't depend on updating the
is_v1 flag.
part of #20
Related to beat/beat.core#64Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/44Fix protocol view definition generation2019-04-18T12:51:56ZSamuel GAISTFix protocol view definition generationThe parameter field was missing.
part of #20
Related to beat/beat.core#64The parameter field was missing.
part of #20
Related to beat/beat.core#64Soft loopsSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/46Improve asset information2019-05-06T12:43:24ZSamuel GAISTImprove asset informationThis merge request moves some information in the Storage class so that it's easier to re-use it rather than having strings all around the code base.
The presence of the class member is checked and will raise an exception if not filled.
...This merge request moves some information in the Storage class so that it's easier to re-use it rather than having strings all around the code base.
The presence of the class member is checked and will raise an exception if not filled.
beat/beat.core> will need to be updated as well since some of the storage class are defined there.Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/49Add dummy documentation to assets in prefix2019-06-04T10:16:29ZSamuel GAISTAdd dummy documentation to 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.backend.python/-/merge_requests/50Add *.rst to list of files to include from test prefix2019-06-06T07:05:50ZSamuel GAISTAdd *.rst to list of files to include from test prefixThis merge request add the .rst files from the test
prefix to the package.
They will be used in tests of other packages like
beat/beat.editor>
A new algorithm has been created for missing
documentation related tests.This merge request add the .rst files from the test
prefix to the package.
They will be used in tests of other packages like
beat/beat.editor>
A new algorithm has been created for missing
documentation related tests.Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/53Improve language auto discovery2019-06-28T12:46:18ZSamuel GAISTImprove language auto discoveryCurrently the auto discovery of the language doesn't take
into account usual errors related to loading a json file.
This patch adds more failure handling that should cover
these.
Fixes beat/beat.editor#232Currently the auto discovery of the language doesn't take
into account usual errors related to loading a json file.
This patch adds more failure handling that should cover
these.
Fixes beat/beat.editor#232Soft loopsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/54Implement loop output2019-07-29T13:02:19ZSamuel GAISTImplement loop outputThis merge request implements output writing from the loop block.
Following conversations with interested parties:
- The loop block must have an output
- The loop block shall be notified when a loop user block writes on its outputs
...This merge request implements output writing from the loop block.
Following conversations with interested parties:
- The loop block must have an output
- The loop block shall be notified when a loop user block writes on its outputs
Part of beat/beat.core#84Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/55New loop user types2019-07-11T17:45:34ZSamuel GAISTNew loop user typesThis merge request implements the support for
both autonomous and sequential loop user types.This merge request implements the support for
both autonomous and sequential loop user types.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/56Fix loop dataformat export2019-07-12T15:10:05ZSamuel GAISTFix loop dataformat exportThis merge request fixes handling of the dataformat objects
in the algorithm.
This allows to properly export all dataformats used be it
in input, outputs or loop communication.
Tests have been update to ensure that different dataformat...This merge request fixes handling of the dataformat objects
in the algorithm.
This allows to properly export all dataformats used be it
in input, outputs or loop communication.
Tests have been update to ensure that different dataformats
are used for these various elements.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/58Change loop parts name2019-07-31T08:12:04ZSamuel GAISTChange loop parts nameAfter experience and discussions, the xxx_loop_user and xxx_loop
algorithm type names are not well expressing what the
corresponding algorithms do.
This patch changes their name to:
- xxx_loop_processor
- xxx_loop_evaluator
W...After experience and discussions, the xxx_loop_user and xxx_loop
algorithm type names are not well expressing what the
corresponding algorithms do.
This patch changes their name to:
- xxx_loop_processor
- xxx_loop_evaluator
Which are clearer for the role of each.
Part of beat/beat.core#86Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/59Do not systematically decode incoming zmq parts2019-09-25T09:25:30ZSamuel GAISTDo not systematically decode incoming zmq partsUnder some circumstances the decoding may fail as the binary
data may contain values outside the utf-8 "visible" range.
Fixes #26Under some circumstances the decoding may fail as the binary
data may contain values outside the utf-8 "visible" range.
Fixes #26Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/60[execution][messagehandlers] Fix write end_data_index handling in LoopMessage...2019-09-27T14:57:08ZSamuel GAIST[execution][messagehandlers] Fix write end_data_index handling in LoopMessageHandlerThe None value is not properly handled and ends up
triggering a warning while it is a valid value for
end_data_index.
This patch fixes this.The None value is not properly handled and ends up
triggering a warning while it is a valid value for
end_data_index.
This patch fixes this.Soft loopsAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/merge_requests/61Improve synchronized output handling2019-10-01T13:10:29ZSamuel GAISTImprove synchronized output handlingThis merge request adds the processor output name that is currently written to the parameters of the evaluator write.
This allows to manage the evaluator write operation more cleanly has the method is called each time a processor output...This merge request adds the processor output name that is currently written to the parameters of the evaluator write.
This allows to manage the evaluator write operation more cleanly has the method is called each time a processor output is written to.
Fixes #27Soft loopsAndré AnjosAndré Anjos