PollyNET
Signal cutoff to improve retrieval for Raman method
The signal data in the first bins behaves unusual / non physical. This affects smoothing and differentiation for the Raman retrieval methods. So the first 10 bins are set equal to the value at the 10th bin. This is done for 532 and 1064nm. For 355nm this might be beneficial as well.
Hi @yZenox , your "patch" has severe implication for all lidars. Also I think the statement that the first 10 bins are unphysical is not valid. THus, we need to disucss about it. Currently I would not like to merge it in dev.
@ulysses78 @martin-rdz What do you think? I guess we cannot do it in such a hard coded way, right? Maybe to use the config file instead? E.g. starting with range bin 262 and then allocating height 41.25 m to it?
Yes, those cutoffs definitly have to be added to the config file for the single polly-device, not in the python file itself.
