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
Roberta -> These are the steps I'm currently looking for in the TEROS manual QA/QC process. They can help create an automated pipeline for simple flag L1.
Identifying SWC values below 0.1. They can suggest problems in the sensor or sensors out of the soil.
Identifying outliers based on the mean absolute deviation. These don't necessarily need to be filtered out at L2 (e.g. CB sites with high EC!), but they should be flagged for closer examination, especially LE.
Issues reported by the technicians during their weekly checks. I've come across instances of 'low connectivity' and a month of missing data. Typically, there's no recorded data or no apparent problems. We might want to consider establishing another system or metadata to link these notes to the automated data processing pipeline. Maybe a power or connectivity check can anticipate problems here.
The text was updated successfully, but these errors were encountered:
bpbond
changed the title
TEROS QA/QC steps suggestions for L1
TEROS QA/QC steps suggestions for L2
Apr 2, 2024
Roberta -> These are the steps I'm currently looking for in the TEROS manual QA/QC process. They can help create an automated pipeline for simple flag L1.
Identifying SWC values below 0.1. They can suggest problems in the sensor or sensors out of the soil.
Identifying outliers based on the mean absolute deviation. These don't necessarily need to be filtered out at L2 (e.g. CB sites with high EC!), but they should be flagged for closer examination, especially LE.
Issues reported by the technicians during their weekly checks. I've come across instances of 'low connectivity' and a month of missing data. Typically, there's no recorded data or no apparent problems. We might want to consider establishing another system or metadata to link these notes to the automated data processing pipeline. Maybe a power or connectivity check can anticipate problems here.
The text was updated successfully, but these errors were encountered: