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
  • Checking correctness of settings

Last edited by Gabriel Wlazłowski May 22, 2021
Page history
This is an old version of this page. You can view the most recent version or browse the history.

Checking correctness of settings

In many cases, before submission of computation to hpc queue system, we would like to check the correctness of various settings to minimize the risk of job failure. W-SLDA Toolkit provides a set of tools that can be used for testing the settings. To build these tools, execute in your project folder:

make tools

The command will generate the following tools:

tool name scope description execution
solve-uniform st,td The code solves uniform problem according settings provided in the input file. ./solve-uniform input.txt
test-external-potentials st The code evaluates external potentials according problem-definition.h file and saves them to W-DATA format. Next, the potentials can be inspected by VisIt. ./test-external-potentials input.txt

The tools are not computationally intensive. You can execute them from login code.

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