R code

[grantmcdermott]

Hi Asjad,

Thanks for putting together this excellent public good.

Would you be open to adding R code examples that match the existing Stata pages on the site?

I know most of the packages quite well and should be able to get a PR submitted fairly quickly if you're up for it.

The main structural thing we'd have to think about ahead of time is organization of the repo for navigation. E.g. Would you want (tabbed?) R and Stata code on the same page, or should they just resolve to separate subdirs?

[asjadnaqvi]

Dear Grant,

That would be awesome! Have been looking for someone to complete the R part for a while.

I would prefer a separate R directory and subfolders. This will ensure that the R section itself reads smoothly. One can always cross-reference if needed.

[grantmcdermott]

Super! I'll try to get on it ASAP.

Gotcha on the separate directory structure. Three more quick things while I have you, since these will save me time down the line.

• The relative Stata code directory/nav path currently resolves to docs/code. Are you okay with me renaming this to docs/code_stata, moving all the sub-folders across, and adding the R stuff under docs/code_r? It would be a breaking change as far as links go, but nice for code symmetry.
• Are you okay with me sightly changing the notation on the R stuff, e.g. using 'time' instead of 't'? Everything would still work with the latter. But I try to steer people away from using t as a variable, since t() is a base function and creates potential for an implicit namespace clash. (Similar to 'c' and 'c()'.) Again, feel free to say no if you'd rather preserve a strict equivalence across the R and Stata examples.
• Can we use a dedicated "data generation" page instead of repeating this step on every sub-page? Obviously, this could apply to the Stata pages too. Apart from my DRY adherence, I think keeping the data gen stuff separate will help readers to focus on the operationalized of each package.

[asjadnaqvi]

1) Yep that is fine! As long as the relative paths are fixed and the pages don't break.

2) That is fine. Let's standardize id and time to id and time. I will change it once you push the updates. I also have a couple of minor errors to fix so I will do it in one go.

3) Yep. I have been planning to do this for a while now. The initial thinking was to keep each page complete especially if someone is interested in just one estimator. But it makes more sense to have a dedicated data generation page.