Klett_BSC_NR not stored in done file list

[HolgerPollyNet]

I realized that the information for the Klett bsc near range is not reported in the done filelist and thus not stored to the data base.

[ZPYin]

This has been fixed.

Bug Analysis

The figure name of Klett bsc near range plot was wrong when making done_filelist, see the code below: https://github.com/PollyNET/Pollynet_Processing_Chain/blob/82bc73fea5b2eb5ffad9145b48ef574cfa25b890/lib/io/pollyWriteDonelist.m#L228-L229

thus, the figure was filtered out in writing the done_filelist.

[HolgerPollyNet]

Hi @ZPYin, I and @martin-rdz realized, that no near-range Klett backscatter is calculated at all. See for example all the recent plots at the website. Only far-range bsc is plotted. Do you have any explanation why?

[ZPYin]

Regarding the near-range products, I do see both the netCDF4 files and plots in the server. Below is a sample:

images

netCDF4 files

In addition, the plots information has been saved in the polly DB successfully as well.

So, the only explanation why they are missing at the website is that they are just not showing!!! To my perspective, this is something out of Pollynet Processing Chain. Please transfer this issue to Rico (@rico-hengst ).

[HolgerPollyNet]

The problem is not, that it is not shown on the website, the problem is that the products are not calculated. I.e., the netcdf and images are there, bot no NR Klett product inside. So it is for sure a problem of the Processing Chain as it holds for all Pollys.

Arbitrary example of today:

While for raman there are NR products:

Any idea where to look at?

[martin-rdz]

Somehow aerBsc_klett_NR_532 only contains masked values.

Example 2019_08_15_Thu_LACROS_06_00_01_0700_0759_NR_profil es.nc

:version = "3.1" ;
:history = "Last processing time at 2021-11-02 14:21:41 by pollySaveNRProfiles, 
git branch: master, git commit: 0b3e3a467de0f1f72fd979f89f7ab1a6cbe898c0" ;
data:

 aerBsc_klett_NR_532 = _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,

Similarly for data in August 2020 (2020_08_31_Mon_LACROS_12_00_01_1641_1759_NR_profil es.nc), where the overlap should have been even better.

:version = "3.1" ;
:history = "Last processing time at 2021-11-06 06:45:01 by pollySaveNRProfiles, 
git branch: master, git commit: 8b4e8286d58208a0b1c820b33c234a448792ca08" ;
data:

 aerBsc_klett_NR_532 = _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,
    _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _, _,

For both instances FR and OC contains reasonable data.

[ZPYin]

Thanks for the detailed information.

This was caused by some (stupid) coding bugs. (see below) https://github.com/PollyNET/Pollynet_Processing_Chain/blob/8b4e8286d58208a0b1c820b33c234a448792ca08/lib/interface/picassoProcV3.m#L1232-L1235 https://github.com/PollyNET/Pollynet_Processing_Chain/blob/8b4e8286d58208a0b1c820b33c234a448792ca08/lib/interface/picassoProcV3.m#L1284-L1287

The near-field results were not transferred to the right variables...

I have fixed it in the latest fixes and updated the version to 3.2 to identify the changes. Below is the new near-field plots:

Sorry for the inconvenience.

[HolgerPollyNet]

@ZPYin many thanks for the fast fixing and no worries about the bug - bug fixing is one of the major task while coding ;-)