VLIDORT User's Guide

end program main_VLIDORT4.3.2. Configuration file discussionIn the previous section, we noted that a call to subroutine VLIDORT_INPUT_MASTER enablesvariables to be assigned from a configuration file of inputs. This process assigns values to most(but not all) of the variables in the input Type Structures. The file-read is done using theFINDPAR tool in the source-code module vlidort_aux ; FINDPAR looks for a characterstring made up of a prefix (in this case the word “VLIDORT”) and a text description of thevariable(s) to be assigned and then reads the variable(s) specified underneath the character string.All strings ending with a question mark indicate the assignment of Boolean variables. If thecharacter string is not present, or if the file-read itself is corrupted by bad input, then an errormessage is generated and a status flag set.Tables J, K, L, and M in Appendix 6.1 contain the lists of dedicated character strings and theassociated input variables. These character string tables and their associated VLIDORT inputtype structures are listed in Table 4.4 to give the reader an initial overview.Examples of configuration files are found in the test directories. In the string tables, we presentvariables from the input tables (i.e. the A, B, E, and F Tables in Table 4.2 above) that areassigned using this file-read procedure, along with their associated character strings. It should benoted that some input variables are not file-reads (array inputs mostly). These include some ofthe variables in Input Tables A6, A7, B6, E2, and F2. Some variables in the control inputs arenormally assigned by the user, depending on the application. It is also possible to overwrite filereadassignments, in particular for applications where the number of layers (variable"NLAYERS" in VLIDORT) will be pre-set by a call to generate atmospheric optical properties.Table 4.4 Summary of VLIDORT input configuration file tables of input stringsVLIDORT I/O Type Structure String Table #VLIDORT_Fixed_BooleanJ1VLIDORT_Fixed_ControlJ2VLIDORT_Fixed_SunraysJ3VLIDORT_Fixed_UserValuesJ4VLIDORT_Fixed_ChapmanJ5VLIDORT_Fixed_OpticalJ6VLIDORT_Fixed_WriteJ7VLIDORT_Modified_BooleanK1VLIDORT_Modified_ControlK2VLIDORT_Modified_SunraysK3VLIDORT_Modified_UserValues K4VLIDORT_Modified_ChapmanK5VLIDORT_Fixed_LinControlL1VLIDORT_Modified_LinControl M14.3.3. Makefile discussionAs an example, we now describe the Makefile in the “vlidort_s_test” directory (other Makefilesare similar). The software was compiled and tested at RT Solutions using the Intel® and GNUFORTRAN compilers. The software has also been tested successfully using the Portland Group®63