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

Closed
Open
Created Jul 06, 2021 by albajacas_a@albajacas_aDeveloper

Different initial distribution with same input file

Summary

When running regression tests multiple times, some parameters of the initial distribution are different at each run, even though SEED is the default. Initial differences are small, but they diverge with time and can yield larger-than-machine-precision errors in the final time-step, which makes it harder to reproduce results and run regression tests (e.g. see #658 (closed)).

Steps to reproduce

By running the regression test Distribution-Gauss-1.in several times one can see that the initial bunch is not the same at each run (see image below).

However, this only happens when I run the tests on 4 cores. When running the test on 1 or 2 cores the initial distribution is the same at every run. So I suspect that this might be due to differences in timing of communication between processors.

Comparison of the initial bunch between three runs on 4 cores: comparison

Edited Jul 06, 2021 by albajacas_a
Assignee
Assign to
2022.1
Milestone
2022.1 (Past due)
Assign milestone
Time tracking