Skip to content

About

Report Driven Template for experiments

Resources

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

report_driven_template

Report Driven Template for experiments

Setup Instructions

fork THIS repo

  1. navigate to https://github.com/colinlclark/report_driven_template.git
  2. in the top right corner, click "Fork" and create a fork under your own github account. Fork Button
  3. In your fork of report_driven_template click the "Code" button and copy the URL to clone the repo into a directory on your computer.
  4. clone the repo onto your computer -- note that git clone creates a folder with the name of the git repo in the directory where it is run, so if are in /usr/you/code and you run clone clone .../report_driven_template.git it will create a new directory /usr/you/code/report_driven_template which will now contain your local copy of the code.
    cd
    cd code
    git clone https://github.com/[your git username]/report_driven_template.git
    
  5. navigate to the directory you just pulled your fork of the repo into: cd report_driven_template

software dependencies

  1. install texlive from here.
  2. install anaconda from here
  3. install git from here

pip and conda

  1. conda install numpy pandas gitpython tabulate matplotlib

running the code, committing and pushing to github

  1. Edit utils/latex_header.tex to add yourself as \author and change the title
  2. python my_project.py
  3. latex report_for_my_project.tex
  4. git add img/*.png if you have added any plot images
  5. git add data/*.csv if you have added any plot images
  6. git commit -am "[describe what you have done]"
  7. git push

Code Development Suggestions:

  1. Print all of your results to the output files -- never manually generate an important result -- never consider an experiment finished until it is securely documented in the report_for_my_project.pdf or report_for_my_project.md file on github.
  2. Add commentary as you go, don't generate a naked result and move on to the next experiment without wrapping it up by writing some notes about how you arrived at that result and your interpretation of it.
  3. Commit git commit -am "brief note" and push git push your code often -- this is your "save" procedure for your project.

files:

.gitignore

File where extensions and files that should not be included in the git repo are listed -- preconfigured for python, LaTeX, emacs, and vim

my_project.py

Script where your experiment is performed

report_for_my_project.tex

LaTeX document that is produced by project.py and stored in git for reuse later.

report_for_my_project.pdf

PDF file created for project.tex stored in git for convenience

report_for_my_project.md

Markdown formatted output for your

utils/utils.py

File where functions that are shared among multiple experiment scripts can be stored. All of the .markdown and .pdf print things live here.

utils/latex_header.tex

Header for your latex document -- preconfigured with everything you need (and way more...)

img/

Directory where output images will be stored

img/My_Plot.png

The Image file produced by our particular block of code.

data/

Directory where output data will be stored -- you can change this to a location outside of the repo if you'll be producing very large files.

data/My_Table.csv

The data file produced by our particular block of code.

About

Report Driven Template for experiments

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages