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
  • Common failures of static codes

Common failures of static codes · Changes

Page history
Update Common failures of static codes authored Dec 17, 2020 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Hide whitespace changes
Inline Side-by-side
Common-failures-of-static-codes.md
View page @ 10128af9
......@@ -24,9 +24,21 @@
[node2067:27224] [ 1] /usr/local/elpa202005-openmpi311-gcc721-cuda90-lapack391/lib/libelpa.so.15(__elpa1_compute_MOD_tridiag_complex_double+0x96c)[0x7fd935f30edc]
[node2067:27224] [ 2] /usr/local/elpa202005-openmpi311-gcc721-cuda90-lapack391/lib/libelpa.so.15(__elpa1_impl_MOD_elpa_solve_evp_complex_1stage_double_impl+0x79d)[0x7fd935f958bd]
```
Segmentation fault is typical error generated by diagonalization routines if there is insufficient amount of memory. In the example above calculations were executed with `p=1` and `q=1` parameters. In this case it was sufficient to set in *input* file
Segmentation fault is a typical error generated by diagonalization routines if there is insufficient amount of memory. In the example above calculations were executed with `p=1` and `q=1` parameters. In this case, it was sufficient to set in *input* file
```
p 2
q 2
```
to solve the problem. For more info see [Memory usage of st-wslda](Memory usage of st-wslda).
\ No newline at end of file
to solve the problem. For more info see [Memory usage of st-wslda](Memory usage of st-wslda).
## Segmentation fault & ScaLAPACK
```
# LATTICE: 128 x 128 x 32
# USING SCALAPACK WITH PZHEEVR.
...
# DIAGONALIZATION 0 15...
srun: error: nid00111: tasks 0-17: Segmentation fault
srun: Terminating job step 512966.0
slurmstepd: error: *** STEP 512966.0 ON nid00111 CANCELLED AT 2020-06-25T17:02:46 ***
```
It is again error related to insufficient memory, see *Segmentation fault & ELPA*.
\ 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