... | ... | @@ -171,7 +171,7 @@ To check that the radiative part of the physic has been requested, we will use a |
|
|
|
|
|
### [Simulation](https://disc.pages.oca.eu/fargOCA/public/doxy/classfargOCA_1_1Simulation.html)
|
|
|
|
|
|
This is the "engine" of the simulation.
|
|
|
This is the "engine" of the simulation. It know how to perform a single step of the simulation, each step will be splitted into substeps (`velocityStep`, `adiabaticStep` etc..) called in the right order. That's the entry point to the simulation processing.
|
|
|
|
|
|
The disk geometry and physic configuration are described through a set of classes that are almost (almost) a [Singleton](https://en.wikipedia.org/wiki/Singleton_pattern) (because we do not need many of them). All object that need to have access to those information do so by referencing the appropriate instances.
|
|
|
|
... | ... | @@ -184,6 +184,12 @@ It describe the discretisation of the (possibly flat) cylinder containing the ga |
|
|
|
|
|
The grid coordinates.
|
|
|
|
|
|
### [SimulationTracker](https://disc.pages.oca.eu/fargOCA/public/doxy/classfargOCA_1_1SimulationTracker.html)
|
|
|
|
|
|
The [Simulation](#simulation) object job is to keep the simulation running. But the user probably want to collect some information along the way. In order to keep both issues separated, all information will be collected through **SimulationTracker**s.
|
|
|
|
|
|
Simulation trackers have a [section on their own](Developer's-corner/Simulation Trackers) in the developer's corner.
|
|
|
|
|
|
## Boundaries Conditions
|
|
|
|
|
|
Boundaries condition are implemented through **BoundariesHandler** [function objects](https://en.wikipedia.org/wiki/Command_pattern)[^5].
|
... | ... | |