Closed griesche closed 8 months ago
Yes we can definitely store this if and when it comes available.
Great! We plan to calculate the pixel-level uncertainties (random and bias) in attenuated backscatter coefficient (and depolarisation ratio) for each lidar/ceilometer in the next operational version - at the moment, these are just scalar values. Obviously, we would need at least SNR to do this, or be able to generate pseudo-SNR for ceilometers.
What other information do we need for the PollyXT systems? Deadcount corrections? Or would you prefer to calculate these uncertainties yourselves and include these in the calibrated files?
The pollynet processing chain now stores also the near-range data in its files. It would be good if the backscatter, SNR, and depolarization of the available wavelengths would be saved in the calibrated files. Together with the respective calibration factors.
Not sure about the deadtime correction. I think it is usually applied in the pollynet processing.
Thanks for the info! We will take a look at this.
Do you know if the near-range data is currently submitted to Cloudnet and how is it stored in the files?
Please re-open this if becomes relevant again.
Hi, it would be great to store also the SNR data from the PollyXT near-range channel in the calibrated files. In the Matlab Version of Cloudnet, this was already implemented.
Yet, so far the near-range SNR is not stored in the PollyNet-Processing-chain files (which are the files cloudnetpy uses as an input to convert the Polly data). However, I have already initiated the storage of the near-range SNR in the PollyNet-Processing-chain.