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
  • Custom SLDAE functional

Custom SLDAE functional · Changes

Page history
Update Custom SLDAE functional authored Apr 04, 2022 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Hide whitespace changes
Inline Side-by-side
Custom-SLDAE-functional.md
View page @ ff47ab9d
TODO
\ No newline at end of file
# Introduction
Within W-SLDA Toolkit we provide a script for generating custom SLDA functional: `extensions/sldae/sldae-dev-tool.c`
Within the script user can provide its own formulas for:
```c
double ground_state_energy (int dn, double _x, int id []);
double chemical_potential (int dn, double _x, int id []);
double inverse_effective_mass (int dn, double _x, int id []);
double pairing_gap (int dn, double _x, int id []);
```
In return, the script generates a source file readable by W-SLDA Engine. Once the functional is created, it becomes available for all code within the toolkit.
# Example: SLDAE with the effective mass equal 1
The function for the computation of the effective mass has been modified to:
```c
double
inverse_effective_mass (int dn, double _x, int id [])
{
int ip0 [1] = {0}; double x0 = xm (dn, _x, ip0);
// ...
return x0;
}
```
Next, the code is compiled and executed:
```bash
[gabrielw@dell sldae]$ gcc sldae-dev-tool.c -lm -lgsl -lgslcblas -o sldae-dev-tool
[gabrielw@dell sldae]$ ./sldae-dev-tool
SLDAE DEV TOOLS
[padé[4/4] interpolation of sldae parameters p = {beta, gamma, B, C}]
p a1 x + a2 x^2 + a3 x^3 + c x^4
----- = ----------------------------------
p_ufg 1 + b1 x + b2 x^2 + b3 x^3 + c x^4
beta interpolation (beta_ufg = -0.481506)
iter = 46 f(x) = 1.110e-16
a1 = +0.797400;
a2 = +0.943961;
a3 = +1.037043;
b1 = +1.227062;
b2 = +2.126210;
b3 = +1.734795;
c = +0.523445;
b_functional interpolation (b_functional_ufg = -0.481506)
iter = 13 f(x) = 8.882e-16
a1 = +0.698112;
a2 = +0.034678;
a3 = +0.455138;
b1 = +0.353905;
b2 = +0.806444;
b3 = +0.403679;
c = -0.031327;
inverse_gamma interpolation (inverse_gamma_ufg = -0.094945)
iter = 14 f(x) = 1.821e-14
a1 = +2.713374;
a2 = +1.441196;
a3 = +3.700251;
b1 = +0.634303;
b2 = +3.522427;
b3 = +3.701347;
c = +1.877961;
c_functional interpolation (c_functional_ufg = -10.532397)
iter = 19 f(x) = 3.664e-15
a1 = +0.370145;
a2 = +1.041299;
a3 = +1.737347;
b1 = +2.458364;
b2 = +5.604947;
b3 = +3.828124;
c = +1.085400;
Parameters written to: sldae_parameters.h
Creating file: sldae_parameters.txt
```
Once the functional is generated user should inspect content of file `sldae_parameters.txt`. It contains following columns:
``` bash
# 1: lambda=a*k_F
# 2: ground_state_energy
# 3: inverse_effective_mass
# 4: chemical_potential
# 5: pairing_gap
# 6: beta_parameter
# 7: beta_parameter - PADE
# 8: b_functional
# 9: b_functional - PADE
#10: inverse_gamma_parameter
#11: inverse_gamma_parameter - PADE
#12: c_functional
#13: c_functional - PADE
```
In particular, it is important to confirm that PADE approximants correctly reproduce functions generated by analytical formulas. Note that W-SLDA Engine uses Pade approximants to deliver the highest performance.
```bash
[gabrielw@dell sldae]$ gnuplot
gnuplot> plot "sldae_parameters.txt" u 1:6 w l, "" u 1:7 w l
# and similar for other functions
```
![image](uploads/1a057ed2aaa2adf039c3656e0c90e9b2/image.png)
Finally, file `sldae_parameters.h` should be moved to folder `hpc-engine`. From now new SLDAE functional will be used when `FUNCTIONAL=SLDAE` is selected in predefines.
# Collection of own SLDAE-like functionals
The information about PADE approximants for functional coefficients loded to the engine through the file `hpc-engine\sldae_functional.h`, precisely:
```c
// Select coefficients
#ifdef SLDAE_FORCE_A1
#include "sldae_parameters_A1.h"
#else
// default one
#include "sldae_parameters.h"
#endif
```
User can modify this section to form that uploads a correct file with the desired set of coefficients.
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