Incorporating John-Luke's edits

Libensemble · Jan 6, 2020 · 8ce8804 · 8ce8804
1 parent 67f91dd
commit 8ce8804
Show file tree

Hide file tree

Showing 3 changed files with 5 additions and 5 deletions.
diff --git a/CHANGELOG.rst b/CHANGELOG.rst
@@ -45,7 +45,7 @@ Release 0.5.2
 * Code has been restructured to meet xSDK package policies for interoperable ECP software (version 0.5.0). #208
 * The use of MPI.COMM_WORLD has been removed. Uses a duplicate of COMM_WORLD if no communicator passed (any process not in communicator returns with an exit code of 3). #108
 * All output from libEnsemble goes via logger. MANAGER_WARNING level added. This level and above are echoed to stderr by default. API option to change echo level.
-* Simulation directories are created only as required and are suffixed by _worker. #146
+* Simulation directories are created only during sim_f calls are suffixed by _worker. #146
 * New user function libE.check_inputs() can be used to check valid configuration of inputs. Can be called in serial or under MPI (see libE API). #65
 * Installation option has been added to install dependencies used in tests ``pip install libensemble[extras]``
 * A profiling option has been added to sim_specs. #170

diff --git a/docs/FAQ.rst b/docs/FAQ.rst
@@ -97,8 +97,8 @@ nodes, while launching all sub-jobs onto other nodes.
 
 **What does "_pickle.UnpicklingError: invalid load key, '\x00'." indicate?**
 
-This has been observed with the OFA fabric and usually indicates MPI messages
-aren't being received correctly when using mpi4py. The solution
+This has been observed with the OFA fabric when using mpi4py and usually
+indicates MPI messages aren't being received correctly. The solution
 is to either switch fabric or turn off matching probes. See the answer for "Why
 does libEnsemble hang on certain systems when running with MPI?"
 

diff --git a/docs/tutorials/local_sine_tutorial.rst b/docs/tutorials/local_sine_tutorial.rst
@@ -234,8 +234,8 @@ That's it! Now that these files are complete, we can run our simulation.
   $ python3 calling_script.py
 
 If everything ran perfectly and you included the above print statements, you
-should get something similar to the following output for ``H``. The columns might
-be rearranged as follows.
+should get something similar to the following output for ``H`` (although the
+columns might be rearranged).
 
 .. code-block::