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 61
    • Issues 61
    • 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
  • #31

Closed
Open
Created Feb 09, 2017 by Valeria Rizzoglio@rizzoglio_v

OPAL-T: missing particles stored in the monitor

I am running the following simulation (input file attached):

Beam: 250 MeV proton beam degraded to 230 MeV due to interaction with graphite

Last part of the beamline without CollimatorPhysics

KMA8: ECOLLIMATOR, XSIZE=0.007, YSIZE=0.007, L=0.075, ZSIZE=0.075, ELEMEDGE=19.004;
MMAP25X: MONITOR, OUTFN="MMAP25X.h5", ELEMEDGE=30.3;

The simulation ends ZSTOP = 34.4 m so there are 4 m of drift space (no losses) between the monitor MMAP25X and the end of the simulation.

The longitudinal beam extension is 0.5 m: the entire beam crosses the monitor. In this case the number of particles recorded by the monitor MMAP25X agrees with the protons stored at the end of the simulation.

If I apply the CollimatorPhysics on KMA8,

CopperCol:  SURFACEPHYSICS, TYPE="COLLIMATOR", MATERIAL="Copper";
KMA8: ECOLLIMATOR, XSIZE=0.007, YSIZE=0.007, L=0.075, ZSIZE=0.075, SURFACEPHYSICS=CopperCol, ELEMEDGE=19.004;

then the longitudinal beam extension increases to 2 m due to the scattering effect. Even in this case, the entire beam should cross the monitor, however the number of protons recorded by the monitor is less than the final number of particles:

Protons at MMAP25X: 9312

Protons at the last step: 9988

Collimator does not go Offline

The situation does not change moving the monitor closer to the collimator (= increasing the distance between the monitor and ZSTOP)

OPAL Version: "old " OPAL binary from Uldis (/home/scratch/locans/install/opal-dks-1.5/src/)

OPAL> This is OPAL (Object Oriented Parallel Accelerator Library) Version 1.5.00.1
OPAL> OPAL compiled with DKS (Dynamic Kernel Scheduler) Version 1.0.2

at the moment this is the only binary I can use that runs the CollimatorPhysics multi-cores and writes the monitor files (issue #29 (closed)).

PROSCAN-G3-LA1-LD-230.in

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking