Skip to content

diegogentilepassaro/min_wage_rent

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Do Minimum Wage Policies Have Spatial Effects on Rents?

In this project we explore the effect of minimum wage policies on the housing market within metropolitan areas.

How to use

  • Data is stored in a Google Drive folder here.

    • Make a local copy of the Google Drive folder.
    • If appropriate, create a juncture link to the datastore in the root of the repo. In windows, run mklink /J "<Root of repo>/drive/" "<Local Google Drive folder>" from the command line.
    • A python 2 compiler is required to run the code in this repo. We recommend to install Anaconda and create a python2 environment.

Repository structure

This repository is organized in stages:

  • drive/raw_data hosts large raw files in datastore, and source/raw hosts light raw files
  • base makes a base cleaning of the raw data
  • derived constructs panels at different geographicals levels
  • analysis conducts estimations and counterfactuals
  • descriptive makes graphics and tables that describe

Steps within each of these folders can be run separately, provided that dependencies have been compiled.

  • To do so, go to the /code/ folder and run python make.py in your Anaconda 2 environment

There is also a run.py file in some of the folders that can be used to run steps in parallel.

Writing the paper

Tex files with code for the paper and slides live in ./paper_slides/. Note that none of these folders is compiled using make nor SCons.

Guidelines

  • To enhance GitHub visualization and debugging, we limit lines in Tex files to a maximum of (approximately) 80 characters. As a general rule, we break lines when starting a new sentence. When appropriate, we also break lines following the structure of a sentence. For example,
$$ y_i = a + b x_i + e_i$$
where
$a$ and $b$ are parameters,
$y_i$ is the outcome,
$x_i$ is the independent variable, and
$e_i$ is an error term.
  • An exception to the the line-wrapping rule is allowed when adding figures or tables with long filenames.

  • Footnotes:

    • Always write a footnote after a punctuation mark (., ,, or ;).
    • Write a % sign at the end of a sentence (to prevent extra spacing) and write the footnote in a new line.
    • E.g.,
    some stuff,%
    \footnote{I am a footnote!}
    and some other stuff.
  • We write notes, comments or suggestions after a % sign. Note that any number of spaces and/or commented lines are allowed within paragraphs. E.g., the below is compiled as part of the same paragraph:

    This is a bold claim about the identification of this paper.
    % SH: I'm not sure if identification is so clear, maybe we want to
    %   search for supporting papers.
    An the paragraph continues with some other stuff here.
  • Use oxford comma.

  • To cite a specific section, appendix, table, or figure use caps. E.g., Section \ref{sec:sec_name} or Appendix Table \ref{tab:tab_name}.

    • When the reference is not specific do not use caps. E.g., The following section shows that .. or .. according to the table ..
  • To cite math or an equation do \eqref{eq:eq_name} or equation \eqref{eq:eq_name} when appropriate.

    • Equations are part of a paragraph, use punctuations marks around them when appropriate

Editors

  • For using VS code:

    • Install LaTeX Workshop extension.
    • Set editor rulers at 80 and 120 characters as in here.
  • For using TexStudio:

    • Set TexStudio to break lines for you by going to Option > Configure TexStudio > Advanced Editor. Set Line Wrapping to Hard Line Wrap after Max. Characters, and Maximal Characters to 90.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors 4

  •  
  •  
  •  
  •  

Languages