VLIDORT User's Guide

More documents

Recommendations

Info

and carried on with this default. If there is a fatal error during the execution of VLIDORT, thenthe model will bypass any further calculation and exit with an error message and 3 error traces toindicate the source of the error. In this case, the STATUS_CALCULATION integer output willhave the value VLIDORT_SERIOUS. There are no warnings here; all errors in execution arefatal. More details on the exception handling are in section 4.5.program main_VLIDORT! Module files for VLIDORTUSE VLIDORT_PARSUSE VLIDORT_IO_DEFSUSE VLIDORT_INPUTSUSE VLIDORT_MASTERS! Negate implicit typingimplicit none! Status declarationsINTEGER :: STATUS_INPUTCHECK, STATUS_CALCULATION! Initialize status variables to 0STATUS_INPUTCHECK=0; STATUS_CALCULATION=0! Determine File-read Control variables in Input Structurescall VLIDORT_INPUT_MASTER &(‘VLIDORT.inp’, & ! InputVLIDORT_FixIn, & ! OutputsVLIDORT_ModIn, & ! OutputsVLIDORT_InputStatus ) ! Outputs! Set number of threads (e.g. number of wavelengths)nthreads = 8! Assign Physical (Optical property) input variables for all threads:call USER_VLIDORT_PREPARE! Start thread loop; this can be put in OPEN_MP environmentsdo i = 1, nthreads! VLIDORT master call and error checkcall VLIDORT_MASTER ( &VLIDORT_FixIn, &VLIDORT_ModIn, &VLIDORT_Sup, &VLIDORT_Out )call VLIDORT_WRITE_STATUS ( &STATUS_FILE_NAME, &STATUS_FILE_UNIT, &STATUS_FILE_FLAG, &VLIDORT_Out%Status )! End thread or wavelength loopend do! finishwrite user-defined output arraysstop62
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
Page 1:
User’s GuideVLIDORTVersion 2.6Rob
Page 5 and 6:
Table of Contents1H1. Introduction
Page 7 and 8:
1. Introduction to VLIDORT1.1. Hist
Page 9 and 10:
Table 1.1 Major features of LIDORT
Page 11 and 12: In 2006, R. Spurr was invited to co
Page 13: corrections, and sphericity correct
Page 16 and 17: Matrix Π relates scattering and in
Page 18 and 19: m⎛ P⎞l( μ)0 0 0⎜⎟mmm ⎜ 0
Page 20 and 21: In the following sections, we suppr
Page 22 and 23: of the single scatter albedo ω and
Page 24 and 25: Here T n−1 is the solar beam tran
Page 26 and 27: ~ + ~ ~ (1)~ ~ + ~ ~ (2)~ ~ − ~ 1
Page 28 and 29: The solution proceeds first by the
Page 30 and 31: Linearizations. Derivatives of all
Page 32 and 33: For the plane-parallel case, we hav
Page 34 and 35: One of the features of the above ou
Page 36 and 37: L↑↑ ↑k (cot n −cotn −1)[
Page 38 and 39: Note the use of the profile-column
Page 40 and 41: βl,aer(1)(2)fz1e1βl+ ( 1−f ) z2
Page 42 and 43: For BRDF input, it is necessary for
Page 44 and 45: streams were used in the half space
Page 46 and 47: anded tri-diagonal matrix A contain
Page 48 and 49: in place to aid with the LU-decompo
Page 50 and 51: In earlier versions of LIDORT and V
Page 53 and 54: 4. The VLIDORT 2.6 package4.1. Over
Page 55 and 56: (discrete ordinates), so that dimen
Page 57 and 58: Table 4.2 Summary of VLIDORT I/O Ty
Page 59 and 60: Table 4.3. Module files in VLIDORT
Page 61: Finally, modules vlidort_ls_correct
Page 65 and 66: $(VLID_DEF_PATH)/vlidort_sup_brdf_d
Page 67 and 68: Finally, the command to build the d
Page 69 and 70: Here, “s” indicates you want to
Page 71 and 72: The main difference between “vlid
Page 73 and 74: to both VLIDORT and the given VSLEA
Page 75 and 76: STATUS_INPUTREAD is equal to 4 (VLI
Page 77 and 78: 5. ReferencesAnderson, E., Z. Bai,
Page 79 and 80: Mishchenko, M.I., and L.D. Travis,
Page 81: Stamnes K., S-C. Tsay, W. Wiscombe,
Page 84 and 85: Table A2: Type Structure VLIDORT_Fi
Page 86 and 87: DO_WRITE_FOURIER Logical (I) Flag f
Page 88 and 89: USER_LEVELS (o) Real*8 (IO) Array o
Page 90 and 91: angle s, Stokes parameter S, and di
Page 92 and 93: DO_SLEAVE_WFS Logical (IO) Flag for
Page 94 and 95: 6.1.1.8. VLIDORT linearized outputs
Page 96 and 97: NFINELAYERS Integer Number of fine
Page 98 and 99: 6.1.2.4. VLIDORT linearized modifie
Page 100 and 101: The output file contains (for all 3
Page 102 and 103: The first call is the baseline calc
Page 104 and 105: for a 2-parameter Gamma-function si
Page 106 and 107: Remark. In VLIDORT, the BRDF is a 4
Page 108 and 109: 6.3.3.1. Input and output type stru
Page 110 and 111: Table C: Type Structure VBRDF_LinSu
Page 112 and 113:
Special note regarding Cox-Munk typ
Page 114 and 115:
squared parameter, so that Jacobian
Page 116 and 117:
6.4. SLEAVE SupplementHere, the sur
Page 118 and 119:
is possible to define Jacobians wit
Page 120 and 121:
etween 0 and 90 degrees.N_USER_OBSG
Page 122:
6.4.4.2 SLEAVE configuration file c
show all

VLIDORT User's Guide

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?