Holger Baars

The same like usual, one plot for each file or all files in one plot, but differently processed 😉

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...

@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...

Thanks for notifying, @georgmueller @yZenox Issue 1 would be correctly fixed with: data.height = double((0:(size(data.signal, 2)-1)) * data.hRes * cos(data.zenithAng / 180 * pi) + config.firstBinHeight* cos(data.zenithAng / 180 *...

For your second point, could you refer to the exact lines in the code to know where and for what it is used?

I have to say, that I prefer short names, i.e. t instead of total, c for cross etc. but I can survive with everything ;-). What about the DFOV depol...

> Does anyone know, if it affects the processing chain, if we just change the channel labels within the polly-config files? Is this related to this topic or a general...

> It is related to this topic. Then only @ZPYin can easily reply to this.

Dear @mtsichla , according to  you glue on the averaged signals, correct? Then the correct position for including it in the chain would be here: https://github.com/PollyNET/Pollynet_Processing_Chain/blob/e85bef047e7cd642a52ab25d1288fd07bd924076/lib/qc/pollyOLCor.m#L154 Could you define...

Hi @mtsichla , can you provide a little bit more detail of the variables and constants. E.g. type (array, which dimensions, etc.) and what values are possible. E.g. for telescope...