Skip to content

GitLab

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

Closed
Open
Opened Mar 19, 2018 by baumgarten@baumgarten
  • Report abuse
  • New issue
Report abuse New issue

Phase output in OPAL-Cycl

The output of the phases in a multiprocessor run involving N nodes is not reliable.

a) if you run the simulation with one core you get all the information about the phases.

b) with more than one core the situation is different: because we sample this information always at the same particle (the one with ID==0) and only node==0 is writing, you only see phase information iff particle with ID==0 is on node 0.

Edited Mar 19, 2018 by snuverink_j
To upload designs, you'll need to enable LFS. More information

Linked issues

Assignee
Assign to
OPAL 1.6.1
Milestone
OPAL 1.6.1
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: OPAL/src#213