<commit_before>FitBit Tools
============

These are my tools and libraries, which I use to manage and interact with
the FitBit API. If you wish to use them, you will have to register a new
app and get credentials from dev.fitbit.com, which is not a difficult task.


Libraries
---------

These are libraries I use to deal with my FitBit data

-   fitbit.py - access to the FitBit API
-   mydb.py - store data locally so I don't abuse the API
-   pushover.py - alerting to my phone
-   spark.py - creating sparklines for Twitter and other social media

Configuration
-------------

I use YAML configuration files to keep from having to hardcode passwords
and tokens into my code. These files show format only.

-   fitbit.cnf
-   my.yaml
-   pushover.yml
-   fitbit.txt - description of the MySQL table I use to store my FitBit data. Not valid SQL.

When using these tools, you must create your own app on FitBit's dev site. For 
"Application Type", choose Desktop, and if you want to use the weight upload 
feature (or add other upload tasks), be sure to choose Read/Write as default 
access type. Otherwise Read-Only is acceptable.

Currently, I use FitBit's API Debug Tool (https://dev.fitbit.com/apps/oauthtutorialpage)
to get access tokens and secrets, but I should and will create a tool that handles this.

Python
------

-   fitbit.battery.py - checks current battery level and alerts if not "high"
-   fitbit.date.py - full db download of FitBit data
-   fitbit.download.py - last few days of FitBit data to configure
-   fitbit.no_sync.py - check if my FitBit has sync'd in the last 3 days
-   fitbit.spark.py - outputs a sparkline showing the ups and downs of my last week's steps
-   fitbit.weight.py - uploads my weight via the FitBit API

RScript
-------

I use R to generate plots of my FitBit data. I'm including two RScripts
which run via crontab. My R is very remedial, and the plots could be made
much prettier with ggplot2 and similar libraries.

-   fb_floors_week.rs
-   fb_steps_week.rs

Copyright and License
---------------------

Copyright (c) 2013 <NAME> (<EMAIL>) and contributors

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:

 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.

 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.


TRIVIAL CHANGE<commit_msg>Added heatmap to README<commit_after>FitBit Tools
============

These are my tools and libraries, which I use to manage and interact with
the FitBit API. If you wish to use them, you will have to register a new
app and get credentials from dev.fitbit.com, which is not a difficult task.


Libraries
---------

These are libraries I use to deal with my FitBit data

-   fitbit.py - access to the FitBit API
-   mydb.py - store data locally so I don't abuse the API
-   pushover.py - alerting to my phone
-   spark.py - creating sparklines for Twitter and other social media

Configuration
-------------

I use YAML configuration files to keep from having to hardcode passwords
and tokens into my code. These files show format only.

-   fitbit.cnf
-   my.yaml
-   pushover.yml
-   fitbit.txt - description of the MySQL table I use to store my FitBit data. Not valid SQL.

When using these tools, you must create your own app on FitBit's dev site. For 
"Application Type", choose Desktop, and if you want to use the weight upload 
feature (or add other upload tasks), be sure to choose Read/Write as default 
access type. Otherwise Read-Only is acceptable.

Currently, I use FitBit's API Debug Tool (https://dev.fitbit.com/apps/oauthtutorialpage)
to get access tokens and secrets, but I should and will create a tool that handles this.

Python
------

-   fitbit.battery.py - checks current battery level and alerts if not "high"
-   fitbit.date.py - full db download of FitBit data
-   fitbit.download.py - last few days of FitBit data to configure
-   fitbit.no_sync.py - check if my FitBit has sync'd in the last 3 days
-   fitbit.spark.py - outputs a sparkline showing the ups and downs of my last week's steps
-   fitbit.weight.py - uploads my weight via the FitBit API

RScript
-------

I use R to generate plots of my FitBit data. I'm including two RScripts
which run via crontab. My R is very remedial, and the plots could be made
much prettier with ggplot2 and similar libraries.

-   fb_floors_week.rs
-   fb_steps_week.rs
-   fitbit_heat_map.rs

Copyright and License
---------------------

Copyright (c) 2013 <NAME> (<EMAIL>) and contributors

 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
 in the Software without restriction, including without limitation the rights
 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the Software is
 furnished to do so, subject to the following conditions:

 The above copyright notice and this permission notice shall be included in
 all copies or substantial portions of the Software.

 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 THE SOFTWARE.


TRIVIAL CHANGE
{'fraction_non_alphanumeric': 0.06579978066739778, 'fraction_numerical': 0.0018799937333542221, 'mean_word_length': 3.4643356643356644, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5226297', 'n_tokens_mistral': 1782, 'n_tokens_neox': 1650, 'n_words': 951}