@@ -12,36 +12,48 @@ This section describes the use of the pre-existing programs, once the binaries h
### cluster
1. cd to the `build/cluster` folder
2.run `edfb`
1. cd to the `build/cluster` folder.
2.Run `edfb`:
> ./edfb
3.run `clu`
3.Run `clu`:
> ./clu
*NOTE:* both `edfb` and `clu` expect an input which is assumed to be in a folder named `../../test_data/cluster/` (i.e. two levels above the current execution path)
*TODO:* set up a code variable to locate the input data (data file paths should not be hard-coded)
4. Run `np_cluster`:
> ./np_cluster
*NOTE:* The C++ version does not need to run a configuration program because all configuration operations are handled by the code at run-time.
5. Check the consistency between the output files (the default output file for the FORTRAN code is named `OCLU`, while the corresponding C++ output has the default name of `c_OCLU`).
### sphere
1. cd to the `build/sphere` folder
2.run `edfb`
1. cd to the `build/sphere` folder.
2.Run `edfb`:
> ./edfb
3.run `sph`
3.Run `sph`:
> ./sph
*NOTE:* both `edfb` and `sph` expect an input which is assumed to be in a folder named `../../test_data/sphere/` (i.e. two levels above the current execution path)
*TODO:* set up a code variable to locate the input data (data file paths should not be hard-coded)
4. Run `np_sphere`:
> ./np_sphere
*NOTE:* The C++ version does not need to run a configuration program because all configuration operations are handled by the code at run-time.
5. Check the consistency between the output files (the default output file for the FORTRAN code is named `OSPH`, while the corresponding C++ output has the default name of `c_OSPH`).
### trapping
The execution of trapping programs requires at least one of the previous programs to have produced a complete output set.
*TODO:*investigate which conditions allow `clu` or `sph` to write `TTMS` output files.
*TODO:*Define a common format for binary I/O operations on the TTMS file.