Christopher Peters comments

Results 13 comments of


                                            Christopher Peters

rake script fail when deployed to production environment

:+1: Third instance of exact bug. Moving 'stringex' out of the development group fixes it.

rake script fail when deployed to production environment

@danielricecodes that feels like the best method to me, too! :thumbsup: I closed the PR: https://github.com/imathis/octopress/pull/1541

Statwonk's suggested edits

Bah, new laptop. Seems my author amendment didn't take.

Statwonk's suggested edits

> This is because brms handles the priors for the default intercept under the presumption you’ve mean-centered all your predictor variables. Wow, I didn't realize this. Good to know.

function for explaining what query will be performed

:clap:

function for explaining what query will be performed

@sckott curious what kind of improvements you'd like to see here?

Test of ids fails for ES 2.0.0

Meanwhile other versions pass: https://travis-ci.org/ropensci/elasticdsl/builds/116706791 It feels like it might be a race condition, is there a way to force a re-run @sckott?

Prototype of an aggs parser handle.

I think it might be nice to shoot for a syntax like, `aggs(my_statistic = mean(decimalLatitude))` `aggs(my_statistics = quantile(decimalLatitude))` `aggs(my_terms = terms(play_name))` The challenge comes in [with nesting](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-aggregations-bucket-nested-aggregation.html) ...

Prototype of an aggs parser handle.

for my own reference: http://adv-r.had.co.nz/dsl.html

Prototype of an aggs parser handle.

:+1: One thing of mention re: last call, I think a `verbose` option that would allow the end user see the call construction in `json` could really help usability.