SiWECAL-TB-monitoring

Event-based almost-online monitoring for the SiW ECAL. To get started, check out the tutorial.

Submodules

The monitoring procedure interacts closely with code from the SiWECAL-TB-analysis repository. In many places (conversion, event building) will directly call the analysis code. Therefore each commit in the monitoring repository can only be expected to work with a specific commit from the analysis repository. This relationship is represented by tracking the analysis repository as a git submodule.

The TLDR for using a repository with submodules:

• Download the repository into monitoring

  git clone git@github.com:SiWECAL-TestBeam/SiWECAL-TB-monitoring.git --recurse-submodules  --shallow-submodules monitoring

• Get the submodules after having cloned without --recurse-submodules

  git submodule update --init --recursive

• Get upstream changes

  git pull --recurse-submodules

  • This will give you the newest version of monitoring. If (and only if) the monitoring is now based on a newer version of its submodules (SiWECAL-TB-analysis), the submodules will be updated to that commit.

• For developers: Get the newest version of the submodules

  git submodule update --remote --recursive

  • Do this if you want to adapt the monitoring for working with a newer version of the analysis repository.
  • Temporary note: Warning: As I am currently the only active developer, I found it simpler to track my fork as a submodule (see .gitmodules). Thus submodule update will go to this fork's last commit, which might be different from upstream.

For more information on git submodules we recommended the submodules chapter of the Git Pro book.

Useful web links

• ROOT docs for Draw()
• Python logging and multiprocessing
• ROOT example workflow with Chain and Draw
• emojis (only use 1-codepoint ones though)