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
  • Units

Units · Changes

Page history
Update Units authored Feb 25, 2022 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Show whitespace changes
Inline Side-by-side
Units.md
View page @ 732f3268
......@@ -11,7 +11,7 @@ The lattice spacing is defined through [predefines.h](https://gitlab.fizyka.pw.e
```c
#define DX 1.0
```
It is *recommended* to work with lattice spacing `DX=1`, however, the code allows to use of other values, in order to support the functionality of [automatic interpolations](Automatic interpolations).
It is *recommended* to work with lattice spacing `DX=1`, however, the code allows to use of other values, in order to support the functionality of [automatic interpolations](Automatic interpolations). Through the lattice spacing, the standard of the code length unit is defined.
# Dimensionless units
When reporting values, it is convenient to use dimensionless units. See here for the [definition of reference scales](Reference scales).
......@@ -26,10 +26,10 @@ To compare with experimental data typically one needs to convert results to SI u
|standard | standard type| SI | code |
| -------| ---- | ----- | -----|
|mass | explicit: mass of particle | $`m\,\left[\textrm{kg}\right]`$ | 1 |
| length | explicit: distance between two lattice points | $`l\,\left[\textrm{m}\right]`$ | 1 (*)|
| length | explicit: via lattice spacing | $`l\,\left[\textrm{m}\right]`$ | 1 (*)|
| time | implicit: time units is defined through requirement that $`\hbar=1`$ | $`\left[\textrm{s}\right]`$ | 1 |
(*) It is assumed that in [predefines.h](https://gitlab.fizyka.pw.edu.pl/wtools/wslda/-/blob/public/st-project-template/predefines.h) `DX=1`. If not, and `DX=a`, one needs to rescale $`l\rightarrow l/a`$.
(*) The lattice spacing defines how the distance between two lattice points relates to the unit of length in which the code operates. If `DX=1` then the lattice spacing itself serves as the standard for the code unit length.
Below we provide conversion factors:
......
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