You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Note: Currently, some, hum, well chosen, parameters can be constant over the
zipped parameters. In the future we may want to extend that to any zipped
parameters.
Fix#110
```
nbr_clients: [1, 1, 1]
nbr_servers: [1, 1, 1]
nbr_calls: [100, 50, 25]
pause: [0.1, 0.2, 0.3]
```
nbr_calls and pause weren't taken into account in the previous iteration
calculation. The framework was misbehaving because, in the above, one new
client and server were started for each iteration.
This addresses #110
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
(ombt-orchestrator/orchestrator/campaign.py
Line 82 in 9204476
and the line :
ombt-orchestrator/orchestrator/campaign.py
Lines 92 to 93 in 9204476
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.The text was updated successfully, but these errors were encountered: