= 27d567bc2d48d9f40e9ccc20ea370b15)
TomM comments on Anti-akrasia tool: like stickK.com for data nerds - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (88)
It should be, but I've never tried it with a ping gap other than 45 minutes! The way to find out is to count the actual number of pings in your tagtime log that have the relevant tags on a given day. Your beeminder datapoint for that day should be gap/3600 hours, where gap is the ping gap specified in your tagtime settings (45*60 by default).
Oh, and do a git pull if you haven't since last week or so -- at one time it was in fact hardcoded for 45 minutes.
Actually, looking more carefully, beeminder is calculating accurately for an average of 25 minutes per ping.
Tagtime however got enthusiastic last night - while it pinged me normally for most of the night, it pinged eight times in the hour between 4 and 5 AM.
Beeminder then (reasonably) put me down for an extra hour of sleep that I didn't actually get.
Them's the breaks when dealing with randomised polling!