Multiple serial numbers: flexibility versus fragility #19
Comments
|
P.S. It took me a while to track down Roberta's GitHub username. @stephpenn1 @hetland could one of you add her to the COMPASS-DOE organization please? 🙏 |
|
Oh and @wilsonsj100 isn't a member either :) thanks! |
|
[like] Wilson, Stephanie reacted to your message:
…________________________________
From: Ben Bond-Lamberty ***@***.***>
Sent: Monday, February 12, 2024 5:43:33 PM
To: COMPASS-DOE/whattheflux ***@***.***>
Cc: Wilson, Stephanie ***@***.***>; Mention ***@***.***>
Subject: [COMPASS-DOE/whattheflux] Multiple serial numbers: flexibility versus fragility (Issue #19)
External Email - Exercise Caution
@robertapeixoto<https://github.com/robertapeixoto> raised an interesting point:
If you have multiple IRGAs going and are entering their metadata into a single file, we will need to enforce a "serial_number" column (or something like that) so that we correctly match the data files with associated metadata.
Of course, this increases the possibility of user error and makes things more fragile, potentially.
@wilsonsj100<https://github.com/wilsonsj100> Maybe we can discuss this decision decision when we meet next, and consult further if needed with Roberta and/or Genevieve about how they work.
—
Reply to this email directly, view it on GitHub<#19>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5E7566ILHZXJGKNZ7FFVZTYTJIELAVCNFSM6AAAAABDFEHFXSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEZTANRTHA2DEMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
I think that the multiple machine issue is sort of a unique problem. I know at SERC, the only time we are using multiple Licors for the exact same type of fluxes (i.e. two people measuring chamber fluxes at the same time) is during tempest. Even then I think we usually have one dedicated to soils and one dedicated to soils (maybe I am incorrect about this?). When Genevieve is doing fluxes at SMARTX or GENX they also are only using one instrument, so it might be a situation where you just need to run the code twice if you have two instruments - one per. |
|
We used four instruments in the first TEMPEST, the same ones for soil fluxes and each treatment throughout the entire week. At LE, we have six equipment files, as we used yours before ours arrived. I preferred running the code six times to manage excessive graphs and errors with the start time, but with the correct start time, a single run suffices. If kept as is, I would add a line in the README, specifying a one-time run for each machine. An alternative perspective is that using a single metadata to run everything at once is more susceptible to filling issues but simplifies the creation of a unified file for plotting all fluxes and statistics (compartments: MAC, SOIL, STEM). |
Both have been invited, @wilsonsj100 @robertapeixoto please check the email you use for github and accept |
|
Thank you @stephpenn1 |
@robertapeixoto raised an interesting point:
If you have multiple IRGAs going and are entering their metadata into a single file, we will need to enforce a "serial_number" column (or something like that) so that we correctly match the data files with associated metadata.
Of course, this increases the possibility of user error and makes things more fragile, potentially.
@wilsonsj100 Maybe we can discuss this decision decision when we meet next, and consult further if needed with Roberta and/or Genevieve about how they work.
The text was updated successfully, but these errors were encountered: