automatically run july campaign september 2022 & July 2023

• in short: N2O needs to be gathered from Aeris storage (instead datalogger)

• problem for july campaign: first part (9 July- 17 July) of the N2O data must be read in from original Aeris data (like in the 2022 script: sort_n2o_conc_by_meas_period.R) rather than the data logger data:

• for comparison, the 2023 script (sort_n2o_conc_by_meas_period_2023.R) takes the data from data logger:

• possible solution: add IF function to 2023 script so it reads the correct data for the first part of campaign. Unsure how to do that.

assigned to @jengel

I'll have a look at it and then we can discuss how to do this in a meeting.

I think this issue is solved. Closing it now. Please re-open if I missed something.

closed

reopened

Sorry, I don't think it's closed. I just work on the data from the end of July but I actually have more :)

created branch feature/automatically-run-july-2023-campaign to address this issue

mentioned in merge request !11

changed title from automatically run july campaign to automatically run july campaign 2023 + september 2022

changed the description

changed title from automatically run july campaign 2023 + september 2022 to automatically run july campaign september 2022 & July 2023

Current status: working on implementing 202209 and 202307 July campaign. Comments:

• it's getting a bit complicated to treat single measurement campaigns individually but field is field and problems arise, so:
• create "new" measCamp 202306. In this measCamp, we can import data as in 202209, with N2O (and CO2) coming from the Aeris rather than the data logger
• rename all functions for 202209 and 202306 with _aeris_ds ending. ds = direct source
• modify create_input_for_goflux_package_n2o.R: because variables then have different names (e.g., n2oppm & n2oppm_aeris_ds), we need another ifelse function in:

line 33: add if mp == 202209 | 202306, then
ppN2OdataDF$n2oppb <- ppN2OdataDF$n2oppm_aeris_ds * 1000

line 79/80: add if mp == 202209 | 202306, then 
goflux_input_n2o_df <- mPN2oPlotHabitat %>%
   select(n2oppb, h2oppm_aeris_ds, meas_ID, time_since_mp_start, datetime_datalogger, V, collar_area_cm, collar_height_cm, airpreskPa, chamberTdegC, flag)

• do the same for CO2
• test with the final and clean field-data-sheet inputs

Filters needed for N2O and CO2 correction when mcDataSource = aeris_ds = measCamp 202209 and 202306:

measCamp 202209

• N2O: filter functions 01, 02, 04, 07-12
• CO2: filter function 01, 02, 08 - 12
• CO2: ADD filter function 07 (min/max values)

measCamp 202306

• N2O: all filter functions

• CO2: all filter functions

• note: for CH4, no distinction is needed

• docu: 202209 was a diff measuremtn device than 202306
  • 202209 no flatlines
  • 202306 with flatlines in data

• "note: for CH4, no distinction is needed"
• what would that refer to, i.e., distinction between or compared to what?

• for CH4, there is no difference between the filters functions needed for the different measCamps.
• why? CH4 concentrations were always gathered by the Licor LI-7810 so there were no flat lines
• concentrations are always "the same" in all measCamps

• issue: measCamps do not run all together
• when 202209 is added to the list, the following error is shown:

• issue: 202209 campaign does not work for ch4:

• issue: current update gives following error when running 202209/202306 campagins

• this is because of l138 in main_data_processing:
• once this is uncommented, it works again