junos
/
rapids
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix periodic segments bug when there are no segments to assign

pull/130/head
JulioV 2021-04-06 20:29:30 -04:00
parent e043dd8815
commit 9551669d47
2 changed files with 33 additions and 54 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/setup/configuration.md
View File

@ -354,7 +354,7 @@ TIMEZONE:
### Multiple timezones ### Multiple timezones
If your participants lived on different time zones or they travelled across time zones, and you know when participants' devices were in a specific time zone, RAPIDS can use this data to process your data streams with the correct date-time. You need to provide RAPIDS with the time zone data in a CSV file (`[TZCODES_FILE]`) in the format described below. If your participants lived in different time zones or they traveled across time zones, and you know when participants' devices were in a specific time zone, RAPIDS can use this data to process your data streams with the correct date-time. You need to provide RAPIDS with the time zone data in a CSV file (`[TZCODES_FILE]`) in the format described below.
``` yaml ``` yaml
TIMEZONE: TIMEZONE:
@ -376,7 +376,7 @@ Parameters for `[TIMEZONE]`
|--|--| |--|--|
|`[TYPE]`| Either `SINGLE` or `MULTIPLE` as explained above | |`[TYPE]`| Either `SINGLE` or `MULTIPLE` as explained above |
|`[SINGLE][TZCODE]`| The time zone code from this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) to be used across all devices | |`[SINGLE][TZCODE]`| The time zone code from this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) to be used across all devices |
|`[MULTIPLE][TZCODES_FILE]`| A CSV file containing the time and code from this [list](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones) visited by each device in the study. Multiple devices can be linked to the same person, read more in [Participants Files](#participant-files) | |`[MULTIPLE][TZCODES_FILE]`| A CSV file containing the time zones in which participants' devices sensed data (see the required format below). Multiple devices can be linked to the same person, read more in [Participants Files](#participant-files) |
|`[MULTIPLE][IF_MISSING_TZCODE]`| When a device is missing from `[TZCODES_FILE]` Set this flag to `STOP` to stop RAPIDS execution and show an error, or to `USE_DEFAULT` to assign the time zone specified in `[DEFAULT_TZCODE]` to any such devices | |`[MULTIPLE][IF_MISSING_TZCODE]`| When a device is missing from `[TZCODES_FILE]` Set this flag to `STOP` to stop RAPIDS execution and show an error, or to `USE_DEFAULT` to assign the time zone specified in `[DEFAULT_TZCODE]` to any such devices |
|`[MULTIPLE][FITBIT][ALLOW_MULTIPLE_TZ_PER_DEVICE]`| You only need to care about this flag if one or more Fitbit devices sensed data in one or more time zones, and you want RAPIDS to take into account this in its feature computation. Read more in "How does RAPIDS handle Fitbit devices?" below. | |`[MULTIPLE][FITBIT][ALLOW_MULTIPLE_TZ_PER_DEVICE]`| You only need to care about this flag if one or more Fitbit devices sensed data in one or more time zones, and you want RAPIDS to take into account this in its feature computation. Read more in "How does RAPIDS handle Fitbit devices?" below. |
|`[MULTIPLE][FITBIT][INFER_FROM_SMARTPHONE_TZ]`| You only need to care about this flag if one or more Fitbit devices sensed data in one or more time zones, and you want RAPIDS to take into account this in its feature computation. Read more in "How does RAPIDS handle Fitbit devices?" below. | |`[MULTIPLE][FITBIT][INFER_FROM_SMARTPHONE_TZ]`| You only need to care about this flag if one or more Fitbit devices sensed data in one or more time zones, and you want RAPIDS to take into account this in its feature computation. Read more in "How does RAPIDS handle Fitbit devices?" below. |
@ -412,7 +412,7 @@ Parameters for `[TIMEZONE]`
- A screen row sensed at `1587400000000` will be discarded because it was logged outside any interval. - A screen row sensed at `1587400000000` will be discarded because it was logged outside any interval.
??? note "Can I get the `TZCODES_FILE` from the time zone table collected automatically by the AWARE app?" ??? note "Can I get the `TZCODES_FILE` from the time zone table collected automatically by the AWARE app?"
Sure. You can put your timezone table (`timezone.csv`) collected by AWARE app under `data/external` folder and run: Sure. You can put your timezone table (`timezone.csv`) collected by the AWARE app under `data/external` folder and run:
```bash ```bash
python tools/create_multi_timezones_file.py python tools/create_multi_timezones_file.py
``` ```

71
src/data/datetime/assign_to_periodic_segments.R
View File

@ -1,32 +1,18 @@
day_type_delay <- function(time_segments, day_type, include_past_periodic_segments){ get_existent_dates <- function(data, time_segments, include_past_periodic_segments){
# Return a delay in days to consider or not the first row of data max_delay = max(time_segments$length_duration)
delay <- time_segments %>% max_delay <- (if_else(is.na(max_delay) | include_past_periodic_segments == FALSE, duration("0days"), max_delay))
mutate(length_duration = duration(length)) %>%
filter(repeats_on == day_type) %>% arrange(-length_duration) %>%
pull(length_duration) %>%
first()
return(if_else(is.na(delay) | include_past_periodic_segments == FALSE, duration("0days"), delay))
}
get_segment_dates <- function(data, local_timezone, day_type, delay){ existent_dates <- data %>%
# Based on the data we are processing we extract unique dates to build segments distinct(local_date, .keep_all = FALSE) %>%
dates <- data %>% mutate(local_date_obj = date(lubridate::ymd(local_date))) %>%
distinct(local_date) %>% complete(local_date_obj = seq(date(min(local_date_obj) - max_delay), date(max(local_date_obj)), by="days")) %>%
mutate(local_date_obj = date(lubridate::ymd(local_date, tz = local_timezone))) %>% mutate(local_date = replace_na(as.character(date(local_date_obj))),
complete(local_date_obj = seq(date(min(local_date_obj) - delay), date(max(local_date_obj) + delay), by="days")) %>% every_day = 0,
mutate(local_date = replace_na(as.character(date(local_date_obj)))) wday = wday(local_date_obj, week_start = 1),
mday = mday(local_date_obj),
if(day_type == "every_day") qday = qday(local_date_obj),
dates <- dates %>% mutate(every_day = 0) yday = yday(local_date_obj)) %>%
else if (day_type == "wday") select(-local_date_obj)
dates <- dates %>% mutate(wday = wday(local_date_obj, week_start = 1))
else if (day_type == "mday")
dates <- dates %>% mutate(mday = mday(local_date_obj))
else if (day_type == "qday")
dates <- dates %>% mutate(qday = qday(local_date_obj))
else if (day_type == "yday")
dates <- dates %>% mutate(yday = yday(local_date_obj))
return(dates)
} }
infer_existent_periodic_segments <- function(existent_dates, segments){ infer_existent_periodic_segments <- function(existent_dates, segments){
@ -36,7 +22,8 @@ infer_existent_periodic_segments <- function(existent_dates, segments){
pivot_longer(cols = c(every_day,wday, mday, qday, yday), names_to = "day_type", values_to = "day_value") %>% pivot_longer(cols = c(every_day,wday, mday, qday, yday), names_to = "day_type", values_to = "day_value") %>%
filter(repeats_on == day_type & repeats_value == day_value) %>% filter(repeats_on == day_type & repeats_value == day_value) %>%
mutate(segment_id_start = lubridate::parse_date_time(paste(local_date, start_time), orders = c("Ymd HMS", "Ymd HM")) + period(overlap_duration), mutate(segment_id_start = lubridate::parse_date_time(paste(local_date, start_time), orders = c("Ymd HMS", "Ymd HM")) + period(overlap_duration),
segment_id_end = segment_id_start + lubridate::duration(length)) segment_id_end = segment_id_start + lubridate::duration(length)) %>%
select(original_label, label, segment_id_start, segment_id_end, overlap_id, length)
} }
dedup_nonoverlapping_periodic_segments <- function(nested_inferred_time_segments){ dedup_nonoverlapping_periodic_segments <- function(nested_inferred_time_segments){
@ -48,6 +35,8 @@ dedup_nonoverlapping_periodic_segments <- function(nested_inferred_time_segments
# d2,r2,twoday0 twoday1 # d2,r2,twoday0 twoday1
# d3,r3,twoday1 twoday0 # d3,r3,twoday1 twoday0
# d4,r4,twoday0 twoday1 # d4,r4,twoday0 twoday1
if(nrow(nested_inferred_time_segments) == 0)
return(nested_inferred_time_segments)
new_segments <- data.frame(nested_inferred_time_segments %>% new_segments <- data.frame(nested_inferred_time_segments %>%
group_by(original_label) %>% group_by(original_label) %>%
mutate(max_groups = max(overlap_id) + 1) %>% mutate(max_groups = max(overlap_id) + 1) %>%
@ -67,7 +56,7 @@ dedup_nonoverlapping_periodic_segments <- function(nested_inferred_time_segments
add_periodic_segment_timestamps_and_id <- function(segments, local_timezone){ add_periodic_segment_timestamps_and_id <- function(data, segments, local_timezone){
# segment timestamps are computed on the data's timezone(s) # segment timestamps are computed on the data's timezone(s)
time_format_fn <- stamp("23:51:15", orders="HMS", quiet = TRUE) time_format_fn <- stamp("23:51:15", orders="HMS", quiet = TRUE)
segments %>% mutate(segment_start_ts = as.numeric(lubridate::force_tz(segment_id_start, tzone = local_timezone)) * 1000, segments %>% mutate(segment_start_ts = as.numeric(lubridate::force_tz(segment_id_start, tzone = local_timezone)) * 1000,
@ -82,26 +71,16 @@ add_periodic_segment_timestamps_and_id <- function(segments, local_timezone){
assign_to_periodic_segments <- function(sensor_data, time_segments, include_past_periodic_segments){ assign_to_periodic_segments <- function(sensor_data, time_segments, include_past_periodic_segments){
time_segments <- time_segments %>% mutate(length_duration = duration(length)) time_segments <- time_segments %>% mutate(length_duration = duration(length))
every_day_delay <- duration("0days") existent_dates <- get_existent_dates(sensor_data, time_segments, include_past_periodic_segments)
wday_delay <- day_type_delay(time_segments, "wday", include_past_periodic_segments) inferred_segments <- infer_existent_periodic_segments(existent_dates, time_segments) %>%
mday_delay <- day_type_delay(time_segments, "mday", include_past_periodic_segments) dedup_nonoverlapping_periodic_segments()
qday_delay <- day_type_delay(time_segments, "qday", include_past_periodic_segments)
yday_delay <- day_type_delay(time_segments, "yday", include_past_periodic_segments)
sensor_data <- sensor_data %>% sensor_data <- sensor_data %>%
group_by(local_timezone) %>% group_by(local_timezone) %>%
nest() %>% nest() %>%
mutate(every_date = map2(data, local_timezone, get_segment_dates, "every_day", every_day_delay), mutate(localised_time_segments = map(data, add_periodic_segment_timestamps_and_id, inferred_segments, local_timezone),
week_dates = map2(data, local_timezone, get_segment_dates, "wday", wday_delay), data = map2(data, localised_time_segments, assign_rows_to_segments)) %>%
month_dates = map2(data, local_timezone, get_segment_dates, "mday", mday_delay), select(-localised_time_segments) %>%
quarter_dates = map2(data, local_timezone, get_segment_dates, "qday", qday_delay),
year_dates = map2(data, local_timezone, get_segment_dates, "yday", yday_delay),
existent_dates = pmap(list(every_date, week_dates, month_dates, quarter_dates, year_dates), function(every_date, week_dates, month_dates, quarter_dates, year_dates) reduce(list(every_date, week_dates,month_dates, quarter_dates, year_dates), .f=full_join)),
inferred_time_segments = map(existent_dates, infer_existent_periodic_segments, time_segments),
inferred_time_segments = map(inferred_time_segments, dedup_nonoverlapping_periodic_segments),
inferred_time_segments = map(inferred_time_segments, add_periodic_segment_timestamps_and_id, local_timezone),
data = map2(data, inferred_time_segments, assign_rows_to_segments)) %>%
select(-existent_dates, -inferred_time_segments, -every_date, -week_dates, -month_dates, -quarter_dates, -year_dates) %>%
unnest(cols = data) %>% unnest(cols = data) %>%
arrange(timestamp) %>% arrange(timestamp) %>%
ungroup() ungroup()