gslab-econ / gslab_stata Goto Github PK

Let's drop all subdirectories of this repository except:

• /crosswalk/
• /gslab_misc/
• /xtreg_ch/

Let's also add a short readme inside each subdirectory summarizing what they do. For crosswalk and xtreag_ch you can base these on the help files. For gslab_misc you can keep the current readme but delete the "Description" header.

Hi, I am running Stata 14.2 on Windows and tried to follow the instructions to install gslab_misc given in the corresponding readme.md file. I got the following error:

. net uninstall benchmark 
package not found
r(111);

It looks like net uninstall fails when the package does not exist. Might it be better to just have a series of net install <package>, replace commands instead of a series of net uninstall, net install command pairs? Thanks

In this issue we'll bring the autofill program we've written in Protests to this repo.

Increment to version 14.

Hey @arosenbe ,
I am not sure who is in charge of this repo but I wanted to share some code for STATA. I wrote a short .ado file to parse yaml file as we use them to define constants at the top of repositories (Typically in a constants.yaml type file) and write these to globals/locals. My file is located here. The original hope was sharing this code would help gslab use yaml files for STATA still.

unfortunately, I just noticed via a reference here that apparently a STATA YAML reader already exists, but was unable to locate it in gslab_stata or generic googling. So I thought I would open this issue to complete one of the following:

• input the referenced yaml program in the ad-price-driver STATA script as a part of gslab_stata so all gslab people have it.
• include my program so that everyone has a YAML parser
• include some other YAML reader I am unaware of as part of gslab_stata

I am going to go out on a limb and assume the referenced yaml reader in the ad-price-driver script is far more sophisticated than mine, and probably should be the standard one used.

Let me know your thoughts

Goal: to clarify how users install the repository's code libraries.