Updated git and Stata slides

part4.Rmd

@@ -1,7 +1,7 @@
 ---
 title: "Command Line/Git & Version Control/Markdown/"
 author: "Linda Wang"
-date: "January 2023"
+date: "April 2023"
 output: slidy_presentation
 ---
 
@@ -13,7 +13,7 @@ This slide is based on the [Carpentries tutorial on the Unix shell](https://swca
 
 - What is a command line and why use it?
   - Graphical user interfaces are the most common way to give instruction to our computers. They are not good when we need to scale things up, do repetitive tasks, or have people reproduce instructions across systems.
-  - Command-line interface are another way to pass instructions to computers. 
+  - Command-line interfaces are another way to pass instructions to computers. 
   - "Shell" instructions can be scripted, allowing repetitive tasks to be done automatically and fast.
 
 ## Commands in the Unix Shell
@@ -167,7 +167,37 @@ Code embedded in the document:
 
 ```
 
+#### Spacing
 
+- Be sure to leave an empty line after a header.
+
+```
+### Bad example
+#### U.S.Census Population Division
+- Retrieved from https://www.census.gov/geographies/reference-files/2017/demo/popest/2017-fips.html
+```
+
+```
+### Good example
+#### U.S.Census Population Division
+
+- Retrieved from https://www.census.gov/geographies/reference-files/2017/demo/popest/2017-fips.html
+```
+
+- Leave an empty line if you want to start a new paragraph.
+```
+Bad example:
+Thank you for your replication archive.Blablabla.
+**Conditional on making the requested changes to the manuscript and the openICPSR deposit prior to publication, the replication package is accepted.**
+```
+```
+Good example:
+
+Thank you for your replication archive. Blablabla.
+
+**Conditional on making the requested changes to the manuscript and the openICPSR deposit prior to publication, the replication package is accepted.**
+
+```
 
 
 

part5.Rmd

@@ -1,7 +1,7 @@
 ---
 title: "Stata Training"
 author: "Linda Wang"
-date: 'January 2023'
+date: 'April 2023'
 output: slidy_presentation
 ---
 
@@ -13,7 +13,9 @@ These slides are based on the [Stata-related procedures](https://labordynamicsin
 
 ## config.do
 
-![](images/stata_config.png)
+![](images/stata_config_new.png)
+![](images/stata_config_new_2.png)
+![](images/stata_config_new_3.png)
 
 
 ## Purpose
@@ -28,27 +30,31 @@ These slides are based on the [Stata-related procedures](https://labordynamicsin
   - If there is no master.do file, add `include config.do` at the beginning and `log close _all` at the end of the .do file(s) you will run.
   - If there is a master.do file, add the lines to it, only.
 
-### Area 1
 
-- Sets file paths.
-- Creates a sub-directory to save logs in, if necessary.
-- There will be no effect in cases where the authors create their own log files, so do not comment this area out.
+### Walkthrough
 
-### Area 2
+#### Package Installation
 
-- Creates a log file each time you run the code.
-- Labels log files with the timestamp of the current run.
+- Indicates the structure of the code.
+- Installs Stata packages needed for replication.
+- You will need to add package names to line 50. (Use line 52 as an example).
 
-### Area 3
+#### Present/Working Directory Set Up
 
-- Provides information about the system the code is run on, for the replication package.
+- Sets file path to root directory (based on the structure indicated previously).
+- Creates a sub-directory to save logs in, if necessary.
+- Keep this area even if authors' code also produces log files.
 
-### Area 4
+#### Diagnostics
 
-- Sets file path for packages.
-- Installs Stata packages needed for replication.
-- You will need to add package names to line 55. (Use line 56 as an example).
+- Provides information about the system the code is run on, for the replication package.
+
+#### Other
 
+- Includes lines for specific cases, e.g.
+  - Net installation of packages
+  - mata
+  - S drive path set up
 
 ## master.do