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
Sweeper plugins may call a launcher multiple times, this means the launcher can no longer know the hydra.job.num without preserving state (which is a bad idea).
@jrapin, this is landing soon.
It solve a problem you may have missed with sweeper plugins that have multiple batches sent to the launcher, where the output directories of the jobs from each batch would overwrite from the previous batch.
It's a pretty easy fix.
there are also some new generic sweeper tests that you may want to try to include.
In particular, see
class BatchedSweeperTestSuite:
def test_sweep_2_jobs_2_batches(): ...
This function launches 6 jobs and expectes the sweeper to split them into two batches of 3.
See the example sweeper in the plugin to see how to use it. I am not sure it will be easy to integrate with your sweeper but it would be good to try.
Sweeper plugins may call a launcher multiple times, this means the launcher can no longer know the hydra.job.num without preserving state (which is a bad idea).
Change Launcher launch API to:
For the BasicSweeper, the change amounts to:
specifically, see how initial_job_idx is passed to the launcher in each batch, and hen being advanced by the batch size.
The text was updated successfully, but these errors were encountered: