by benhamner on 2/27/17, 5:29 AM with 110 comments
by confounded on 2/27/17, 6:49 AM
Stan is amazing in that you can fit pretty much any model you can describe in an equation (given enough time and compute, of course)!
More on Stan here: http://mc-stan.org/
by rodionos on 2/27/17, 7:30 AM
The wikipediatrend R package relies on http://stats.grok.se/, which in turn relies on https://dumps.wikimedia.org/other/pagecounts-raw/ which has been deprecated.
The new dump is located at https://dumps.wikimedia.org/other/pageviews/
Data is available in hourly intervals.
* pageviews-20170227-050000
en Peyton_Manning 58 0
[edit] There is a wikipedia-hosted OSS viewer for these logs, e.g. Swedish crime stats:https://tools.wmflabs.org/pageviews/?project=en.wikipedia.or...
by saosebastiao on 2/27/17, 3:46 PM
That being said this claim in point #1 baffles me:
> Prophet makes it much more straightforward to create a reasonable, accurate forecast. The forecast package includes many different forecasting techniques (ARIMA, exponential smoothing, etc), each with their own strengths, weaknesses, and tuning parameters. We have found that choosing the wrong model or parameters can often yield poor results, and it is unlikely that even experienced analysts can choose the correct model and parameters efficiently given this array of choices.
The forecast package contains an auto.arima function which does full parameter optimization using AIC which is just as hands free as is claimed of Prophet. I have been using it commercially and successfully for years now. Maybe prophet produces better models (I'll definitely take a look myself), but to claim that it's not possible to get good results without experience seems a bit disingenuous.
As an aside, anybody interested in a great introductory book on time series forecasting should check out Rob Hyndman's book which is freely available online. https://www.otexts.org/fpp
by schlarpc on 2/27/17, 6:47 AM
by techno_modus on 2/27/17, 9:46 AM
by cardosof on 2/27/17, 6:25 AM
A few days ago I was asked to do some forecasting with a daily revenue series for a client. Due to her business' nature the series was really tricky with weekdays and months/semesters having some specific effects on the data. I as many use Hyndman's forecast package, but I threw this data at prophet and it delivered a nice plot with the (correct) overall trend and seasonalities. Very cool and easy to do something.
by yoghurtio on 2/27/17, 7:42 AM
Its a completely managed solution. No need to setup anything yourself.Just upload the data and predict next week's data, today itself. There is a free trial and if anyone here is looking for an extended trial, they can reach out to me.
by anacleto on 2/27/17, 9:15 AM
I've been using CasualImpact by Google [0] for months. This seems pretty straightforward.
by jl6 on 2/27/17, 6:39 AM
by pacifika on 2/27/17, 7:30 AM
by asafira on 2/27/17, 6:02 AM
Very cool though --- I would be interested to dive into the methods they've implemented sometime in the near future!
by hnarayanan on 2/27/17, 6:49 AM
by dmichulke on 2/27/17, 1:01 PM
It's major benefit is that it figures out relationship to the target time series by itself, so you can just throw in all time series and see what comes out.
Language is Clojure, 20kloc, incanter, encog. If anyone is interested in working for/with it, let me know. I currently develop a Rest Api for it and plan to release it as open source once the major code smells are dealt with.
by Steeeve on 2/27/17, 8:21 AM
Between this and Stan I think my free time for the next week is gone.
by zebrafish on 2/27/17, 2:57 PM
You talk about having to choose the best algorithm but it seems like Prophet is just another algorithm to choose from. Is there some kind of built in grid-search or are you just stating that results from your AM have been more accurate than ARIMA?
by hn_username on 2/27/17, 4:37 PM
Some feedback: it'd be nice to see you actually quantify how accurate Prophet's forecasts are on the landing page for the project. In the Wikipedia page view example, you go as far as showing a Prophet forecast, but it'd be nice to have you take it one step further and quantify its performance. Maybe withhold some of the data you use to fit the model and see how it performs on that out of sample data. It's nice that you show qualitatively that it captures seasonality, but you make bold claims about its accuracy and the data to back those claims up is conspicuously absent. Related, it might be worth benchmarking its performance against existing automated forecasting tools.
I'll definitely be checking it out!
by SmellTheGlove on 2/27/17, 4:25 PM
I got really excited for a second. Actually, I'm still pretty excited about this even if it was something else entirely.
by nickfzx on 2/27/17, 11:16 AM
We're planning to add forecasting to our SaaS analytics product (https://chartmogul.com) later this year, I'm going to look and see if we can use this in our product now.
by minimaxir on 2/27/17, 6:54 AM
See also the R vignette, which shows that the data is returned per-column which gives it a lot of flexibility if you only want certain values: https://cran.r-project.org/web/packages/prophet/vignettes/qu...
by paulvs on 2/27/17, 3:49 PM
I see this being applicable to analysts when deciding on on a company's credit worthiness.
by syntaxing on 2/27/17, 4:47 PM
by monkeydust on 3/4/17, 8:15 AM
Has anyone managed to get this working on windows with Juypter (Anaconda build) struggling with Pystan errors. Any guidance welcomed.
by eternalban on 2/27/17, 1:36 PM
by elwell on 2/27/17, 8:59 PM
by nodesocket on 2/27/17, 8:35 AM
by alexpetralia on 2/27/17, 2:28 PM
by poppingtonic on 2/27/17, 9:42 AM
by recurser on 2/27/17, 9:28 AM
by ayayecocojambo on 2/27/17, 11:20 AM
by agounaris on 2/27/17, 6:38 AM
by hubot on 2/27/17, 2:49 PM
> df['y'] = np.log(df['y'])
by Helmet on 2/27/17, 5:42 PM
by fagnerbrack on 2/27/17, 7:02 AM