Holger Baars
Holger Baars
For 3.0, one could also think of one dedicated module producing EARLINET nectdf in ADDITION to pur Picasso netcdf.
Concerning my previous comment, the EARLINET netcdf product should be a product for lidar dummies ;-) (let's say, user who just use the profile without the need to know anything...
Thanks you Moritz for your ideas. 1) In general I agree, all information which is read from the config file should be transferred to the output netcdf. I also think...
@Moritz-TROPOS Concerning your first comment, please also have in mind that we have also the follwoing issue: https://github.com/PollyNET/Pollynet_Processing_Chain/issues/79 Given your experience you could also start working on that! We welcome...
From Patric: 1) The Picasso output files (att_bsc, vol_depol) do not contain any information about zenith angle. Would be good to have it included. It would also be required in...
use far range values as reference to near-range profiles
already implemented
@griesche was there work on this?
IS this still an issue? @Moritz-TROPOS @gast-ben
After thinking about, I do not know if this is really needed. --> but maybe for higher versions