Show in graph when the real data ends and predictions start

[christophertull]

Maybe add a vertical dotted line where the true data ends? or change to dashed line chart for predicted values?

[patwater]

I like the idea of a dashed line for predicted values though both would work. If we're really smart we'll show error bars for the predicted values ;)

[anudeepvanjavakam1]

Hi Patrick,

Showing error bars is an excellent idea. I will try to work on it.

On 6 December 2016 at 15:21, Patrick Atwater notifications@github.com wrote:

I like the idea of a dashed line for predicted values though both would work. If we're really smart we'll show error bars for the predicted values ;)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/California-Data-Collaborative/RateComparison/issues/26#issuecomment-265305297, or mute the thread https://github.com/notifications/unsubscribe-auth/AVUVJ6KcRFBfeeH4rhx_Qwg3vzwFTNVqks5rFe3pgaJpZM4LA6tr .

[christophertull]

Will take some thought about how we want to do error bars. Right now our forecasts are mean usage for each customer in each month. One option would be deriving error bars from the standard deviation of the residuals for each predicted month.

[patwater]

Yeah I think we might want to hold off on error bars while we're doing this sort of arithmetic accounting type forecast. When we get into more sophisticated econometric type forecasting there's natural links to error bars with OLS and (I think?) also ARIMA.

Might also be some stuff we can learn from the Water Demand Forecasting tool @fwhigh and the DataKind folks built. See here: https://github.com/California-Data-Collaborative/waterd/blob/master/app/train.R

Note also something we discussed with @EricSchles

[christophertull]

Going to close this for now. @anudeepvanjavakam1 added a nice looking line to demarcate the predictions in dde330a6d2aa84b01db86fca6a070123b88916b7:

Created a new issue for discussion of error bounds here: #31