Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • wslda wslda
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wtools
  • wsldawslda
  • Wiki
  • Monitoring of conservation laws

Monitoring of conservation laws · Changes

Page history
Update Monitoring of conservation laws authored Apr 06, 2022 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Hide whitespace changes
Inline Side-by-side
Monitoring-of-conservation-laws.md
View page @ e7d216bf
......@@ -17,5 +17,26 @@ To avoid situations where the code uses computing resources for generating traje
# Nconservation_stop 10000 # Stop to monitor total particle number conservation at time*eF, default=1e12 (infinity)
# Nconservation_tol 0.05 # if |[N(t)-N(start_t)]/N(start_t)|>tol then the code will terminate, default=0.05
```
Note that the energy conservation checking is disabled by default while particle number conservation monitoring is activated. If the violation (measured as deviation from the initial value) is detected, the code terminates.
Note that the energy conservation checking is disabled by default while particle number conservation monitoring is activated. If the violation (measured as deviation from the initial value) is detected, the code terminates. The information will be displays in `stdout` file:
```
# SIMULATION INSTABILITY CRITERIA MET FOR PARTICLE NUMBER!!!
# INITIAL VALUE=19.000000, PRESENT VALUE=20.351277, RELATIVE CHANGE=0.07112 [> 0.050000]
# !!! BREAKING !!!
```
# Forcing checkpoint
If the checkpoint tag is selected
```bash
checkpoint 1 # do checkpoint at the end of the calculation?
```
then immediately after terminating the code, the checkpoint files will be created
```
# SIMULATION INSTABILITY CRITERIA MET FOR PARTICLE NUMBER!!!
# INITIAL VALUE=19.000000, PRESENT VALUE=20.351277, RELATIVE CHANGE=0.07112 [> 0.050000]
# !!! BREAKING !!!
# CHECKPOINT INFO: MODE=WRITE: DATA SIZE= 0.04 GB
# CHECKPOINT INFO: MPI_NP_PER_IO_GROUP=24.
# CHECKPOINT INFO: WRITE TIME= 0.07 sec
# CHECKPOINT INFO: WRITE SPEED= 0.525 GB/sec
# CREATING CHECK STAMP: `test_check.stamp`
```
\ No newline at end of file
Clone repository
  • API version
  • Automatic interpolations
  • Auxiliary tools
  • Browsing the code
  • Broyden algorithm
  • C and CUDA
  • Campaign of calculations
  • Checking correctness of settings
  • Chemical potentials control
  • Code & Results quality
  • Common failures of static codes
  • Common failures of time dependent codes
  • Computation domain
  • Configuring GPU machine
  • Constraining densities and potentials
View All Pages