... | @@ -67,5 +67,20 @@ You're done. |
... | @@ -67,5 +67,20 @@ You're done. |
|
|
|
|
|
It's possible to apply any number of boundaries conditions, so instead of replicating common code, make it an independent conditions and call them as needed. (need details ?)
|
|
It's possible to apply any number of boundaries conditions, so instead of replicating common code, make it an independent conditions and call them as needed. (need details ?)
|
|
|
|
|
|
|
|
If you think it would be easier for the user to have a prepackages set of conditions, you can still cluster them[^1]:
|
|
|
|
|
|
|
|
```
|
|
|
|
FctBoundariesHandler evanescent(EVANESCENT,
|
|
|
|
[](GasDisk& gas, real dt) {
|
|
|
|
ComputeReflecting(gas, dt);
|
|
|
|
EvanescentBoundaryIn(gas, dt);
|
|
|
|
// Radial dumping in the outer region doesn't operate in case of stellar heating
|
|
|
|
if(!gas.disk().physic().starRadiation()) {
|
|
|
|
EvanescentBoundaryOut(gas, dt);
|
|
|
|
}
|
|
|
|
});
|
|
|
|
```
|
|
|
|
|
|
###
|
|
###
|
|
|
|
|
|
|
|
[^1]: here, using a lambda expression so that you can show off a bit. You could have used a regular function. |