@@ -18,7 +18,7 @@ For this task we will edit the following files:
Parameters can either be directly defined within your program, or specified
via the input file. Within every main file, (`*.cc`), the following function
is called, which will read in the imput file parameters
is called, which will read in the input file parameters
```c++
// parse command line arguments and input file
...
...
@@ -46,7 +46,7 @@ EntryPressureAquitard = 4.5e4 # Pa
PermeabilityAquifer=1e-12 # m^2
EntryPressureAquifer=1e4 # Pa
```
When a parameter is defined directly within your program, you'll need to recompile your program everytime you change the value. When a parameter is passed via the imput file, this is not the case. If we decided to vary the entry pressure in our geologic units a few times via the parameters listed above, there would be no need to recompile between simulation runs.
When a parameter is defined directly within your program, you'll need to recompile your program everytime you change the value. When a parameter is passed via the input file, this is not the case. If we decided to vary the entry pressure in our geologic units a few times via the parameters listed above, there would be no need to recompile between simulation runs.
* > __Task 1__: Change the aquitard's entry pressure in the input file to a lower value and compare the results with the previous solution. You don't need to recompile the executable.
*`<PARAMNAME>` is the name of the parameter in the input file
An example of this is already performed in the problem constructor. The Injection Duration (`injectionDuration_`) is defined via the imput file, and can then be used later in the problem.
An example of this is already performed in the problem constructor. The Injection Duration (`injectionDuration_`) is defined via the input file, and can then be used later in the problem.
