Because the user may want to monitor differences between energy-deposition files, I have written an endep_diff code to do that. This code is also for use on reactions for a one target at a time, and the best way to run it is with the script
endep_diff.script [-Dir_1 dir_name_1] [-Dir_2 dir_name_2] \
[-Lib_1 lib_name_1] [-Lib_2 lib_name_2]
The first set of data may either be in an ENDL-type directory
such as dir_name_1 or in the form of an endl.asc file, as
given by lib_name_1, and analogously for the second data set.
For example, a common use of endep_diff would be to compare a new set of energy depositions with the corresponding current ENDL data. Because the output of endep.script includes a lib.new file in endl.asc format, a natural way to compare this with ENDL data, e.g., for lithium 6, is to run
endep_diff.script -Dir_1 /nds/data/endl/za003006 -Lib_2 lib.new
The default threshold for flagging differences in energy deposition is 1%, but the user may set a different threshold in an endep.input file. For example, if you want a 2% threshold, include the lines
&endep_diff_opt diff_tol = 0.02/in your endep.input file. Note that the same endep.input file may be used for both the endep and endep_diff codes, basically because the namelists have different identifiers.
The output of endep_diff is a file endep_diff.log, and the format of this file is as follows. The results are ordered by reaction (c identifier) and by secondary particle. If the energy depositions for a data set agree to within the prescribed tolerance, no further data is printed. Otherwise, the energies of the incident particle for both data sets are given, along with the energy depositions from the first library. When the relative difference exceeds the tolerance, the deposition from the second library is also given, as well as the relative difference.