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

Add option to use latest GDAS profile instead of standard atmopshere #110

Closed HolgerPollyNet closed 2 years ago

HolgerPollyNet commented 2 years ago

It would be nice, to add the option that the latest available GDAS profile for a site is used in the NRT processing instead of standard atmosphere.

This option should not prevent the reprocessing during the night once GDAS profiles for the time of the measurement are available.

ZPYin commented 2 years ago

There is a keyword meteorDataSource to configure the meteorological data source for Picasso (see below). https://github.com/PollyNET/Pollynet_Processing_Chain/blob/456285034326bcf8f7f4002a1c4fcb864d08b009/config/pollyConfigs/polly_global_config.json#L83

So far, there are four options for meteorological data source:

If I remember correctly, the latest GDAS profiles have a latency of 1 day (at least). Therefore, Picasso will turn to standard atmosphere during NRT processing, since no GDAS profiles can be found in the server.

HolgerPollyNet commented 2 years ago

@ZPYin thanks for explaining the current procedure, however, this issue was intent to add one more option, namely the use of the latest available GDAS profile instead of using standard atmosphere for preliminary processing.

ZPYin commented 2 years ago

@ZPYin thanks for explaining the current procedure, however, this issue was intent to add one more option, namely the use of the latest available GDAS profile instead of using standard atmosphere for preliminary processing.

OK, it can be implemented. But it's time consuming to search the exact latest available GDAS, since you need to iterate the entire GDAS file tree. As an alternative, I decided to search the past 2-month for the "latest" profile. You can find the implementation in the commit id above this post.