Commit 12b6da33d49d60ae799c00670e763aa174a5b695
1 parent
18f94e48
Exists in
proximity_effects
Update README_proximity_effects.md and version number in proximity_effects branch
Showing
2 changed files
with
18 additions
and
2 deletions
Show diff stats
README_proximity_effects.md
@@ -12,3 +12,19 @@ fasthenry will need to be installed and fasthenry executable directory | @@ -12,3 +12,19 @@ fasthenry will need to be installed and fasthenry executable directory | ||
12 | must be in the users $PATH | 12 | must be in the users $PATH |
13 | 13 | ||
14 | The SACAMOS/bin directory must also be in the users $PATH so as to be able to run write_FH_input_file which creates input files for fasthenry. | 14 | The SACAMOS/bin directory must also be in the users $PATH so as to be able to run write_FH_input_file which creates input files for fasthenry. |
15 | + | ||
16 | +PROXIMITY_EFFECT_TEST_CASES | ||
17 | + | ||
18 | +A set of proximity effect test cases may be found in the directory: | ||
19 | +PROXIMITY_EFFECT_TEST_CASES | ||
20 | + | ||
21 | +There are a number of sub-directories, each corresponding to a particular scenario. | ||
22 | +The sub-directories may contain a number of SACAMOS test runs with different | ||
23 | +flags set in the input files to deomonstrate particular aspects of the model, and | ||
24 | +also to create comparison results with the original SACAMOS models (no use of fasthenry). | ||
25 | + | ||
26 | +The full set of test cases can be run from the PROXIMITY_EFFECT_TEST_CASES directory with the command | ||
27 | + | ||
28 | +run_test_cases | ||
29 | + | ||
30 | +The results must be viewed by going to the individual test case directories. |
version_information.inc