*3.3. Measured Data*

In the end of the data-collection phase, 500 event structures were recorded. Each event instance has 15 s worth of data saved into files: 15 JPG files containing the captured images and one text file containing the rest of the measured data. The text file is structured so every second of the event is one line (separated by a newline character "\n"), and the measured quantities are separated by commas. Table 3 shows an example of the numeric data measured during one event.

**Figure 4.** Flowchart of decision process and data flow within DAS software.

The first column contains the time stamps from each measurement point in the event. Each component is separated by an underscore, following the "hh\_mm\_ss\_YYYY\_MM\_DD" format. The last component is a Boolean value, indicating whether daylight savings time is in effect. This is in local time and is used to determine the solar position angles.

Next are temperature measurements taken once per event, if, as with this example, there is more than one value in one event, it is because events were detected close to one another and some of the time stamps intersect. The negative values were used to represent "no data", and those were replaced by linear interpolations for the data-modeling phase. The last three values are the measured voltage, current and power, respectively. One such file was generated per detected event. As for the captured images, Figure 5 shows two examples of raw images, one from the beginning of the event and the second from the end.


**Table 3.** Example of numeric data pertaining to one event structure.

(**a**) (**b**)

**Figure 5.** Raw image examples from the beginning of an event (**a**) and from the end (**b**).
