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

SWH_UP (now Swamp) sap flow deep sensor install issue #281

Closed
aestearns01 opened this issue Mar 23, 2025 · 11 comments · Fixed by #296
Closed

SWH_UP (now Swamp) sap flow deep sensor install issue #281

aestearns01 opened this issue Mar 23, 2025 · 11 comments · Fixed by #296
Assignees
Milestone

Comments

@aestearns01
Copy link

@bpbond @stephpenn1 @roylrich I noticed during intensive site checks on 18 Mar 25 that the SWH_UP (now swamp) SF 2 deep sensor was installed incorrectly with the heated probe on the bottom. Not sure how this will affect the data. SF 2 shallow 3.5 cm sensor was installed correctly.

Additionally, how have we addressed the UP to Swamp naming convention in the L1 data set since in loggernet it is technically still UP? For monitoring, I still use "UP" to reflect the loggernet designations. Reminder that we don't have SF sensors in the current Upland (previously Upland Control).

@bpbond
Copy link
Member

bpbond commented Mar 24, 2025

Hi @aestearns01

Oh, that's a thing. Presumably then the reference probe is seeing heated sap? Ugh.

Re your question, we use a 'design table' to map loggernet variables to L1 outputs, so we can simply assign different mappings:

Image

Here the first block (WaterLevel600A) is mapped to SWAMP, while WaterLevel600B is assigned to UP.

@aestearns01
Copy link
Author

@bpbond yes, the ref probe is logging heated sap

Thanks for showing me how it looks!

@stephpenn1
Copy link
Member

Interestingly sensor 02D looks pretty good compared to the other deep sensors

Image

@aestearns01
Copy link
Author

aestearns01 commented Mar 25, 2025

@stephpenn1 interesting. I suppose that's why I never caught it doing loggernet checks. I would have expected the daily flux to be opposite/inverse, no??

@bpbond
Copy link
Member

bpbond commented Mar 26, 2025

That is interesting! Thanks @stephpenn1

@aestearns01 No, I don't think it would be inverted or anything. The unheated probe is serving as a reference, so if it's slightly warmer than it should be (because it's above, not below, the heated one) all that would happen is that the computed sap flow would be a bit lower than the true value.

@stephpenn1
Copy link
Member

@aestearns01, if you're planning to re-install in the same tree, we could compare the two data sets. I'm curious how much dampening is happening

@bpbond
Copy link
Member

bpbond commented Apr 8, 2025

@stephpenn1

What about if we add a note to the SWH site metadata file, noting this problem but also that visual inspection of the data shows that it's performing like the others?

@bpbond
Copy link
Member

bpbond commented Apr 9, 2025

Please look at https://github.com/COMPASS-DOE/sensor-data-pipeline/pull/296/files -- does this suffice?

@stephpenn1
Copy link
Member

Yes that's good for now

@bpbond bpbond closed this as completed Apr 9, 2025
@bpbond bpbond added this to the L1 v2-0 milestone Apr 9, 2025
@aestearns01
Copy link
Author

aestearns01 commented Apr 11, 2025

@bpbond it's the 02D (deep 5.0 cm sensor) that is installed incorrectly. The metadata note you created says the 02 sensor (regular 3.5 cm)
@stephpenn1 not planning to re-install any deep sensors

@bpbond
Copy link
Member

bpbond commented Apr 11, 2025

Ahhhhh! Thank you @aestearns01 -- much appreciated-- fixed in b3649a9

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

Successfully merging a pull request may close this issue.

3 participants