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
First of all, such filtering and interpolation should not be done at L0toL1 level, but rather on the L1toL2 level.
But secondly, when done on (noisy) 6-hourly TX data, this interpolation adds spurious "waves" in the tilt data. And although there is an attempt in L1toL2 to filter noise, the result down the line is different when the input data is from a TX file and a RAW file.
Here is an example at KAN_U in October 2023 for which we have both old transmission and logger data:
We should make sure that at L0toL1, the data is not modified, just made readable.
In L1toL2, we should make sure that the smoothing and interpolation lead to similar values when calculated on 6hr and 1hr data.
We need an assessment of the tilt sensor: is the variations seen in the hourly RAW data true ? or should it be filtered out?
The text was updated successfully, but these errors were encountered:
I kept seeing slightly different radiation values when replacing old transmission files by
raw
logger files and eventually tracked it down.In TX files, tilt is available every 6 hours while in RAW files it's every hour (at least).
In the L0toL1, NaNs in tilt_x and tilt_y are interpolated:
pypromice/src/pypromice/process/L0toL1.py
Lines 304 to 338 in 3813c77
First of all, such filtering and interpolation should not be done at L0toL1 level, but rather on the L1toL2 level.
But secondly, when done on (noisy) 6-hourly TX data, this interpolation adds spurious "waves" in the tilt data. And although there is an attempt in L1toL2 to filter noise, the result down the line is different when the input data is from a TX file and a RAW file.
Here is an example at KAN_U in October 2023 for which we have both old transmission and logger data:
The text was updated successfully, but these errors were encountered: