Latexikztaudecaysignatures CMS wiki pages serve as a centralized knowledge hub for researchers working with quantum field theory calculations and collider phenomenology. These pages combine LaTeX code snippets, TikZ visualizations, and decay signature templates to streamline the documentation of complex particle decay processes.
The repository emphasizes reproducibility by linking annotated source code directly to published results, enabling rapid reuse across experiments and theoretical studies. Clear versioning and change logs help teams maintain consistency when updating model parameters or detector-level selections.
Decay Topology Annotations
Key Diagram Categories
Organized collections of TikZ-based diagrams clarify common decay chains encountered at hadron colliders, including cascade and resonant topologies.
| Signature ID | Decay Chain | Kinematic Region | Associated Wiki Page |
|---|---|---|---|
| LZTS-001 | H → bb+WW | High-pT, resolved | /wiki/Higgs_to_bbWW |
| LZTS-007 | Σ → π+π0 n | Intermediate mass | /wiki/Sigma_to_pipin |
| LZTS-014 | X → μ+μ + invisible | Low multiplicity | /wiki/X_to mumu_MET |
| LZTS-023 | t → q q′ W | Top tagging | /wiki/Top_tagging_template |
Integrating TikZ Visualizations
From Source Code to Diagrams
Each signature page embeds compilable TikZ code so authors can reproduce and adapt Feynman diagrams without external drawing tools. Standardized node placement rules reduce visual clutter when multiple jets and leptons appear in the same event.
Version-controlled snippets are stored in the wiki repository, enabling reviewers to compare minor revisions and ensure that line styles, labels, and color schemes remain consistent across related plots.
Collaboration and Naming Conventions
Team Workflow Guidelines
Contributors follow a shared template that separates kinematic definitions from drawing commands, which simplifies reuse in both publication figures and internal slides. Page titles and file names encode process information so searches return correct matches quickly.
Minimal redundancy is maintained by referencing common subdiagrams from a shared macro library, while each unique channel retains its own dedicated wiki entry with full context and usage notes.
Validation and Testing Strategies
Ensuring Diagram Accuracy
Automated checks compare rendered TikZ output against reference plots generated from validated Monte Carlo samples, catching mismatches in branching ratios or kinematic boundaries early in the workflow.
Cross-checks between independent implementations of the same decay chain help identify subtle typos in vertex labels or arrow directions that are otherwise easy to overlook during manual review.
Best Practices for Maintaining Latexikztaudecaysignatures CMS wiki
- Store TikZ macros in the shared library to avoid duplication across pages.
- Keep kinematic labels aligned with official experiment naming schemes.
- Run compilation checks before uploading updated diagrams.
- Link each signature page to relevant validation plots and reference cards.
- Document assumptions about branching fractions and selection efficiencies.
FAQ
Reader questions
How do I locate the correct signature page for a specific decay mode?
Use the search box on the main wiki index and combine process keywords with detector-level terms, such as “leptonic tau decay signatures CMS”, to narrow results quickly.
Can I edit the TikZ code directly on the wiki page?
Inline editing is restricted to protect stability; instead open the version-controlled source file from the repository, make changes in a local or cloud sandbox, then submit a pull request for review.
What should I do if my decay chain involves overlapping resonances not covered by existing templates?
Create a new signature page using the nearest matching template as a base, document the resonance parameters clearly, and link to any relevant analysis notes that justify the modeling choices.
How are changes to decay signature diagrams tracked over time?
Each wiki page maintains a revision history with timestamps and contributor names, and significant updates trigger a short changelog entry summarizing modifications to diagrams or associated metadata.