GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

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.

Edited Jan 13, 2025 by Nathalie Triches

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information