Working together

Collaboration

GUNDAM connects software development, statistical methodology, and experimental analysis across the neutrino community.

Mission

Shared methods for better analyses

The collaboration develops and maintains a flexible analysis framework that can serve multiple experiments and physics goals. Its central aim is to make generic fitting, uncertainty, and validation work reusable, reviewable, and reproducible.

Participation

Ways to take part

Users

Apply released GUNDAM software and documentation to scientific or technical analysis work.

Contributors

Improve code, documentation, tutorials, tests, validation material, or community support.

Collaborators

Participate in the sustained scientific, technical, and organizational work of the collaboration.

Reviewers

Help verify proposed changes, physics behavior, interfaces, documentation, and reproducibility.

Contributors

Recognizing project work

Contribution is broader than committing source code. Documentation, issue triage, validation studies, release testing, training material, design review, and user support all strengthen the project.

View GitHub contributors

Development Policy

Small branches, focused changes

  • main is the official development head.
  • Development occurs in a dedicated branch with a descriptive name.
  • Use prefixes such as fix/, feature/, doc/, or experimental/ to communicate intent.
  • Keep feature and fix branches short-lived and limited to one coherent change.
  • Reference the related issue in the pull request and require continuous-integration checks to pass before merging.

Governance

Transparent technical decisions

Project decisions should be recorded in durable collaboration channels, with software changes represented by issues, pull requests, reviews, and release notes. Formal governance and collaboration-policy documents can be linked from this section as they are approved.

Get Involved

Begin with the public project

  1. Read the user documentation.
    Understand the supported workflow and current configuration model.
  2. Try an official example.
    Reproduce a known result before adapting the framework.
  3. Open a focused issue.
    Describe the use case, evidence, expected behavior, and environment.
  4. Propose a reviewed change.
    Include tests, validation, and documentation appropriate to the impact.
Open GUNDAM on GitHub