search

PollyNET / Pollynet_Processing_Chain

NRT lidar data processing program for multiwavelength polarization Raman lidar network (PollyNET)
https://polly.tropos.de/
GNU General Public License v3.0
20 stars 8 forks source link

near range SNR in att bsc files #124

Closed griesche closed 2 years ago

griesche commented 2 years ago

It would be great to save also the near-range SNR in the netCDF att bsc files. So far, only the far-range SNR is stored in these files.

HolgerPollyNet commented 2 years ago

Could this be a job for @ulysses78 ?

ulysses78 commented 2 years ago

I can do that. Should be no problem (I guess). Is this the same SNR-variable which is altready stored in the "normal" att_bsc-files? Only for 355 and 532 nm? Do you also want to store the quality-mask-variable (355+532nm)?

griesche commented 2 years ago

What do you mean by 'normal att_bsc_files'? I also already started on this, but if you're faster you can also do the job :)

Yes, only 355 and 532 nm. I think the quality mask would be good as well.

ulysses78 commented 2 years ago

By 'normal att_bsc_files' I mean the att_bsc files of the far range, where those variables are already implemented.

ZPYin commented 2 years ago

So far, the near-range SNR is calculated inside Picasso, but was not saved in the netCDF file. You can extract the near-range SNR from data.SNR (3D dataset: channel x height x time), and implement the saving within pollySaveNRAttnBeta.m, similar to what was done in pollySaveAttnBeta.m for far-range variables.

griesche commented 2 years ago

I have updated the pollySaveNRAttnBeta.m so that the near-range SNR is also stored. I also started with the quality mask, but this is not yet in the data input to pollySaveNRAttnBeta.m.

I have opened a pull request to the dev branch,

ulysses78 commented 2 years ago

Can this issue be closed?

griesche commented 2 years ago

Yes I think so.