Skip to content
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.

Exploring trends between daily routine and the body's engine πŸ—“πŸ«€

Notifications You must be signed in to change notification settings

charlieforward9/beat_foundation

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

87 Commits
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

BEAT

An attempt at optimizing the routine of life using the body's engine

See Projects tab for upcoming developments

The Stack

  • App foundation built using Django
  • User Experience controlled with Plotly
  • Database managed with Oracle Developer
  • Application connected to Databases using cx Oracle and Oracle instant Client
  • Input files provided by Google Calendar(Calendar) and Apple Health(Heart Rate) parsed with Python Libraries: dateutil, csvical, datetime, xml.etree, time, random, os, re and sys.

Collecting valid user input

  • Calendar (.ics) parsed using this tool
    • Only events preceded by a category keyword will be counted (case insensitive):
    • Work, Rest, Fitness, Eating, Social or Other
  • Heart Rate (.xml)

Duplicate rows are automatically removed by the parser.

Repo Layout

  • BEAT_PROJECT contains the applciation code, everything that makes the app run (still a local build)
  • BEATPARSER is the current code required to parse the calendar and heart rate data. At this point it is all located in one file and mixed up with code coming from another tool meant to collect ALL Apple Health Data.
  • QUERIES.SQL is the easiest way to see the queries that go into each trend. Integrated queries are in BEAT_PROJECT > myapp > views.py
  • server_connect still figuring out what this is. I think its to connect to the SQL database, but that may be BEAT_PROJECT > manage.py .

About

Exploring trends between daily routine and the body's engine πŸ—“πŸ«€

Topics

Resources

Stars

Watchers

Forks

Contributors 4

  •  
  •  
  •  
  •