Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEROS QA/QC steps suggestions for L2 #52

Open
3 tasks
robertapeixoto opened this issue Nov 9, 2023 · 1 comment
Open
3 tasks

TEROS QA/QC steps suggestions for L2 #52

robertapeixoto opened this issue Nov 9, 2023 · 1 comment

Comments

@robertapeixoto
Copy link

robertapeixoto commented Nov 9, 2023

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.

@bpbond bpbond changed the title TEROS QA/QC steps suggestions for L1 TEROS QA/QC steps suggestions for L2 Apr 2, 2024
@bpbond
Copy link
Member

bpbond commented Apr 2, 2024

I have changed the issue title to refect that these are L2 items, not L1 (except perhaps the first). Thanks again @robertapeixoto !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants