-
Notifications
You must be signed in to change notification settings - Fork 35
Project Outline
Zong Huang edited this page Apr 30, 2019
·
25 revisions
- Create more detailed example scripts for
template
- Have lab members test
template
(on different computing environments) and try to break it - Refactor
tablefill
andtextfill
- Consider adding minimum versions for required software (Python, Stata, R, Lyx, etc.)
- 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
fromgslab_python
See also "MG Template Notes" in Evernote.
See also Hunt's RA manual here
- 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 inconfig_module.yaml
at the top level of the module.