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 59
    • Issues 59
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • 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
  • #699

Closed
Open
Created Dec 13, 2021 by ext-calvo_p@ext-calvo_pDeveloper

Redefine heavy ion beams

The following discussion from !548 (merged) should be addressed:

  • @snuverink_j started a discussion: (+9 comments)

    Is there maybe a reference why we use these particle charges for Xenon and Uranium? I think it would be good to add this here.

Beam particle definition for heavy ions is not well determined. Uranium and xenon beams can have different ionization states, but currently OPAL only considers a given charge state. The definition of these particles must be reviewed, establishing univocal values for the mass and the charge states as PARTICLE types in the BEAM command. If any user wants to simulate these type of ions with a different ionization state or other isotope kind, it can be done by means of the attributes MASS and CHARGE. In addition, the documentation in the Manual must be modified (see OPAL/documentation/manual#70 (closed)).

Edited Jan 10, 2022 by ext-calvo_p
Assignee
Assign to
2022.1
Milestone
2022.1 (Past due)
Assign milestone
Time tracking