Open apratap opened 5 years ago
For this, I suggest dropping to the columns: participant_id, cid, category, week, time_in, and time_out
Should we include the timezone offset in the timestamps?
And finally, to match the other tables I suggest renaming to Passive Cluster Entries Brighten v2
# | Variable Name | Data Type | Description |
---|---|---|---|
1 | participant_id | str | Unique ID |
2 | week | int | The $$( n^{th} )$$ week into the study |
3 | cid | str | Unique of participant's identified location |
4 | category | str | Semantic category of location |
5 | time_in | str | Timestamp of location entry (local) |
6 | time_out | str | Timestamp of location exit (local) |
I agree this covers the baseline well
In the interest of keeping it simple and hopefully useful lets merge the following two tables
GPS Cluster Entries (v2):
Identified Clusters Data Dictionary: the only reason we have this table is to keep
mean_ti_between_visits
. Let's get rid of that and merge with the table above.PS: For internal analysis please still keep all the features available in the internal project.
-A