I see from the earlier comments that this runs some sort of "optimized" ARIMA model. Is there anyway to output the statistical information of the fitted model though the API?
Show HN: Unplugg: An automated Forecasting API for timeseries data
11–20 of 35 posts
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#12dear lord, why? this reminds me of the old "xml binary format" joke:
0 0 1 0 0 1 0 0
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#13I see from the earlier comments that this runs some sort of "optimized" ARIMA model. Is there anyway to output the statistical information of the fitted model though the API?
Not really. We're directing this more towards a completely automated use-case of forecasting with no human interaction, so it's not on our plans to release internal parameterization of the forecast.
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#14Earlier quoted context omitted.
Not really. We're directing this more towards a completely automated use-case of forecasting with no human interaction, so it's not on our plans to release internal parameterization of the forecast.
Hmm, I think at the minimum, the variance of the forecasted results should be obtainable. I'm not sure how many people would use a black box model without knowing some sort of performance/statistical confidence metric.
I do believe we have some similar feature in the pipeline for development, I'll make sure to push it forward. Thanks for the feedback.
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#15{ "timestamp": 1458000000, "value": 63.422235 }, dear lord, why? this reminds me of the old "xml binary format" joke: 0 0 1 0 0 1 0 0
EDIT: But XML payloads are actually a really useful idea, it's going ASAP to the Trello board. :p
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#16{ "timestamp": 1458000000, "value": 63.422235 }, dear lord, why? this reminds me of the old "xml binary format" joke: 0 0 1 0 0 1 0 0
Yeah, it's kind of verbose right now :p We'll get around to it when we make sure the forecast is the best it can be. EDIT: But XML payloads are actually a really useful idea, it's going ASAP to the Trello board. :p
but in all seriousness, why the timestamp at all? your examples are all spaced at 3600ms. asking for it implies certain behavior. can you handle heterogeneous interval data? missing data?
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#17Earlier quoted context omitted.
Yeah, it's kind of verbose right now :p We'll get around to it when we make sure the forecast is the best it can be. EDIT: But XML payloads are actually a really useful idea, it's going ASAP to the Trello board. :p
hah. well hopefully you support http gzip compression. :) but in all seriousness, why the timestamp at all? your examples are all spaced at 3600ms. asking for it implies certain behavior. can you handle heterogeneous interval data? missing data?
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#18Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#19Is this somehow connected to facebook Prophet? How do you compare?
As fate has it, we have no connection to FB's Prophet - we at Whitesmith have been working on unplugg for some time now and decided a few weeks ago that this week we'd share it on some communities to have more people testing it and more feedback. It seems that the folks over at Facebook decided something similar. You know what they say, great minds :p
Joking aside, as intimidating as it might have been to see FB releasing a related tool, we feel that we still fill a different segment. From what I've been reading today, Prophet is a tool tailored for timeseries forecasting with human interaction and input in mind - it can work like a black forecasting box but it seems that it is the most useful when paired with an analyst that can keep looking at the output and tweak the model accordingly. It is _really friendly_ as far as forecasting packages go and trust me, we looked at a fair amount of them. That and the use of ProbProgramming to infer their params is just awesome (I'm a fervent Bayesian at heart).
Unplugg on the other hand, fills the need for a "generic" forecasting tool for uses where you don't want/need much specific tailoring and want a really Plug&Play solution - it's an API that you can call from pretty much everywhere, with no dependencies or specific environments needed (so no need to deploy your own R/Python/Matlab - yikes - environment where your models live and run). One possible use case would be an energy monitoring portal that lives completely client-side and requests forecasts to our API on-the-fly directly from the client.
We are still actively developing and testing different forecasting models - the one running is just the one we feel most confident about - and will be looking at Prophet as a possible alternative (although I haven't seen their license carefully, so can't be sure).
Re: Show HN: Unplugg: An automated Forecasting API for timeseries data
#20Earlier quoted context omitted.
Hmm, I think at the minimum, the variance of the forecasted results should be obtainable. I'm not sure how many people would use a black box model without knowing some sort of performance/statistical confidence metric.
We could return a confidence interval for the forecasted values, you're right, it can help in cases where it would be used for simple anomaly detection (and it would give a greater sense of security/control over using the forecast). I do believe we have some similar feature in the pipeline for development, I'll make sure to push it forward. Thanks for the feedback.