@@ -11,7 +11,8 @@ Here we will expand on what we've covered in the basics exercise, and the proble
We'll be editing the following files during this exercise:
* The __input file__: `params.input` ,
* and the __problem file__: `problem.hh`
* the __problem file__: `problem.hh` ,
* and the __properties file__: `properties.hh`.
Currently our grid is defined using the following input parameters in the input file:
...
...
@@ -41,7 +42,7 @@ The simulation should take much more time. Luckily there are other ways to resol
Up until now, we have used a basic uniform structured grid. This grid is provided in the Dune environment and is called the YASP grid (Yet Another Structured Parallel Grid).
In the Problem file, the grid properties are defined using the following command.
In the properties file, the grid properties are defined using the following command.
A YaspGrid, of dimension `dim` is used, and the coordinate system `Dune::TensorProductCoordinates`, with arguments coordinate type `ctype` and dimension `dim`, is provided as a secondary argument. This allows us to switch to a grid format that allows for more cells in certain zones, and a cell grading.
To use this format, we need to set the grid property in our problem file accordingly. Our problem dimension is 2 (`dim`), and we will provide the coordinates as doubles (`ctype`).
To use this format, we need to set the grid property in our properties file accordingly. Our problem dimension is 2 (`dim`), and we will provide the coordinates as doubles (`ctype`).
To switch the property we should replace the `Dune::YaspGrid<2>` argument with `Dune::YaspGrid<dim, Dune::TensorProductCoordinates<ctype, dim> >`, and the `dim` and `ctype` with `2` and `double`
In our input file, we can now specify more specific Grid sizing directions: Positions, Cells, and Grading, each of which can be defined per direction.
