Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 62
    • Issues 62
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #683

Closed
Open
Created Sep 30, 2021 by ext-calvo_p@ext-calvo_pDeveloper

Variables of incident particles in OPAL-t elements

Position and time variables of incident particles in OPAL-t elements must be adjusted to correspond to the physical boundary of the element.

There are different ways of saving the particles according to each element: MONITOR implementation is correct, FLEXIBLECOLLIMATOR records one step after the element input, DEGRADER currently do not save incident particles.

All elements should have the same structure to store the incident particles in the output file.

Assignee
Assign to
2022.1
Milestone
2022.1 (Past due)
Assign milestone
Time tracking