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
  • #294

Closed
Open
Created Apr 03, 2019 by snuverink_j@snuverink_jDeveloper

ParallelCyclotronTracker crashes (in single particle?) mode when all particles are lost

I noticed that in single particle mode (might not be related) that if all particles (in this case on a stripper) are lost OPAL crashes:

OPAL> At step 25071, lost 1 particles on stripper, collimator, septum, or out of cyclotron aperture
Error> 
Error> *** User error detected by function "boundp() "
Error>     h<0, can not build a mesh
Error>     h<0, can not build a mesh
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD 
with errorcode -100.

In ParallelCyclotronTracker::deleteParticle() there needs to be a check after the particles are removed if there are any particles left and early return before the boundp() call.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking