Skip to content

Increasing npool of dynesty sampler while the run is in progress

Can the npool be increased in the dynesty sampler while the run is in progress?

I had a bilby_pipe job with ncpus=npool=32. I first quit a job and launched another run after keeping the resume files in the result directory. I modified both the ncpus and npool in the new configuration file to be 64. The new error file shows that it's setting up the multiprocessing pool with a new number supplied in the config file, but htop shows that the number of running jobs is the same as the older one.

Also, I have checked the column of LoadAv by running this command condor_status -cons 'JobId=="123.0"'. It shows the same as I can see from htop. The value in the LoadAv column is always smaller than the older one. I did this check with bilby 2.1.1, bilby_pipe 1.0.7, and dynesty 2.1.2.