CLARE 98 (CHILBOLTON, UK)
Data set of the DLR Lidar ALEX onboard the FALCON aircraft
Arbeitsgruppe LIDAR - DLR Oberpfaffenhofen, D-82234 Weßling
Tel.: 0049 +8153-281103
Fax: 0049 +8153 281271
The FALCON aircraft took part at the CLARE campaign from 12-23 October 1998. It carried a downward looking aerosol lidar (ALEX) measuring the backscatter coefficient using the frequency doubled and tripled light of a Ne:YAG laser. Backscatter coefficients at (355nm,) 532nm and 1064nm are available for:
12 October 98 (Transferflight), 6:50 - 7:35 UTC
13 October 98, 12:16 - 14:40 UTC
14 October 98, 11:38 - 13:43 UTC
20 October 98, 9:25 - 10:50 + 12:43 - 14:55 UTC
21 October 98, 9:57 - 10:50 UTC
The quicklook files contain:
The 3-panels of vertical along-flight-path sections are contour plots of the backscatter ratio at 1064nm and at 532nm as well as the depolarisation at 532nm. The backscatter ratio (total scattering of particles + molecules devided by molecular scattering) gives the relative contribution of particle scattering to the received signal. It is always larger than 1 and is equal to1 if only Rayleigh scattering by molecules occurs.
The depolarisation is the ratio of received light intensities in two different channels polarized paralelly and perpendicularly towards the incident laser beam. It is a qualitative measure of the non-spericity of the scattering particles. A depolarisation about 1.4% occurs if only the unsymmetric air-molecules contribute to depolarisation. If depolarising (non-spherical, solid) particles are within the measured volume the volume-depolarisation is between 1.4% and 100% depending on the concentration and shape of the scatterers. Clouds with spherical (liquid) particles cause a depolarisation below 1.4% since only the intensity in the parallel channel is increased.
Since the backscatter ratios are not corrected for extinction, shading occurs behind dense clouds due to the attenuation inside them. The relatively low remaining light intensity behind the cloud feigns low backscatter.
7 October 1998
There is no FALCON data from 7 October since the FALCON did not yet operate.
13 October 1998
clare981013.igd5.ps: W to E section starting on 13 October about 1340 UT (not extinction-corrected).
clare981013.igd6.ps: the according E to W section starting on 13 October about 1346 UT (not extinction-corrected).
clare981013.prof5.ps and clare981013.prof6.ps: extinction-corrected vertical profiles over Chilbolton on 13 October at 13:39:52 UT and 13:45:48 UT, respectively.
20 October 1998
clare981020.igd11.ps: E to W section starting on 20 October about 14:15 UT (not extinction-corrected)
clare981020.igd12.ps: the according W to E section starting on 20 October about 14:33 UT (not extinction-corrected).
clare981020.prof11.ps and clare981020.prof12.ps: extinction-corrected vertical profiles over Chilbolton on 20 October at 14:20:30 UT and 14:32:32 UT, respectively.
clare981020.igd13.ps: E to W section starting on 20 October about 14:49 UT (not extinction-corrected)
clare981020.prof13.ps: the extinction-corrected profile over Chilbolton on 20 October, 14:54:32 UTC.
Due to a lack of fuel the leg in the opposite direction was not flown.
21 October 1998
For 21 October only for one leg data is available since the ARAT and the FALCON stopped the measurements at 10:51 due to low cloud cover.
clare981021.igd4.ps: W to E section starting on 21 October about 1043 UTC (not extinction-corrected).
clare981021.prof4.ps: extinction-corrected vertical profile over Chilbolton at 10:49:54 UTC.
HDF-FILES
Part of the FALCON Lidar data on this server are in Hierarchical Data Format (HDF) carrying the extension .hdf.
The .hdf files in the ...falcon/data directory are named in analogy to the Quicklook (...igd*.ps) files described above. (e.g. clare981021.4.hdf corresponds to the Quicklook clare981021.igd4.ps which means the 4th flight leg on 21 Oct 98, and so on).
However the data is given in terms of backscatter coefficient, while the Quicklooks show backscatter ratio as explained above. Available wavelengths are 1064nm, 532nm, and 354nm.
Reading the .hdf files is quite easy (idl Version 5.1): As is documented in the idl online help (see 'hdf_read') there are mainly two ways, either creating a reusable template with the function 'hdf_browser' or extracting the data directly (also by use of 'hdf_browser' but without re-use option) with the function 'hdf_read'' e.g. by typing '' datastructure=hdf_read()'' to the idl prompt. You then will be asked for the filename and the browser will be opened automatically. Reading of two lowermost items can be dis- or enabled by de- / activating the read button for the single datasets. (With this I think it is not neccessary to provide an additional .pro to read the files.)
ASCII-FILES
Single Profiles of attenuated backscatter-coefficient are available in ASCII format like this:
Backscatter coefficient [1/m sr] at ***nm on 'date'...'time'....'#shots'...'latitude'...'longitude'
This file contains each 896 entries of altitude and bs-coefficient -0.03345 -0.03278 .................[km] 2.9753e-8 2.756e-8 .................[1/m sr] (eof) |
More explanations can be requested from Arbeitsgruppe LIDAR
Last modified: 26 Feb1999, 11:00 CET
by Harald Flentje (harald.flentje@dlr.de)