21 | | '''Important''': the log data index can be generated without any knowledge of the meaning of each log entry type. The index is keyed by the integer log entry type IDs contained in the log data itself. The log data index and log data always correspond 1:1 - once generated, the log data index can be saved alongside the log data and re-used as needed. Refer to the {{{log_data_to_hdf5}}} utility for an example implementation. |
| 21 | '''Important''': the log data index can be generated without any knowledge of the meaning of each log entry type. The index is keyed by the integer log entry type IDs contained in the log data itself. The log data index and log data always correspond 1:1 - once generated, the log data index can be saved alongside the log data and re-used as needed. |
| 22 | |
| 23 | Refer to the {{{log_data_to_hdf5}}} utility for an example use of the implementation. |
| 24 | |
| 25 | == Log File Writing & Reading == |
| 26 | The wlan_exp_log framework uses the HDF5 file format to store raw log data and indexes. |
| 27 | |
| 28 | The {{{log_data_to_hdf5}}} method will store log data in a new or existing HDF5 file. It will also generate and store the corresponding log data index. |
| 29 | |
| 30 | The {{{hdf5_to_log_data}}} method will retrieve log data from an HDF5 file created by {{{log_data_to_hdf5}}}. {{{hdf5_to_log_data_index}}} will retrieve the corresponding log data index. |
| 31 | |
| 32 | Refer to the {{{warpnet_example_wlan_log_read.py}}} script for an example of retrieving log data from a node and writing it to an HDF5 file. |
| 33 | |
| 34 | Refer to the {{{warpnet_example_wlan_log_parse.py}}} script for an example of reading log data and its index from an HDF5 file. |