forked from Schulik/aiolos
-
Notifications
You must be signed in to change notification settings - Fork 0
/
README.txt
219 lines (153 loc) · 9.07 KB
/
README.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
************************************
************************************
*** AIOLOS - A 1-D radiation hydrodynamics multi-species code
************************************
************************************
************************************
*** 0. Download and branches
************************************
In order to install and run Aiolos, we recommend the following steps:
1.) Clone this git repository (This presumably has just been done) via 'git clone https://github.com/Schulik/aiolos/'
The default version of the code, with which the tests in our documentation paper were performed (Schulik&Booth2023, hereafter SB23) is 'version0.2' (can also be found via the github tags),
as opposed to the main branch, on which active code development might be ongoing.
We recommend switching to this branch.
2.) Install the EIGEN library via https://eigen.tuxfamily.org
3.) Compile, details below
4.) Run, details below
************************************
*** 1. Compilation
************************************
aiolos can be compiled with make and gcc, just type 'make'.
If you wish to provide your own initial conditions or boundary conditions, add them to your own problem
file, e.g. "problems/my_problem.cpp". These can then be compiled into aiolos
via:
make PROBLEM=my_problem
* Fixed number of species
By default, aiolos is compiled in a flexible mode that can run problesm with any
number of input species. However, a significant (10-20%) speed up can be
realised if the number of species is set at compile time. This can be
done via:
make PROBLEM=my_problem NUM_SPECIES=4
where the "4" refers to a target of 4 species total.
A few warnings might occur concerning unused temporary variables. Those can be ignored.
************************************
*** 2. In order to execute Aiolos, type:
************************************
./aiolos -dir test_files/ -par planet_spherical.par -spc mix3.spc
with the *.par (parameter) and the *.spc (species) file present into the command line.
This is a simple hydrostatic test problem, i.e. the initial density profile that is constructed should be kept perfectly.
They command line does not require the species file to be added to it, it can be added to the parameter file instead.
Add into the parameter file
PARAMETER_FILE mix3.spc
then aiolos can be executed via
./aiolos -dir test_files/ -par planet_spherical.par
A simple static, radiative solution can be obtained via
./aiolos -dir runs_mdot_vs_euv_plot/ -par dynamic3_euv1e3_C_1s2b_rerun.par
And a simple hydrodynamic, radiative solution can be obtained (this will take longer to run) via
./aiolos -dir runs_mdot_vs_euv_plot/ -par dynamic3_euv1e3_C_1s2b_rerun.par
A simple isothermal wind solution (currently needs fixing):
./aiolos -dir test_files/ -par planet_wind.par -spc mix_wind.spc
_________________________________
# 2.1 Output files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
* Output and Diagnostic:
Output and diagnostic files give snapshots in time of the state of the simulation. Comparing subsequent outputs can inform about whether steady-state has been achieved.
They are numbered by integer numbers, and output files are specific to each species, but with a set number of columns.
Diagnostic files contain summary as well as detailed information about the radiation transport, opacities for all species, optical cell depths per band, etc. and they change their column numbers
depending on how many bands and species are set per simulation.
The cheat_sheet.ods contains information about what to find in individual columns.
* Monitor:
The monitor file can be used to check global mass, energy conservation etc. but is currently switched off.
* Execution log
The execution_log.txt logs all aiolos executions with their command line and timestamps in the folder of the executable.
This helps to keep track of what one was doing a few days or weeks ago, but just can't quite remember in which running directory.
************************************
## 3. Execution parameters
************************************
As outlined in SB23, the code solves various differential equations, corresponding to code modules.
Code modules are hydrodynamics, friction, (thermal) radiation transport and (photo)chemistry.
Add the following keywords into the parameter file (**no tabs, only whitespaces**) to activate the modules.
Some parameters are prefixed with "PARI_", this is a leftover from code development and does not signify anything special now.
Parameters can be added in any line.
_________________________________
# 3.0 Basic execution
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The simulation starts at t=0 and runs until tmax, specified via
PARI_TIME_TMAX 1e6
(where this simulation will run till 1e6 seconds)
Output and diagnostic files are produced every
PARI_TIME_OUTPUT 1.e6
simulated seconds.
If very fine output (e.g. every 1e-2 seconds) just before an interesting time point is desired, then the time offset can be set via
TIME_OUTPUT_OFFSET 0.9e6
the outputs will then proceed every PARI_TIME_OUTPUT seconds after the offset time.
_________________________________
3.1 Hydrodynamics module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DO_HYDRO 1
//options: 0: off, 1: on
//Off will allow to ignore the hydrodynamical CFL condition.
USE_TIDES 1
//options: 0: off, 1: use tidal field based on PARI_MSTAR and PARI_PLANET_DIST
_________________________________
3.2 Friction module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
FRICTION_SOLVER 2
//options: 0: off, 1: analytic implicit, 2: numeric implicit
PARI_COLL_MODEL P
//options: C: constant, P: physical
PARI_ALPHA_COLL 1e0
//If coll_modell==C, then this is the constant value
_________________________________
3.3 Radiation transport module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARI_USE_RADIATION 1
//options: 0: Off, 1: Full solver for coupled J_b and T_s variables. No limitation on the number of in or outgoing bands.
// 2: 'Fast' solver, limited to one outgoing radiation band, any number of instellation bands. Radiation and temperatures are solved in a decoupled manner.
NO_RAD_TRANS 1.
//options: multiplier value for thermal radiative losses. If 0, only nonthermal cooling is activated. If no nonthermal cooling functions are specified, then absorption will be balanced by adiabatic cooling, i.e. energy-limited escape.
PARI_OPACITY_MODEL P
//options:
/* U: User defined opacity. Go into user_opacity() and specify your custom algorithm.
* C: Constant opacities. Modifiers for solar, planck and rosseland opas exist individually.
* P: 'Physical': Constant with simple pressure-broadening parameterization powerlaw above 0.1 bars
* F: Freedman model. Only the fit for Rosseland opacities is currently included.
* M: Malygin2014 (Planck Rosseland Gas opa)/Semenov2003 (Planck Rosseland Dust opa) combined opacities. Solar opas taken from *opa files.
* D: Dust only model, given a certain dust size.
* T: Tabulated opacities. Takes p-T dependent solar, planck and rosseland data from *aiopa files.
* K: 'Kombined' opacities. Planck and Rosseland is p-T dependent from *aiopa data and solar are p-T-constant, but spectrally resolved from *opa files.
*/
Planetary core (internal) temperature boundary condition:
USE_PLANET_TEMPERATURE 1
T_INT 350.
MAX_TIMESTEP_CHANGE 1.01 //Not required, but radiative boundaries will produce results off by 50% of timesteps are too large.
//If hydro is used, timesteps are small enough by default and this option is not required.
_________________________________
3.4 (Photo) chemistry module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PHOTOCHEM_LEVEL 1
//options: 0: off, 1: C2Ray scheme as described in SB23, 2: General photo and thermochemistry solver
_________________________________
3.5 Species files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Specify the number of species in the *par file via
PARI_NUM_SPECIES 2
and the species file via
SPECIES_FILE mix1.spc
//options: Species filename
In *spc files, columns are as follows:
# 1:Number 2:Name 3:mass in amu 4:dof 5:electrostatic charge 6:relative amount 7:initial density excess 8: is_dust_like 9:opacity.opa
@ 0 S0 1.0 3. 0 1.0 -0.0 0 highenergy_atomichydrogen.opa
//options: number: running number from 0 to s-1
// name: string, used to designate output files for species
// mass in amu: self-explanatory
// dof: degrees of freedom for this species, defining adiabatic index as gamma_ad = (dof+2)/dof
// electrostatic charge: in elementary charges, can be positive or negative
// relative amount: relative density in boundary cell
// initial density excess: density jump at discontinuity, in case PARI_INIT_WIND 1 e.g. if value is -0.9 density jump of ratio 10, for -0.99 we get a jump of ratio 100 etc.
// is_dust_like: 0 or 1
// opacity.opa opacity files, depending on the preset opacity model, *opa, *op2, *op3 or *aiopa files are expected here.
_________________________________
3.6 Opacity files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
See example files in inputdata/