Xopt icon indicating copy to clipboard operation
Xopt copied to clipboard

Asynchronous Xopt does not make a dump file

Open ndwang opened this issue 1 year ago • 2 comments

Hi, I recently updated my xopt from 1.4.1 to 2.2.2. I noticed that running Xopt in parallel (processes, threads, MPI) does not make a dump file anymore. This makes it difficult to see the data and resume halted optimizations.

I'm running https://github.com/ChristopherMayes/Xopt/blob/main/docs/examples/basic/xopt_parallel.ipynb The only modification I made is adding dump_file: dump.yaml to the initialization file.

ndwang avatar Jun 25 '24 15:06 ndwang

It looks like this is a bug: https://github.com/ChristopherMayes/Xopt/issues/235

@ndwang What generator are you using? CNSGA now has its own population file output, which you can restart with. You don't need the dump file for that.

ChristopherMayes avatar Jun 25 '24 18:06 ChristopherMayes

It looks like this is a bug: #235

@ndwang What generator are you using? CNSGA now has its own population file output, which you can restart with. You don't need the dump file for that.

@ChristopherMayes Thanks for looking into this. I found xopt.utils.read_xopt_csv can parse populations files easily and do basically the same thing. I just really liked X = Xopt.from_file('dump.yaml')

ndwang avatar Jun 25 '24 19:06 ndwang