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
  • Output files

Output files · Changes

Page history
Create Output files authored Dec 28, 2020 by Gabriel Wlazłowski's avatar Gabriel Wlazłowski
Show whitespace changes
Inline Side-by-side
Output-files.md 0 → 100644
View page @ 3c307352
# Copying results to a new location
If you want to copy results to a new location it is sufficient to execute
```bash
cp outprefix* new-location
```
where `outprefix` stands for string provided in input file.
*NOTE*: this command most likely will display a warning:
```
cp: -r not specified; omitting directory 'outprefix'
```
In the folder `outprefix` the code stores checkpoint files and wave-functions.
Since it contains a lot of data (in many cases measured in TB) by default we skip copy of it.
If you want to copy the complete dataset to new location (including checkpoint files, and wave-functions) you need to execute:
```bash
cp -r outprefix* new-location
```
# List of output files
| file name | content | comment|
| --------- | ------- | ------ |
|`outprefix`.wtxt| Metdata file of W-DATA format |It is `txt` file.<br> See for more [W-data format](W-data format)|
| `outprefix`_*variable*.wdat | Binary files with saved variables. | See for more [W-data format](W-data format) |
|`outprefix`.wlog| Log file |It is `txt` file.<br> See for more [Logger](Logger)|
|`outprefix`_check.stamp | File with control sums | It is `txt` |
|`outprefix`_input.txt | Copy of used input file | |
|`outprefix`_predefines.h | Copy of used for compilation `predefines.h` file | |
|`outprefix`_problem-definition.h | Copy of used for compilation `problem-definition.h` file | |
|`outprefix`_logger.h | Copy of used for compilation `logger.h` file | |
|`outprefix`/| Folder with checkpoint and wave-functions | This folder main contains a lot of data.<br> Its content depends on flags in input file. |
|`outprefix`/checkpoint.s*x*dpca| Binary file with checkpoint for `st` code. | *x* stands for the code dimensionality. The file is generated when `checkpoint 1`. This is the only file requested by the `st` code when starting with `inittype 5`. |
|`outprefix`/uniform.solution| Binary file with a solution for uniform system | File is generated only if `inittype 5` and `init0save 1`.|
|`outprefix`/s*x*dpca*|Binary files with wave-functions produced by `st` codes.| *x* stands for the code dimensionality. The files are generated only if `writewf 1`. |
|`outprefix`/checkpoint_*|Checkpoint files produced by `td` code | These are binary files with evolved wave-functions. They are generated when `checkpoint 1`. These files are requested by the `td` code when starting with `inittype 5`. |
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