Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • S sim_runner
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cta-unige
  • sim_runner
  • Merge requests
  • !9

Feature, config files launcher file for testing

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Luis David Medina Miranda requested to merge feature/test-config-launcher-files into master Jun 30, 2020
  • Overview 5
  • Commits 3
  • Pipelines 2
  • Changes 5

Description

The physics-wise configuration files for launching the sim_runner are added. 2 files to run and determine the safe threshold : prod_nsb_rate_scan.toml and prod_proton_rate_scan.toml Once the safe threshold is determine, a production of diffuse gamma, gamma, and protons should be done using : prod_gamma_diffuse.toml, prod_gamma.toml, and prod_proton.toml

Related Issue

Related to issue #4 (closed)

How Has This Been Tested?

Testing will come in a later integration once the runner is operational for testing

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
Edited Jun 30, 2020 by Luis David Medina Miranda
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/test-config-launcher-files