Corrected fitbit and CRF app data merge

Sage-Bionetworks / CRF_validation_analysis

analysis code for CRF validation study

0 stars 1 forks source link

Corrected fitbit and CRF app data merge #15

Closed itismeghasyam closed 4 years ago

itismeghasyam commented 6 years ago

Updated the fitbit heartrate extraction from recordId based to healthCode based platform
While merging now the fitbit data from the previous day as upload date is also counted (like for eg., if the fitbit data is uploaded on 22nd of April 9PM for 24hrs, it will contain data for the 12MT stair test done on 23rd of April at say 4AM)
Right now the healthCodes in only one timezone are considered, dealing with healthCodes which have multiple time zones has not been done yet

itismeghasyam commented 6 years ago

resolves issue #4 , but creates another one. If healthCodes have multiple timezones (Thank day light savings for most of them), they are not considered now. The timezone is required because, we use it in converting the fitbit data to UTC. The fitbit table does not have the createdOnTimeZone and we are currently populating it from the activities table.

itismeghasyam commented 6 years ago

Added polar data functionality too

itismeghasyam commented 4 years ago

I checked all the code, it is up to date and in sync with the algorithm used on the phone

itismeghasyam commented 4 years ago

Closing this PR since there is another one from a more relevant branch