This won't be an issue once we're getting results straight from pyenergy, but at the moment pyenergy doesn't produce the results file quickly enough for the framework.
A quick fix for now is to wait for the output file to be produced with a while loop before moving on, and to delete the output file (with os.remove) once it's been read.
This won't be an issue once we're getting results straight from pyenergy, but at the moment pyenergy doesn't produce the results file quickly enough for the framework.
A quick fix for now is to wait for the output file to be produced with a while loop before moving on, and to delete the output file (with os.remove) once it's been read.