@@ -33,7 +33,7 @@ This section describes the use of the single programs that make up the *NP_TMcod
2. copy the test data in the current working folder
> cp ../../test_data/cluster/DEDFB .
>
> cp ../../test_data/cluster/DCLU .
3. Run `edfb_clu`:
@@ -66,7 +66,7 @@ The default behaviour of `np_cluster` is to take the same input files as `edfb_c
2. copy the test data in the current working folder
> cp ../../test_data/sphere/DEDFB .
>
> cp ../../test_data/sphere/DSPH .
3. Run `edfb_sph`:
@@ -110,10 +110,8 @@ The execution of trapping programs requires at least one of the previous program
5. Check the consistency between `np_trapping` output files (`c_force_cs.txt` and `c_torque_cs.txt`) and the legacy *FORTRAN* output for this case (the files named, respectively, `fort.66` and `fort.67` in the `test_data/trapping/` folder). Consider that some of the output values will be affected by numeric noise and take substantially different values. However, this is expected for results whose order of magnitude is clearly below the precision level of the calculation, as they represent results approaching zero that were just approximated with different precision. This can be done using the `pycompare.py` script (which requires _Python 3_):
(where the `--data-order=-10` option tells the script to consider as data only nummbers down to the order of 1e-10 and ignore anything below this limit).
