Simulate a panorama. Only works with mc_sensorposition, mc_sample_grid and mc_backward. Can best be explained by following example:



mc_panorama_view PHI_1 PHI_2 THETA_1 THETA_2
mc_sensorposition X Y Z
mc_sample_grid NPHI NTHETA [] []
mc_backward NPHI1 NTHETA1 NPHI2 NTHETA2

 

or, with numbers:



mc_panorama_view 45 135 80 180
mc_sensorposition 3000 3000 26
mc_sample_grid 90 100 [] []
mc_backward 10 0 10 99

 

In this example, mc_panorama_view defines the camera to cover the area between 10 degrees below the horizon (80 degrees from nadir, looking into the ground) and the zenith (180 degrees from nadir), and looking into the directions between south-west (45) and north-west (135). The camera is positioned at x=3km, y=3km and z=26m, see mc_sensorposition. The number of pixels that the camera has is defined by mc_sample_grid, hence the camera horizontal resolution is 1 degree in the horizon: (135-45)/90. The camera vertical resolution is also 1 degree: (180-80)/100. This run only calculates one vertical line at phi=55.5 (see mc_backward). The square brackets in the line mc_sample_grid are usually dx and dy, they are set automatically in the presence of 3d clouds. If no clouds are present, you need to set them, if you use mc_elevation_file, you need to set them consistent with the elevation file. NOTE: If you have formerly used mc_panorama, this is what has changed: The order of the numbers has changed: Formerly, we wrote mc_panorama MU_1 MU_2 PHI_1 PHI_2, where MU_i=cos(THETA_i). In the options mc_sample_grid and mc_backward, X and Y have been swapped. Although these changes are far from being nice, they are necessary to introduce a conform nomenclatur throughout libRadtran. Sorry for that. (CAUTION! The definition of phi for panoramas was formerly different than that of phi! This has been changed on 19.11.2010!)