The Road Editor is a Bee Plus / Beemium feature that gives you an interface for making very specific changes to your road. Take a Break lets you change the rate temporarily, ratcheting lets you immediately make the road jump closer to your data, and you can use the road dial to change the rate more permanently. The Road Editor lets you do all of those things in one tool, and with a lot more precision!
Reading the Road Editor
There are three sections:
- Start date & value: the date and value at which your yellow brick road begins
- Road rows: each of these defines one segment of the yellow brick road
- End date/rate/value: defines the final segment of the yellow brick road
Each of the three-part road segments is combined to create the entire road. The segments take two values and infer the third, and can be understood as follows:
- a date-rate segment ( X _ Z ) makes the road have Z slope through X date
- a date-value segment ( X Y _ ) jumps the road to Y value on X date
- a value-rate segment ( _ Y Z ) makes the road have Z slope until it reaches Y value
Using the Road Editor
Because the road editor is how Beeminder goals are represented in the database, you can recreate any standard Beeminder features using it!
- A derailment, for example, is usually created by adding a date-rate segment followed by a date-value segment. It creates a row that preserves the shape of the road you were following until you derailed, then a second row that moves the road position to your current value. There might be a second date-rate if you don't have no-mercy on, so you get the 7 days off afterward.
- A ratchet usually adds a date-rate segment, to preserve the shape of your road up until you hit the button, and a date-value segment, using today's date and the value that best corresponds to the number of safe days you wanted left
- Take a break adds two date-rate segments: one that ends the day before your break to preserve the current shape of your road, and one that ends the final day of your break that uses your break rate instead.
(The above road subset is from a goal with rate 5. A break was taken from 2016-08-27 through 2016-09-05. The rate went back to 5 per week after the break, but then it derailed on the 11th and got a week off. Then it derailed again on 2016-10-11, and got another week off!)
All of the above are changes to the present or future state of the goal. You can also use the road editor to change the past, if you're so inclined — you could smooth out previous rate changes, or remove breaks that weren't necessary, or deemphasize prior derailments if you caught up enough after-the-fact! With the Road Editor, you have complete control over how the road is drawn (as long as you don't make it easier in the next 7 days).
To make changes to existing rows, edit the values inside. If you need to add or remove a row, use the +/- buttons on the right-hand side, or the Add Row button to add a row directly to the bottom. Once you've made all your changes, click Update Road to submit!
Debugging the Road Editor
Unfortunately there's no "preview changes" functionality yet, so you can instantly derail your goal if you make a bad change. The Undo Road Edit button will restore your graph to its previous state, and you'll need to reply to the legitimacy check for support to cancel the charge.
If you've accidentally busted your goal and are trying to self-diagnose, some common "bad road" error triggers to check for are:
- Illogical rate/value combinations (e.g., trying to lose weight at -1 pound per week until you reach 200, when your last datapoint was 196). Usually this is fixable by changing the rate from negative to positive, or vice versa — but make sure the final graph image looks reasonable, or you may end up committed to something you didn't intend!
- Duplicate row included
- Road row with 1 or 3 values was submitted, rather than 2
- Road rows submitted with dates out of order
- Final road row has a date that is earlier than the last middle road row
UPDATE: We have a prototype Visual Road Editor!