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
  • Auxiliary tools

Auxiliary tools · Changes

Page history
Update Auxiliary tools authored May 21, 2021 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Hide whitespace changes
Inline Side-by-side
Auxiliary-tools.md
View page @ 4da4e300
W-SLDA Toolkit provide various tools that may support computation and data analysis process.
W-SLDA Toolkit provides various tools that may support the computation and data analysis process.
In order to create them enter [tools](https://gitlab.fizyka.pw.edu.pl/wtools/wslda/-/tree/public/tools) folder and edit (if necessary) header of [Makefile](https://gitlab.fizyka.pw.edu.pl/wtools/wslda/-/blob/public/tools/Makefile). Next execute
```bash
make
......@@ -10,12 +10,16 @@ Executables will be written to `wslda/tools/bin` folder.
## wdata-cut
*Purpose*: extracts subset from existing wdata set.
In many cases for testing purposes it is sufficient to have only sample of data (for example to download it locally and test a code). You can use `wdata-cut` tool exatract a data sample. Syntax is following:
In many cases, for testing purposes, it is sufficient to have only a sample of data (for example to download it locally and test a code). You can use `wdata-cut` tool to extract a data sample. The syntax is following:
```bash
WDATA SUBSET EXTRACTOR
Usage: ./wdata-cut file.wtxt outprefix start stop
or
Usage: ./wdata-cut file.wtxt outprefix start stop stride
file.wtxt - metadata file
outprefix - for new files, metadata file will be written to outprefix.wtxt
[start,stop) - range for subtructing cycles
stride - every `stride` frame will be taken only from given range, default stride=1
```
For example to extract the first cycle only:
```bash
......@@ -29,9 +33,9 @@ DONE.
```
## wdata-sample
*Purpose*: creates new data set, where only every `stride` measurment is present.
*Purpose*: creates new data set, where only every `stride` measurement is present.
This tool is very similar to `wdata-cut` tool with change that it strides the data set. Syntax is following:
This tool is very similar to `wdata-cut` tool with change that it strides the data set. The syntax is following:
```bash
Usage: wdata-sample file.wtxt outprefix stride
file.wtxt - metadata file
......@@ -87,6 +91,13 @@ const eF 0.72
GENERATED `ufg1V0.6.wtxt`
```
## dpca2wdata-hard
*Purpose*: converts dpca file into wdata set.
```
DPCA -> WDATA HARD CONVERTER
Usage: ./dpca2wdata-hard prefix
prefix - prefix of dpca files
```
# st-wslda related tools
## wdata2checkpoint
......
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