Bram
/
BangleApps
forked from FOSS/BangleApps
1
0
Fork 0
Code Pull Requests Activity

[sleeplog] Update README.md

master
storm64 2022-05-20 20:17:48 +02:00 committed by GitHub
parent cdff3173ba
commit 5e7d8c14b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 19 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

35
apps/sleeplog/README.md
View File

@ -23,12 +23,14 @@ I would love to hear about your impressions and like to know your choice of thre
The last piece of work is to rewrite the README.md to show how to use it and show the restrictions and possibilities. The last piece of work is to rewrite the README.md to show how to use it and show the restrictions and possibilities.
But here are some explanations how to use the app and settings: But here are some explanations how to use the app and settings:
- __On the app screen:__ - __On the app screen:__
- swipe left & right to change the displayed day - swipe left & right to change the displayed day
- touch on the "title" (e.g. `Night to Fri 20/05/2022`) to enter a day selection prompt - touch on the "title" (e.g. `Night to Fri 20/05/2022`) to enter a day selection prompt
- touch on the info area (by default displaying consecutive and true sleeping) to change the displayed information - touch on the info area (by default displaying consecutive and true sleeping) to change the displayed information
- touch on the wrench (upper right corner) to enter the settings - touch on the wrench (upper right corner) to enter the settings
- exit the app with the UI back button widget on the upper left corner - exit the app with the UI back button widget on the upper left corner
- __Inside the settings:__ - __Inside the settings:__
- the threshold values are accessible through a submenu - the threshold values are accessible through a submenu
- app timeout lets you specify a separate `lockTimeout` and `backlightTimeout` only for the sleeplog app - app timeout lets you specify a separate `lockTimeout` and `backlightTimeout` only for the sleeplog app
@ -38,22 +40,23 @@ But here are some explanations how to use the app and settings:
- the `Duration` specifies how long data should be written into the .csv file - the `Duration` specifies how long data should be written into the .csv file
- the .csv file loggs the following data (timestamps are in days since 30.12.1899 as used by office software): - the .csv file loggs the following data (timestamps are in days since 30.12.1899 as used by office software):
_timestamp, movement, status, consecutive, asleepSince, awakeSince, bpm, bpmConfidence_ _timestamp, movement, status, consecutive, asleepSince, awakeSince, bpm, bpmConfidence_
- __Timestamps and files:__
1. externally visible/usable timestamps (in `global.sleeplog`) are formatted as UNIX timestamps: - __Timestamps and files:__
seconds since 1970-01-01 00:00 UTC 1. externally visible/usable timestamps (in `global.sleeplog`) are formatted as UNIX timestamps:
2. internally used and logged (to `sleeplog.log (StorageFile)`) is within the highest available resolution: seconds since 1970-01-01 00:00 UTC
10 minutes since 1970-01-01 00:00 UTC (`UNIX / (10 * 60 * 1000)`) 2. internally used and logged (to `sleeplog.log (StorageFile)`) is within the highest available resolution:
3. debug .csv file ID (`sleeplog_123456.csv`) has a hourly resolution: 10 minutes since 1970-01-01 00:00 UTC (`UNIX / (10 * 60 * 1000)`)
hours since 1970-01-01 00:00 UTC (`UNIX / (60 * 60 * 1000)`) 3. debug .csv file ID (`sleeplog_123456.csv`) has a hourly resolution:
4. logged timestamps inside the debug .csv file are formatted for office calculation software: hours since 1970-01-01 00:00 UTC (`UNIX / (60 * 60 * 1000)`)
days since 1899-12-30 00:00 UTC (`UNIX / (24 * 60 * 60 * 1000) + 25569`) 4. logged timestamps inside the debug .csv file are formatted for office calculation software:
5. every 14 days the `sleeplog.log (StorageFile)` is reduced and old entries are moved into separat files for each fortnight (`sleeplog_1234.log`) but still accessible though the app: days since 1899-12-30 00:00 UTC (`UNIX / (24 * 60 * 60 * 1000) + 25569`)
fortnights since 1970-01-04 12:00 UTC (converted with `require("sleeplog").msToFn(UNIX)` and `require("sleeplog").fnToMs(fortnight)`) 5. every 14 days the `sleeplog.log (StorageFile)` is reduced and old entries are moved into separat files for each fortnight (`sleeplog_1234.log`) but still accessible though the app:
- __Logfiles from before 0.10:__ fortnights since 1970-01-04 12:00 UTC (converted with `require("sleeplog").msToFn(UNIX)` and `require("sleeplog").fnToMs(fortnight)`)
timestamps and sleeping status of old logfiles are automatically converted on your first consecutive sleep or manually by `require("sleeplog").convertOldLog()` - __Logfiles from before 0.10:__
- __View logged data:__ timestamps and sleeping status of old logfiles are automatically converted on your first consecutive sleep or manually by `require("sleeplog").convertOldLog()`
if you'd like to view your logged data in the IDE, you can access it with `require("sleeplog").printLog(since, until)` or `require("sleeplog").readLog(since, until)` to view the raw data - __View logged data:__
since & until in UNIX timestamp, e.g. `require("sleeplog").printLog(Date()-24*60*60*1000, Date())` for the last 24h if you'd like to view your logged data in the IDE, you can access it with `require("sleeplog").printLog(since, until)` or `require("sleeplog").readLog(since, until)` to view the raw data
since & until in UNIX timestamp, e.g. `require("sleeplog").printLog(Date()-24*60*60*1000, Date())` for the last 24h
--- ---