We expect the incremental campaign to start (1, 1) then (1, 0) then (1, 0) clients and servers.
But I observed that the above results in starting (1, 1) then (1, 1) then (1, 1) clients and servers.
We want to support constant parameters in the zipped parameters.
Indeed parameters are treated separately leading the second line to always have previous_servers=0 and current_servers=0. This is due to the plist.index to return the first index of the occurence in a list.
Currently if one specifies:
We expect the incremental campaign to start (1, 1) then (1, 0) then (1, 0) clients and servers. But I observed that the above results in starting (1, 1) then (1, 1) then (1, 1) clients and servers.
We want to support constant parameters in the zipped parameters.
The function
generate_current_values
(https://github.com/msimonin/ombt-orchestrator/blob/9204476ec555ae3597019cea9a8b0d665350941b/orchestrator/campaign.py#L82) and the line : https://github.com/msimonin/ombt-orchestrator/blob/9204476ec555ae3597019cea9a8b0d665350941b/orchestrator/campaign.py#L92-L93 causes the above behaviour.Indeed parameters are treated separately leading the second line to always have
previous_servers=0
andcurrent_servers=0
. This is due to theplist.index
to return the first index of the occurence in a list.