GitLab

Use similar setup as the loop experiment for globals and processor
algorithm specific parameters to ensure the tests cover also these
cases.

Useful for beat/beat.editor> v2 tests

Fix loop parameters handling

See merge request !93

Samuel GAIST authored Sep 18, 2019 and André Anjos committed Sep 18, 2019

Only the global parameters values were used for the setup.

Make loop processor related fields clearer

See merge request !92

Improve loop algorithms crosschecking for experiment

See merge request !91

The current technique use had a flaw. With algorithm containing
a different number of groups, it would truncate the to the shortest
as explained in the zip function documentation.

Now itertools.zip_longest is used to ensure that the iteration is
done on the longest input.

Fix loop field names

See merge request !90

This makes them coherent with the algorithm types.

This makes them coherent with the algorithm types.

Improve algorithm setup handling in local executor

See merge request !89

With Python 3.7, the runner failing its creation
doesn't propagate the same as with Python 3.6.

Improve two loops testing

See merge request !88

This patch updates the naming of the blocks as well as
change the algorithm used in the blocks part.

This allows to improve testing for the beat/beat.editor> v2
version.

Simple algorithm with parameter that will help
also validate beat/beat.editor> v2 editors.

This allows to know directly which algorithm failed

Remove parameters from analyzer block

Closes #87

See merge request !87

Remove the possibility to parametrize an analyzer as it creates
unwelcomed side effects.

Fixes #87

Fix two_loops experiment declaration

See merge request !86

Change loop parts name

Closes #86

See merge request !85

This makes the content of the prefix clearer and
easier to understand.

They are now loop_evaluator and loop_processor.

Their respective type values are also updated.

Loop synchronized read

Closes #85

See merge request !84

Loop block output

Closes #84

See merge request !83

This test implements a more complex toolchain
and experiment that will check that loop blocks
are working in more involved setups.

New version of the scripts takes it as an option rather
than a parameter.

New version of the scripts takes it as an option rather
than a parameter.

Rather than having a loops field containing only the "loop"
blocks, they have now become their own entity like "blocks" and
"analyzers".

This new type of block will contain all the information needed
for both the loop user algorithm and for the loop itself as
they work in pair anyway.

Rather than having a loops field containing only the "loop"
blocks, they have now become their own entity like "blocks" and
"analyzers".

This new type of block will contain all the information needed
for both the loop user algorithm and for the loop itself as
they work in pair anyway.

This makes the code easier to read and maintain.

This closes all the outputs of the executor.

All other assets can have it. There seems to not be
any reason to make database an exception.