<commit_before># node-rrtpmonitor
Check the current ComEd RRTP Rate and trigger an event in IFTTT.

## Installation
As this isn't properly packaged up in NPM yet, simply copy these files into any folder.
You will need to use NPM to install Resilient which is a declared dependency for this package.

## Configuration
At a minimum, modify the 'config.json' to put in your [IFTTT](https://ifttt.com) [Maker Channel](https://ifttt.com/maker) key.  You can, if you wish, also change the event name (currently set as 'rrtp' in 'the maker.path'.

You may need to edit the first line of 'rrtpmonitor.js' in order to set the path for 'node'.

You can also feel free to adjust the 'thresholds', be sure to keep them in low-to-high value order, otherwise, the code will not work as expected.

At runtime, the rrtpmonitor will expect to be running in the same folder as it's installed (as I'm using relative path for the 'config.json'), and will need read/write access to the file/folder that is set for 'lastThresholdFileName'.

There should only be console output when there's a problem.

I've installed it as a crontab job on my Raspberry Pi B+ 2, that runs every 5 minutes.<commit_msg>Fixed some markdown.<commit_after># node-rrtpmonitor
Check the current ComEd RRTP Rate and trigger an event in IFTTT.

## Installation
As this isn't properly packaged up in NPM yet, simply copy these files into any folder.
You will need to use NPM to install Resilient which is a declared dependency for this package.

## Configuration
At a minimum, modify the `config.json` to put in your [IFTTT](https://ifttt.com) [Maker Channel](https://ifttt.com/maker) key.  You can, if you wish, also change the event name (currently set as `rrtp` in the `maker.path`.

You may need to edit the first line of `rrtpmonitor.js` in order to set the path for 'node'.

You can also feel free to adjust the `thresholds`, be sure to keep them in low-to-high value order, otherwise, the code will not work as expected.

At runtime, the rrtpmonitor will expect to be running in the same folder as it's installed (as I'm using relative path for the `config.json`), and will need read/write access to the file/folder that is set for `lastThresholdFileName'.

There should only be console output when there's a problem.

## Runtime
I've installed it as a crontab job on my Raspberry Pi B+ 2, that runs every 5 minutes.
{'fraction_non_alphanumeric': 0.06781802864363942, 'fraction_numerical': 0.0016849199663016006, 'mean_word_length': 4.2312775330396475, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1390001', 'n_tokens_mistral': 675, 'n_tokens_neox': 660, 'n_words': 380}