You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, qi_total is initialized with "0". If no additional quality control is applied, this prevents e.g. NWP from using the corresponding quantity. Hence, qi_total needs to be initialized with "1".
The text was updated successfully, but these errors were encountered:
if nr_qitotal_fields > 0:
if hasattr(qitotal, QITOTAL_METHOD):
method = getattr(qitotal, QITOTAL_METHOD)
result = method(qitotalfields)
scan.addOrReplaceQualityField(result)
Now ALL NIMBUS QC-PVOL files contain qi-total quality field. Even the radar data from sources which are only treated with "distance,scansun,qi-total".
Note that "distance,scansun" filters do leave traces (quality fields) in the HDF data so qi-total filter does not see them and the BALTRAD BUG was not creating even an empty qi-total quality field.
This is now SOLVED.
Testing details below.
Testing node=plgda; QC-FILTERS based on modules_by_radar.xml: <plgda modules="distance,scansun,qi-total"></plgda>
Quality-fields: node=plgda; scan_qc_list=[] before computing qi-total.
Testing node=nosta; QC-FILTERS based on modules_by_radar.xml: <nosta modules="distance,scansun,qi-total"></nosta>
Quality-fields: node=nosta; scan_qc_list=['no.met.prorad.qi_total', 'no.met.prorad.beamblockage'] before computing qi-total.
Testing node=nldhl; QC-FILTERS based on modules_by_radar.xml: <default modules="distance,scansun,hac-increment,ropo,beamb,satfilter,hac-filter, qi-total"></default>
Quality-fields: node=nldhl; scan_qc_list=['fi.fmi.ropo.detector.classification', 'se.smhi.detector.beamblockage', 'fr.mf.satfilter'] before computing qi-total.
Currently, qi_total is initialized with "0". If no additional quality control is applied, this prevents e.g. NWP from using the corresponding quantity. Hence, qi_total needs to be initialized with "1".
The text was updated successfully, but these errors were encountered: