Kyle F Butts

Are you misspeaking here? A regression with fewer instrumental variables than endogenous variables should not be able to produce a coefficient estimate. The testing procedure is for the *over*-identified case...

Very slick code @TomBearpark. I have a hunch using `est_env` + putting 0 as weights for a cluster might avoid some overhead in this case. I wonder if an argument...

Nerd-snipped into writing this. It's almost as fast as `summclust::vcov_CR3J` now. It's a bit slower since `summclust` uses smart algebra and demeaning by cluster FE to simplify the amount of...

@s3alfisc I don't know if you saw this, but in the newest version of `fixest`, you can now access the original dataset with an exported function: https://github.com/lrberge/fixest/issues/465 and https://lrberge.github.io/fixest/reference/fixest_data.html

I would really enjoy this feature as well! A plain python file, `# %%`, and the interactive notebook is my favorite part of using python. It seems like discussion of...

Ahh, I think I figured it out. Since it's a call to `glue()`, you can pass a function within the `{}` like `.names = "{gsub("emp_", "share_", .col)}`. Would y'all recommend...

Example: ``` r library(devtools) load_all() spin_w_tempfile = function(..., format = "Rmd") { tmp = tempfile(fileext = ".R") writeLines(c(...), tmp) spinned = spin(tmp, knit = FALSE, format = format) result =...

Correct on both points @yihui! The `rle` solution is nice, thank you.

@cderv I'm confused by this. What is the intended output of the first example? From my understanding of the internals of `knitr::spin`, `#|` are ignored, so they work sort of...

Ahh, yes! I agree. That `#|` works is just because it is left alone by `knitr::spin()`. Just to be clear, you think the result of your first code block should...