JSegrave-IBM

Note: in order to work out the tech (algos / ML) behind the alerts, we're going to need to do some of the storyboarding described in [Issue 89](https://github.com/Code-and-Response/Prometeo/issues/89) e.g. (illustrative...

@lidderupk @mrodrise - table definitions for the sensor log and analytics output... **Key points:** * There are two tables: * `firefighter_sensor_log` where each row is the raw/unmodified sensor readings associated...

Thanks @mrodrise - table name is now 'firefighter_status_analytics' - is that OK? (mix of calculated values and 'cleaned' sensor values - e.g. dropout-refilled, minute-aligned ). Also added 'device_id' and 'device_battery_level'...

> ```sql > CREATE DATABASE IF NOT EXISTS prometeo character set UTF8mb4 collate utf8mb4_unicode_ci; > ``` Thanks @krook - I presume all the CREATE TABLE statements should have DEFAULT CHARSET=UTF8mb4;...

**Changes:** (FYI - @mrodrise @lidderupk ) * There are two tables: * `firefighter_sensor_log` where each row is the raw/unmodified sensor readings associated with `firefighter_id` during the minute `timestamp_mins` - we...

Normally the `device_status_LED` and `analytics_status_LED` (i.e. the LED colors) will be the same, but in a disconnected scenario, they may be different. We'll capture both. Hence these two updates above:...

Pull request: https://github.com/Code-and-Response/Prometeo-Database/pull/3

Modified DB field names to make them less sensitive to configuration changes. Fields for the different time-window TWAs are now named the after the number of minutes in that window...

Here's the plan (summarising today's call): 1. We’ll get `maxed out` handling in for the October test burns. When the firmware detects PPMs above 95% of the sensor max specification,...

The analytics side of this is ready for review/merging. Based on the sensors sending a signal value of '-1' to indicate when they've exceeded their range.... This change makes sure...