> Today, we could have dozens of popular Stan models running in any web browser by translating the C++ file to javascript with emscripten or compiling the C++ to PNaCL format which will run in Chrome. But we don't have a WebStan interface and don't have any plan to develop one, even though it would be simpler than the interfaces we have already written because WebStan would basically just be a wrapper around CmdStan.
Sounds like you do have a plan! Let's find someone to do it.
If we can fit models client side, that'd be awesome. I hadn't
wanted to build server-side web apps until we had a way to pay for
hosting.
No plans for Excel or SPSS yet.
We may also want to consider permanently supporting the users who
are never going to want to define their own models in Stan (or for
bglmer() or for BUGS).
> Today, we could have dozens of popular Stan models running in any web browser by translating the C++ file to javascript with emscripten or compiling the C++ to PNaCL format which will run in Chrome. But we don't have a WebStan interface and don't have any plan to develop one, even though it would be simpler than the interfaces we have already written because WebStan would basically just be a wrapper around CmdStan.
Sounds like you do have a plan! Let's find someone to do it.
If we can fit models client side, that'd be awesome. I hadn't
wanted to build server-side web apps until we had a way to pay for
hosting.
> On Monday, May 19, 2014 2:02:03 PM UTC-4, Bob Carpenter wrote:
> No plans for Excel or SPSS yet.
>
> I don't think we need an Excel or SPSS "plan". We just need a way to generate .csv files and maybe combine them so that they can be read into Excel or SPSS or another spreadsheet-like program.
I see. That we should be able to do.
What do they want as input? Presumably not the chains of
samples.
> I believe the exact extent of my plan was to hire a "12 year old HTML5 speaking little dude" and you volunteered Mitzi. I just don't know how to write web apps but there are millions of people that do. It can't be that hard to take user input and build a call to the Stan model.
There aren't millions of people who know how to do it competently,
as you can see by what's actually out there on the web. Luckily,
Mitzi knows more about web dev than most HTML5 speaking little dudes,
even if she doesn't know HTML5 itself.
I don't think the web infrastructure will be the hard part
unless we want to support a wide range of archaic and/or
marginal browsers. Famous last words, of course.
> If we can fit models client side, that'd be awesome. I hadn't
> wanted to build server-side web apps until we had a way to pay for
> hosting.
>
> I think client-side would be fine. Or server-side where the server is Amazon's and people can pay for it themselves.
That we could do, too. For that, we need some 22-year old
MapReduce and virtual machine speaking medium-sized dude(tte).
No need to support archaic or marginal browsers. That is one reason why I was thinking to rely on the HTML5 standard, not that WebStan should embed <video> or anything. But we need to translate the CmdStan arguments to web app things like file finders for data and inits, spinboxes for chains and iterations, drop down menus for sampling vs. optimization, tabs to separate the less-used options from the commonly-used options etc.
# Uncomment the relevant lines
#
# method sample
## num_samples 1000
## num_warmup 1000
...
--
You received this message because you are subscribed to the Google Groups "stan development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to stan-dev+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.