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
  • User defined parameters

User defined parameters · Changes

Page history
Update User defined parameters authored Mar 09, 2023 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Hide whitespace changes
Inline Side-by-side
User-defined-parameters.md
View page @ d30661cc
......@@ -3,20 +3,21 @@
The W-SLDA toolkit provides a framework for creating flexible parametrization of formulas. The list of numbers (of double type) that can be passed from an input file to the code is called *custom parameters*. In the input file they start with the tag:
```bash
# Custom parameters
params0 0.0 # value of the parameter
params1 1.0 # value of the parameter
params2 2.0 # value of the parameter
params0 0.0 # value of the params[0], simple syntax
params[1] 1.0 # value of the params[1], alternative syntax
params[2] = 2.0; # value of the params[2] in C style
# ... and so on ...
# ... if you need pass string parameter...
strings0 aaa
strings1 bbb
strings0 aaa # accessible via (global) variable strings[0]
strings[1] aaa # accessible via (global) variable strings[1]
strings[2] = "ccc"; # (global) variable strings[2], C style
```
Maximal number of parameters is specified in `predefines.h` by macro-variable:
The maximal number of parameters is specified in `predefines.h` by macro-variable:
```c
// Maximal number of parameters in params array
#define MAX_USER_PARAMS 32
```
When the program reads the input file custom parameters are uploaded into `params` array in a such way that *paramsk* is assigned to `params[k]`. Pointer to the array is passed to each user-defined function, for example:
When the program reads the input file, custom parameters are uploaded into `params` array in a such way that *paramsk* is assigned to `params[k]`. The pointer to the array is passed to each user-defined function, for example:
```c
double v_ext(int ix, int iy, int iz, int it, int spin, double *params, size_t extra_data_size, void *extra_data)
{
......@@ -27,12 +28,12 @@ double v_ext(int ix, int iy, int iz, int it, int spin, double *params, size_t ex
}
```
During the self-iteration process, before `params` array is passed to user-defined functions the array can be processed by function:
During the self-iteration process, before `params` array is passed to user-defined functions the array can be processed by the function:
```c
/**
* THIS FUNCTION IS CALLED DURING THE SELF-CONSISTENT PROCESS.
* After loading params array from input file, the parameters are processed by this routine.
* The routine is executed at beginning of each iteration.
* The routine is executed at the beginning of each iteration.
* @param params array of size MAX_USER_PARAMS with parameters from input file.
* @param kF typical Fermi momentum scale of the problem.
* kF=referencekF if the referencekF tag is indicated in the input 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