Skip to content

Commit 141b931

Browse files
authored
Merge pull request #66 from su2code/UpdateDocRestart
Update Restart-File.md
2 parents 43a5aa3 + b1d9607 commit 141b931

File tree

1 file changed

+36
-2
lines changed

1 file changed

+36
-2
lines changed

_docs_v7/Restart-File.md

Lines changed: 36 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,9 +3,43 @@ title: Restart File
33
permalink: /docs_v7/Restart-File/
44
---
55

6+
7+
## Saving files for restarts or adjoint runs
8+
69
The SU2 binary restart format has the extension `.dat`, but it is also possible to write out restart files in a simple ASCII file format with extension `.csv`. Have a look at the [Output section](/docs_v7/Custom-Output/) to learn how to change output file formats.
710

8-
The restart files are used to restart the code from a previous solution and also to run the adjoint simulations, which require a flow solution as input. In order to run an adjoint simulation, the user must first change the name of the `restart_flow.dat` file (or `restart_flow.csv` if ASCII format) to `solution_flow.dat` (or `solution_flow.csv`) in the execution directory (these default file names can be adjusted in the config file). It is important to note that the adjoint solver will create a different adjoint restart file for each objective function, e.g. `restart_adj_cd.dat`.
11+
The restart files are used to restart the code from a previous solution and also to run the adjoint simulations, which require a flow solution as input. To save a restart file, the user needs to add the option `RESTART` to the keyword `OUTPUT_FILES`:
12+
13+
`OUTPUT_FILES= RESTART`
14+
15+
A restart file with the name given by the keyword `RESTART_FILENAME` is then saved at the end of the simulation, or after every number of iterations given by the keyword `OUTPUT_WRT_FREQ`. For instance,
16+
17+
`RESTART_FILENAME= restart_flow` \
18+
`OUTPUT_WRT_FREQ= 100`
19+
20+
will write the the file restart_flow.dat every 100 iterations when then the total number of iterations is larger than 100, or only once at the end of the simulation when the total number of iterations is smaller than 100. Note that the file extension (the suffix) is automatic and can be left out.
21+
If you would like to keep copies of previously saved restart files, this is possible by setting
922

10-
To restart a simulation the `RESTART_SOL` flag should be set to `YES` in the configuration file. If performing an unsteady restart the `RESTART_ITER` needs to be set to the iteration number which you want to restart from. For instance if we want to restart at iteration 100 and run the unsteady solver with 2nd-order dual time stepping method, we will need to specify `RESTART_ITER = 100` and have the restart files `solution_flow_00098.dat` and `solution_flow_00099.dat`.
23+
`WRT_RESTART_OVERWRITE= NO`
24+
25+
This option is available only for steady simulations. In unsteady simulations, the number of timesteps is appended to the filename automatically. Additional to the regular restart file, a restart file with the current iteration appended to the filename will be written every `OUTPUT_WRT_FREQ` iterations.
26+
27+
## Starting a simulation from a saved solution
28+
29+
When restarting the primal or starting an adjoint, the filename given by the keyword `SOLUTION_FILENAME` will be used. In order to restart the primal or start the run of an adjoint simulation, the user must therefore first change the name of the saved file, e.g. `restart_flow.dat` (or `restart_flow.csv` if ASCII format) to the filename `solution_flow.dat` (or `solution_flow.csv`) in the execution directory. It is important to note that the adjoint solver will create a different adjoint restart file for each objective function, e.g. `restart_adj_cd.dat`.
30+
To restart a simulation the `RESTART_SOL` flag should be set to `YES` in the configuration file.
31+
32+
`RESTART_SOL= YES` \
33+
`SOLUTION_FILENAME= solution_flow`
34+
35+
If performing an unsteady restart the `RESTART_ITER` needs to be set to the iteration number which you want to restart from. For instance if we want to restart at iteration 100 and run the unsteady solver with 2nd-order dual time stepping method, we will need to specify `RESTART_ITER = 100` and have the restart files `solution_flow_00098.dat` and `solution_flow_00099.dat`.
36+
1137

38+
| Option value | Default value | Description | Data type |
39+
|---|---|---|---|
40+
| `RESTART_FILENAME` | restart.dat | filename under which the restart file will be saved | string |
41+
| `OUTPUT_WRT_FREQ` | 250 | the frequency with which the output files will be saved | integer |
42+
| `WRT_RESTART_OVERWRITE` | YES | overwrite the restart file or (additionally) append the iteration number to the filename | boolean |
43+
| `RESTART_SOL` | solution | restart from file or from initial conditions | boolean |
44+
| `SOLUTION_FILENAME` | solution.dat | filename that will be used to restart the primal or start the adjoint computation | string |
45+
| `RESTART_ITER` | 1 | iteration number that an unsteady simulation will restart from | integer |

0 commit comments

Comments
 (0)