Improve accuracy test description

README.markdown

@@ -27,6 +27,16 @@ on the raw FP performance but tests the memory bandwidth, numa effects and scala
 
  - [EAGLE](./eagle/README.markdown) (Multi node weak scaling test)
 
+# Important: Accuracy tests
+
+If the code is altered, new compiler flags added or anything is done that may change the accuracy of
+the solver, a test of the accuracy needs to be performed. This can be done (to first order) using
+the test:
+
+ - [Small cosmo volume](./small_cosmo_volume/README.markdown) (Cosmological integration accuracy test)
+
+This produces a small meaningful metric for the simulation that can be tested against a reference solution.
+Please provide us with this file for all of your compiler combinations.
 
 # Notes on Benchmark Inputs
 
@@ -44,13 +54,3 @@ Side tables of size < 100 MB are also required for the EAGLE run.
 Please save files named `timesteps_<NUM_THREADS>.txt` as these contain information about performance.
 If you want to assess performance, you should take the second last column "Wall-clock time [ms]" of this file, discard the 0th time step and sum up the rest of the entries.
 Lower values are better for this.
-
-# Accuracy tests
-
-If the code is altered, new compiler flags added or anything is done that may change the accuracy of
-the solver, a test of the accuracy needs to be performed. This can be done (to first order) using
-the test
-
- - [Small cosmo volume](./small_cosmo_volume/README.markdown) (Cosmological integration accuracy test)
-
-This produces a small meaningful metric for the simulation that can be tested against a reference solution.