Skip to content

Workflow

This document describes the current workflow for working in the helmholtz-juniors organization on github.

Plots

Overview of plots: https://notes.desy.de/s/X42lW1ct-

Tasks

  • all currently available tasks can be found in the Project 'Survey'
  • go to this project and pick a task from the 'Ready' column
    • if you are interested in the conceptional side of things and want to work on getting tasks ready for assignment, get in touch with Carolyn Guthoff (there might be no availability for this, but it's still good to know)
  • assign yourself to this task (please only assign yourself to one task at a time)
  • once you've started working on the task, move it to the column 'In progress'
    • check out the 'How to Commit' section in the README.md file in survey-framework (it is important that you follow the how to commit-workflow, because due to this being a private project, github doesn't automatically enforce the rules)
    • remember to write loads of comments in your code, so others can easily understand what is happening
  • after you've finished the task, move it to the column 'Review' and assign two of the following three for review on the task (Florian Hantke, Keno Hassler, Carolyn Guthoff)

Helpful notes

Writing Code

  • In general, it is important to write code as reusable as possible. For the survey framework this means, that no hard coded references should be included except for testing purposes where functions are tested with real data.
  • If you want some references, look in plotting/barplots.py, plotting/helper_barplots.py for the functions and in testing/test_A.py and testing/test_E.py for examples.
  • We can recommend using Jupiter Notebooks for testing initially how things work and how to best handle the data. However, it is strictly forbidden to commit Jupyter Notebooks to the github project. These files are however useful to write documentations. Just remember, to use dummy data for any figures to not leak any confidentail data.

Documentation

  • Write adaquate documentations in the documentation folder on how to use the code you wrote. Once there's an example available, we'll link it here :)