Doppler lidar wind profiling: long-term assessment of the perpendicular vertical sweeps reconstruction method
Abstract. Doppler lidars have become a relatively common tool to measure wind profiles in the lower troposphere, as commercial instruments improved and became more accessible to answer the demand, notably from the wind energy industry. Most often, the Doppler Beam Swinging (DBS) technique is used to reconstruct the horizontal wind profile from the radial wind raw observations, because it is implemented in the software of commercial Doppler lidars. However, the DBS leaves a blind zone near the ground that makes it difficult to observe very low-altitude phenomena such as certain low-level jets, plus the wind profiles can be noisy if most of the lidar observation time is dedicated to other types of sweeps. However, the horizontal wind can also be reconstructed by combining observations from two vertical sweeps of the Range-Height Indicator (RHI) type, recorded in perpendicular directions. Radial wind observations are binned into horizontal layers, which allows to retrieve both the average wind and its variance, providing an estimation of the horizontal part of the turbulent kinetic energy (TKE). This work introduces a method to take into account the flow inclination over sloping terrains, as well as filter the range-folded echoes from high-altitude clouds. The horizontal wind speed and direction retrieved with this cross-RHI method were compared with standard DBS observations over six months of observations in total, recorded at two urban sites in France, one coastal flat city (Dunkerque) and one continental hilly megacity (Paris). The wind speed intercomparison below 200 m altitude yielded very good correlation coefficients around 0.85 on both sites, with a cross-RHI-vs-DBS fitting slope of 0.93. At higher altitudes, up to 3 km, results were even better as range-folded echoes from clouds disappeared from the DBS, with correlation coefficients and slopes both around 0.97 for altitudes above 1 km. The wind direction showed higher dispersion, though in Dunkerque, 83 % of points below 200 m had an error lower than 10°, and 62 % in Paris, where there was no averaging over several DBS cycles. Again, results improved with increasing altitude, demonstrating that the cross-RHI wind reconstruction method can be used to retrieve full-height wind profiles without limiting the sweeps to low-elevation beams. In addition, case studies highlighted the ability of the cross-RHI technique to operate with low aerosol loads, range-folded echoes, and convective conditions. The two-dimensional flow inclination angle could be optimized successfully for about 88 % of the RHI pairs on both sites. The most frequent tilt angle was around 0.6° in Dunkerque and 1.0° in Paris, with 95 % of the values below 8°, though the direction of the steepest slope could only be partially related with the orography. In Paris, the decrease in horizontal TKE permitted by the flow inclination correction was −5.2 % at the lidar level, but could reach −12 % around 1 km altitude, though these values were very sensitive to the altitude band used to optimize the tilt angle. The comparison with a near-ground ultrasonic anemometer in Dunkerque showed that the cross-RHI retrieval overestimated the horizontal TKE by about 13 %, even when accounting for the flow inclination, though this may result from the slightly higher altitude at which lidar data were recorded.
The paper introduces a method for the calculation of wind profiles from RHI scans compares the retrieved wind with wind retrieved from DBS scans and surface-near in-situ measurements. A focus is on turbulence parameters. The authors implement a retrieval for vertical wind profiles of horizontal wind and horizontal TKE. The overall procedure is clearly described. However, I think there is a lack of justification for design decisions at some crucial points. I recommend to either use the methods established in the literature, or indicate clearly why established methods fail or are at a disadvantage for your purpose. DBS has advantages and disadvantages, but is not generally at a disadvantage. Perhaps you can specify the situations/use cases your method is designed for. Please distinguish between the scan patterns and the retrieval techniques. Some retrievals might be specific for a scan pattern. I am not aware about the retrieval methods the manufacturers use for DBS evaluations, but most likely they do not use the retrieval method you assumed for DBS as there are more robust methods that can be generally applied for measurements at the same height (or with height binning). However, they are usually not able to make turbulence estimations. This can justify your method for turbulence estimations. The blind zone can justify using RHI scans if the wind close to the ground is under investigation. In case you consider just wind profiling, established methods (with binning) would also work; in case you also consider TKE, they won't work. When you make comparisons between two methods (or your method and a reference method), please ensure that the application case is clear.
Detailed comments:
line 14, 91, 169: From my point of view it is not clear why DBS is generally more noisy than RHI. If you have a longer accumulation time and fixed beam positions, I assume measurements are less noisy than in continuous RHI measurements.
line 18: Please clearly indicate what the (new) method is doing before you describe what it takes into account.
Section 1: The information you provide about radars might not apply for all types of radars. Please add the type of radar.
There is a general ambiguity in the usage of the "VAD" term in the literature. Sometimes it is related to the scan type, sometimes to the retrieval technique, sometimes combinations. Please ensure the clarity of what is meant when you're using the "VAD" term.
line 87: Why must the Doppler lidars be positioned on a rooftop? Are 75° DBS scans not possible? Is it related to RHI scans from 0°?
Sometimes you use "single-Doppler cross-RHI", sometimes "cross-RHI". Why is it called single-Doppler? Just because it is not dual-Doppler, which is a special application?
Steinheuer et al. (doi:10.5194/amt-15-3243-2022) discuss some more scan patterns for similar application cases.
line 120: Please explain this issue. Why can vertical wind be neglected at 45° elevation angle?
line 180: Is the -27dB threshold recommended for both instrument types? You could validate that with a CNR to radial-wind-speed distribution like carried out by e.g. Zentek et al. 2018 (doi:10.5194/amt-11-5781-2018) in AMT (Fig. 5).
line 188: How do you define good-quality observations?
line 194: A more detailed explanation about the range-fold echoes (e.g. in the caption of S1) would help to follow in the figure. Maybe you can support the understanding by showing the associated CNR or Doppler spectrum width plot if there are significant differences between regular measurements and range-folded measurements. I understand that filtering these echoes is very difficult and sometimes maybe not possible. However, I do not understand how the filter applied addresses the range-folded echoes. You apply a filter removing measurements where not enough valid measurements (according to the CNR?) are in the surroundings. It probably does not work for range-folded echoes at high elevation angles, since the echo will not appear in this "whiskers" and more neighbouring measurements are flagged as valid. Additionally, it does not work, if the range-fold echoes are mapped to areas, where also real measurements are available. In Fig. S1, range fold measurements are only filtered if there was no measurement from the neighbour beams in the surrounding. When highlighting the removal in these areas, you should also discuss the other cases. A further step follows in line 233.
line 205: What does it mean "the contribution of the vertical wind is canceled"? With at least three beams from DBS pointing in different directions, the 3D wind vector can be calculated. What is the DBS retrieval? Is it the proprietary software developed by the manufacturer? Even though the implementation is unknown, I would expect they calculate the 3D wind vector with a least squares fit like many others (e.g. Päschke et al. 2015 doi:10.5194/amt-8-2251-2015). Later, the term "usually" is used. Please clarify, what typical retrieval technique you refer to.
line 209: I do not understand, why a DBS retrieval should produce noisy u and v in case of high w, if not all beams are close to the vertical.
Section 2.3.1: I am wondering why you deviate from the standard least-squares fit wind vector retrieval method using pseudoinverse/svd submatrices. Perhaps, the reason is your space averaging instead of time averaging, which is introduced very shortly in line 220. If that is the reason why you are using another method, this should be indicated more early. Additionally, the advantages and disadvantages compared to the state of the art should be discussed. From my point of view, calculating a 3D wind vector least-squares fit works as well for the layer binning displayed in Fig. 1. Maybe the turbulence estimation have additional requirements. If such requirements exist and are essential for the wind vector calculation, these requirements should be introduced before.
line 234: radial wind speeds from range-fold echoes are in many cases higher than the other observations, but not generally.
line 239: Is it on average really close to 230? In the figure caption you wrote, the maximum is 230.
line 245: Is there a reference for the random errors from scattering particles' movement? I would expect already an averaging effect due to many laser pulses covering differences in the movement. However, moving scatterers are essential for the Doppler lidar measurement principle.
line 247: What was the estimation/result of Eberhard et al. (1989)?
line 248: Do you propose to "correct"/reduce the random error? Why is there a need, when it is stated that -27dB (the threshold you apply as well) ensures a sufficient data quality? Regarding the determination of the threshold, see above.
line 254: Has the DBS wind reconstruction been introduced and you want to refer, or do you want to state that you use the same method for both?
supplement S2.1: Do you have only the horizontal component, i.e. elevation is 0°? From Sect. 2.3.1 (you are referring to) that is not clear. If so, do you calculate the horizontal component from the scan with azimuth in the opposite direction?
line 264: Is full TKE generally not possible without a series of vertical shots for at least one minute or in your specific application case?
line 296: Why does the minimum not work and you need fminbnd? Is the presented curve usually not available and an algorithm has to figure out the minimum?
line 303: What are the consequences? Are these measurements rejected? Are they flagged?
Section 3: Clarify what the DBS reconstruction method is. Usually, three radial velocity measurements in three linearly independent directions are sufficient to retrieve a 3D wind vector (check line 324).
line 326: What could be the reason? Did the DBS scan have more accumulation time for a specific direction?
line 335: Where can we detect the noise?
Fig. 2: Could you also plot the wind speed difference between (a) and (b) to make it easier to detect the differences (e.g. in the supplement).
Section 3.1.2: Could you provide the standard deviation or variance?
Fig. 4: Please add labels for the axes or add the information in the caption. For very low wind speeds (e.g. below 3m/s), high direction differences could occur, even though the differences in the resulting wind vectors are small. I would suggest removing these measurements from the direction comparison.
Section 3.2.1: Describe the objective of the optimization. What range of inclinations would you expect? Generally, you should specify where your messages apply to. For example, one can understand that DBS or VAD retrievals (line 415) cannot be applied in sloping or complex terrain. I would not agree with that in general. Your statement is probably related to the turbulence estimation.
Section 3.2.2: I'm struggling with the wording. I would expect a bias of TKE_h (not inclined), if you see the TKE_h of the inclined version as the (true) reference. The true value lies within your confidence interval with 95% probability, so you can refer to that interval (95% probability for the true value to be between the interval limits, that are very close to 1; e.g. similar to the formulation in line 455) but not due to the 1 is within the interval.
line 458: You compare optimizations for the intervals [0,0.5km], [0,1km], [0,1.5km]. If you have the optimal result (inclination angle) for [0,0.5], I would expect to have worse results when comparing larger intervals. Could it be an option to use non-overlapping intervals?
line 466: Are slice-wise optimizations and different inclinations a possible solution?
line 475: If you have perfect horizontal wind at some height with TKE_RHItilt = TKE_RHI, resulting in 1 for the fraction, the "bias" would be higher than the "bias" minimum detected, even though there would be no bias at the height of the perfect horizontal wind.
Figure 6: To identify the impact of the different inclinations, it is necessary to compare (a), (b), and (c), which have also different x axes. Is it possible to display it in one figure? More generally, it would be possible to see the impact of different inclination angles. Could you indicate the angles used in (a), (b), and (c)?
line 478: Could you describe the temporal and spatial setup you compare for sonic and lidar?
line 496: Are the measurements considered at these low heights all of high CNR or are there possibly noisy measurements close to the -27dB threshold included? If so, does the CNR have an impact on the bias?
Figure 7: How would this comparison look like for TKI_RHI (without tilt)? Is there a significant difference? Maybe you can add this to the supplement.
Summary and conclusions: You are highlighting some points, where it is not clear what is novel (new comparison/evaluation, advanced method) and what are general comments. For example, you write you provide "a more detailed description". Do you just describe another work in more detail, or did you extend/improve/adapt this work. The blind zone of DBS might not be relevant in many application cases. If you defined the scenario you are targeting at, it would be easier to follow the argumentation.
Minor comments:
Please check if you want to use British or American English; you used both (BE would be centre, metre).
Please check your prepositions for locations.
An object should be inserted between "allows" and "to" in "allows to", e.g. "allows the user to".
"m.s-1" should be without the dot in between.
line 9: consider writing "measure wind" instead of "measure wind profiles" as the profiles are not directly measured
line 13: "plus" is informal
line 29: What is the flow inclination angle?
line 45: New sentence beginning with "Middle-income"
line 55: Not all Doppler lidars have a 2 axis scanner
line 60: What is "virtually impossible"?
line 70: How can I imagine gas particle interpretation with Doppler lidars?
line 73: elevation angle
line 86, 170: deep?
line 97: Is this your experience or evidence?
line 101: Too large at higher heights?
Table 1: Consider using "scenario duration" or "iteration duration" instead of "total duration"
line 179: averaged
line 204: singular or plural?
line 221: "too-vertical" is informal
Figure S9f: Is the colourbar label correct (compare to figure S8b)
Supplement line 9: space missing before "denote"
line 272: Maybe you can find a formulation that is easier to understand
line 275: that?
Figure S7: Paros
Figure S7, S9: Why do the subfigures have different resolutions?
line 371: slope of the regression
line 428: presents
line 434: RH or RHI?
line 428: connective??
line 431: If you have a first step, do you have more steps?
line 508: vertical wind profile of the horizontal wind.
line 517: its
line 528: on average