Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #204

Closed
Open
Opened Jul 31, 2020 by Lukas Riedel@lriedelOwner

endOfTransportStep output policy leads to desynchronization of models if executed in parallel

Summary

When selecting transport.output.policy = endOfTransportStep, and running the application in parallel, the models desynchronize. The transport model may then take time steps which advance further than the Richards model.

Steps to reproduce

  1. Model settings: simulation.mode = richards+transport, transport.output.policy = endOfTransportStep
  2. Run in parallel: dorie run -p 2 config.ini

What is the current bug behaviour?

Transport model advances further in time than Richards model if it outputs every time step and the simulation is run in parallel.

What is the expected correct behaviour?

Transport model never advances further in time than Richards model.

Relevant logs, screenshots, files...?

Will be supplied later

Reproducing input

Input data
Simulation Case Description goes here
PFG config file if any
Grid mapping file if any
GMSH grid file if any
Boundary Condition file
Parameterization file
Run config file

Ideas how to fix this?

Check how write_data() method or endOfTransportStep output policy of transport model mess with time.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#204