Hi @abhiskk,

I've looked into disabling waiting for the jobs to return, and I've run into a problem: Hydra's sweepers plugins expect the launcher to return information about the launched job (including the return value).

For example, you'll see here that Hydra's BasicSweeper collects the returned values from each job in the sweep. An exception is raised if the job does not return a value. The same is true of Hydra's other sweeper plugins.

I think making this work in a clean way would require changes to Hydra's sweeper API.

One limitation is that we can not execute several scheduling commands in a loop.

Maybe there's another way we can work around this limitation. Could you please share an example of how you're running the for loop? Is it a loop in python or in bash? Is there a reason you're using a for loop instead of using a hydra sweep?

If there's no other workaround, we can add an option to have the submitit launcher use a dummy return value (e.g. return None).

Any update on this? It would be very uesful.

+1. This would be very useful. I am using an HPC and need to launch experiments on a login node via hydra and hydra_submitit_launcher. It would be very convenient to exit the process for launching once the actual jobs are sent to the computing nodes.

A simple workaround is to launch your command in the background with & (possibly combined with nohup if you're not using some kind of persistent shell like tmux or screen).

It is not a good idea, since if you are submitting 400 jobs, it will exceed the thread limit of some servers.

But if you only submit 10 jobs, it is fine.

Any progress on this?