Skip to content

Project Outline

Zong Huang edited this page Apr 25, 2019 · 25 revisions

To-dos

  • Make error handling as robust and user-friendly as possible
  • Add functionality to inputs.txt that checks inputs have an unmodified git status and give friendly warning if check fails
  • Create more detailed example scripts for template
  • Have lab members test template (on different computing environments) and try to break it
  • Write README.md and add user guides where appropriate
  • [In progress] Refactor tablefill and textfill
  • Consider adding minimum versions for required software (Python, Stata, R, Lyx, etc.)
  • Add output_local functionality
  • Add top level /examples/ directory containing modules illustrating lots of different use cases. Consider making the main repository modules use only Python + Latex and then use the /examples/ to illustrate Stata, R, Lyx, as well as other things like Matlab, etc. that we want to support.
  • Remove gslab_make from gslab_python

See also "MG Template Notes" in Evernote.

See also Hunt's RA manual here

To add to RA manual

  • Rules for raw data directories including readme.txt
  • Each directory should be able to run on clean checkout of repo; so anything called by inputs.txt must be checked in
  • config_user.yaml should never be committed
  • Do not commit commented out code in major commits
  • config.yaml should be a one stop shop for all repository-wide metadata. Metadata that pertains only to a single module can be stored in config_module.yaml at the top level of the module.
Clone this wiki locally