coolhandlouis/zscooplitter

coolhandlouis/zscooplitter:

+1 due

or pay $5*

DAYOF GOAL

DAY	DELTA	TOTAL
Today	✔	29
Tomorrow	✔	29
Wed (8th)	✔	29
Thu (9th)	✔	29
Fri (10th)	✔	29
Sat (11th)	+1	30
Sun (12th)	+2	31

Datapoints ?

Your actual reported data. The color shows where you are with respect to your bright red line:

Green:
> 3 days of buffer

Blue:
~ 2 days of buffer

Orange:
~ 1 day of buffer

Red:
crossed the red line
Bright Red Line ?

Keep your dots on the good side of this bright red line!
Colored guiding lines ?

The orange line shows one day of safety buffer. The blue line is two days, and the green line demarcates seven days of safety buffer.

(If you keep your safety buffer at 7 days or higher then you're immune to being stung. If anything comes up, just flatten your bright red line. It will take effect after the 7-day akrasia horizon but since you have that much safety buffer, you're golden!)
Yellow guide lines ?

These thin yellow lines indicate the good side of the bright red line.
Akrasia horizon ?

This line is a week away from now. You can only make changes in the steepness of your red line beyond the akrasia horizon.
Pink zone ?

This shaded pink zone on the wrong side of your bright line shows the bare minimum that you are committed to doing this week. Your red line can never get easier and dip into this forbidden zone.
Infinitely safe region ?

This light yellow shaded region shows the infinitely safe area. If your datapoints are in this zone, then you have exceeded the final total of your graph, and your safety buffer is unbounded. You usually see this as your goal approaches the end date, or if you have an infinitely flat bright red line for some reason.
Skull & Crossbones ?

We fly the Jolly Roger on your graph if it freezes. The primary way this happens is if you derail when your graph is scheduled to be archived.
Watermarks ?

The watermarks in the corner regions of your graph (shown darker here) indicate your current pledge amount and how much safety buffer you have. How safe you are is shown on the good side of the red line, and the amount pledged is shown on the derails-this-way side.

Features not enabled on this graph:

Optimistic projection (deprecated) ?

An optimistic view of progress, i.e., a view of your data through rose-colored glasses. It shows your inexorable march towards your goal. If you're bouncing around it just shows you flat. When you go down (or whichever direction your goal is), it shows you that right away.

It never shows you going up (or whatever the wrong direction is) unless it's sure you've screwed up.

If you find the random fluctuation unnerving, you can focus on the pink dots day-to-day.
Moving average ?

This is a moving average implemented as an IIR filter. If most of your daily numbers are below this trend line then you are inexorably dragging it down.

For the case of weight loss, this was inspired by The Hacker's Diet as a way to see the forest through the trees, to see past the daily random fluctuations to what your weight is really doing.
Smoothed trend swath ?

Think of this as a very thick line charting your progress or an aura around your actual data. It's like the moving average line but fatter and smoother, and it extends past your actual data as a kind of projection into the future, in case that's useful. (Gory details on the blog.)
Max flux ?

This thicker yellow line denotes the user-specified maximum daily fluctuation, shown as an offset from the bright red line. Details in the FAQ.
Standard flux ?

This dashed yellow line indicates a so-called 90% variance derived from your data, shown as an offset from the bright red line. Details in the FAQ.

Careful what order you edit datapoints in. Beeminder derails you if your data crosses the red line, even retroactively. (Also FYI this goal is auto-summing aka cumulative, which can be confusing.)

Date

Value

Comment

This goal has the following fine print specified by coolhandlouis:

I want to accomplish this goal every day. However, I'm only going to be responsible to beeminder to complete this goal once every 5 days. While this leaves me an "out" to drop my performance, it aslo reduces my beeminder pressure, which reduces chance of beeminder burn-out.

This is an experimental goal. "DAYOF" means I only track the goal on (the "day of") it's beemergency due date. I still endeavor to complete the task on other days, but that's entirely outside beeminder and I do not increment on those days.

I'm trying to figure out if it's ok to OPTIONALLY mark a off-day as "done +1", or perhaps even retroactively mark an off-day as "done +1". I'll need to iron out the details to ensure that I remain on the good side of beeminder paradgim, non-weaselly, no fake data, etc. OTOH, it's a little complicated, and just sticking to "only increment on beemergency day" is a paradigm-safe way to manage this.

I think the following is paradigm-safe: OPTIONAL data entry on any day. If I want to kick the beeminder can down the road, I can. For example, if it's beeminder 1/5 days, then the presumptive schedule is done on day 5 and 10. But if today is the 4th day, i can mark it done and kick the beeminder can down to day 9. I've only shifted my 1/5 days to a little earlier. This is best managed with an auto-ratchet to 5 days.

On the other hand, I don't think I can easily retroactively mark yesterday as done if today is a beemergency. That could effectively create the same schedule such as on day 5, making the schedule be done on day 4 and next beemergency is day 9. However, the auto-ratchet to 5 days may not work in some situations, and it's a bit weaselly if i retroactively kick the can down the road and also don't complete today's beemergency task. Even though it's no different, it doesn't feel right.

Amounts Due By Day

Goal Progress

Stats

Graph stats

Data stats

Graph Legend