multi_config experiments currently schedule all jobs at once. That makes sense since there is no sequentiality and the order of evaluation doesn't matter. Still it would be nice to give the user more control over the resources demanded. Ideally, we would give an optional argument to the multi_experiment_args in the experiment .yaml, which states max_number_of_running_jobs at a time or something like that.
This connects with #8 & #9 and should probably addressed together.
multi_configexperiments currently schedule all jobs at once. That makes sense since there is no sequentiality and the order of evaluation doesn't matter. Still it would be nice to give the user more control over the resources demanded. Ideally, we would give an optional argument to themulti_experiment_argsin the experiment.yaml, which statesmax_number_of_running_jobsat a time or something like that.This connects with #8 & #9 and should probably addressed together.