Currently, data is stored with the following convention: f'./data/{nodeid}_bme688.csv' (i.e., for the BME, without loss of generality).
Suppose computer A uses node 1234; later that day, computer B uses node 1234. Suppose neither computer has access to the internet during this time. When the computers are reconnected to the internet, they push these files. They will hit a merge conflict between the two files, an unnecessary issue.
Moreover, suppose someone wants to (1) parse all the data for a given test day or (2) parse all the data from a specific transmitting SNode. This is currently difficult to find and parse.
Currently, data is stored with the following convention:
f'./data/{nodeid}_bme688.csv'(i.e., for the BME, without loss of generality).Suppose computer A uses node 1234; later that day, computer B uses node 1234. Suppose neither computer has access to the internet during this time. When the computers are reconnected to the internet, they push these files. They will hit a merge conflict between the two files, an unnecessary issue.
Moreover, suppose someone wants to (1) parse all the data for a given test day or (2) parse all the data from a specific transmitting SNode. This is currently difficult to find and parse.