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

Bad vwc sensor 4 at PTR-W? #210

Open
bpbond opened this issue Sep 7, 2024 · 5 comments
Open

Bad vwc sensor 4 at PTR-W? #210

bpbond opened this issue Sep 7, 2024 · 5 comments

Comments

@bpbond
Copy link
Member

bpbond commented Sep 7, 2024

@robertapeixoto notes that PTR soil moisture data look a little funky in the wetland:

image

What's up with sensor 4?

@robertapeixoto
Copy link

I suspect that the issues with sensor 4 are the same as those on the dashboard. We don't have sensors 3 and 4 in the wetland, but somehow the datalogger is saving data that appears as continuously incorrect values. I will tag @stephpenn1 here because I believe the easiest way to avoid this problem in L1, the dashboard, and the COMPASS driver is to remove WET sensors 3 and 4 from the datalogger input. Can you adjust the code to prevent it from saving these values? However, what is bothering me is the very negative value in the transition (below -0.4). This should be filtered out in L1 because it is outside the sensor range, but I can't see why it is still appearing here.

@bpbond
Copy link
Member Author

bpbond commented Sep 10, 2024

Ah, okay, thank you! So there are two issues

  • We need to remove the sensor 4 in the wetland — it's not real. This is a quick edit to the design table.
  • Why aren't the bad values being removed? First we will check the bounds/units table, then the code.

@stephpenn1
Copy link
Member

Note this is related to #200

I agree with your summary Ben, and we should check what is different about these two sensors vs the other open ports in the other synoptic sites since these show up in the raw data and L1.

@bpbond
Copy link
Member Author

bpbond commented Sep 12, 2024

@robertapeixoto FYI @stephpenn1 and I are both a little jammed up at the moment but will look at this in early October if that's OK.

@robertapeixoto
Copy link

That sounds great to me! Let me know if I can help. =) I had the same out-of-sensor range values issue with ClimaVue data for temperature. So let me know when you get back to this. I might save other graphs here so you know which ones to check in L1 in October. Thanks.

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

3 participants