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

Closed
Open
Created Jun 16, 2017 by frey_m@frey_mMaintainer

ParallelCyclotronTracker::applyPluginElements

In ParallelCyclotronTracker the particles are mapped several times from local to global coordinates and vice versa. The PartBunch::boundp() operation where the particles are redistributed among the cores is always performed in local coordinates except in during the function call ParallelCyclotronTracker::applyPluginElements in case the boolean flag_stripper being true (line 3389 ff.).

if(((*sindex)->first) == ElementBase::STRIPPER)    {
            bool flag_stripper = (static_cast<Stripper *>(((*sindex)->second).second))
                -> checkStripper(itsBunch, turnnumber_m, itsBunch->getT() * 1e9, dt);
            if(flag_stripper) {
                itsBunch->boundp();
                *gmsg << "* Total number of particles after stripping = " << itsBunch->getTotalNum() << endl;
            }
        }

The workflow of ParallelCyclotronTracker::Tracker_Generic()

...
ParallelCyclotronTracker::initDistInGlobalFrame(); // (line 1235) --> particle in global coordinates
ParallelCyclotronTracker::applyPluginElements(dt); // (line 1285) --> PartBunch::boundp() in global coordinates !!!
...
// start tracking

Shouldn't the PartBunch::bounp() operation always be performed in local coordinates?

Best, Matthias

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking