Member CouetteScenario::_generator: piet
Member CouetteScenario::_multiMDCellService: piet
Member CouetteScenario::_multiMDService: piet
Member CouetteScenario::_sum_noise: piet
Member CouetteScenario::_sum_signal: piet
Member CouetteScenario::_tws: Piet
Member CouetteScenario::getCouetteSolverInterface (const double dx, tarch::la::Vector< 3, double > mdOffset, tarch::la::Vector< 3, double > mamicoMeshsize, tarch::la::Vector< 3, unsigned int > globalNumberCouplingCells, unsigned int outerRegion): piet, what is the mamicoMeshsize & the outer layer
Struct CouetteScenario::TimingValues: Piet
Class coupling::cellmappings::VelocityGradientRelaxationMapping< LinkedCell, dim >: Philipp please take a look on this class
Class coupling::cellmappings::VelocityGradientRelaxationTopOnlyMapping< LinkedCell, dim >: Philipp please take a look on this class
Class coupling::cellmappings::ZhouBoundaryForce< LinkedCell, dim >: Philipp please take a look on this class
Member coupling::configurations::CouetteConfig::twsLoop: piet
Member coupling::configurations::CouetteConfig::twsLoopMax: piet
Member coupling::configurations::CouetteConfig::twsLoopMin: piet
Member coupling::configurations::CouetteConfig::twsLoopStep: piet
Member coupling::datastructures::LinkedCellContainer< LinkedCell, dim >::applyXLayersOfGlobalNonGhostCellsWithLinkedCells (A &a, unsigned int layers2Use): Helene!!
Member coupling::datastructures::Molecule< dim >::setForce (const tarch::la::Vector< dim, double > &force): Philipp When the force should be set? when not? you need to implement this function.
Member coupling::interface::MDSimulation::init ()=0: Philipp ??
Member coupling::interface::MDSimulation::init (const tarch::utils::MultiMDService< MDSIMULATIONFACTORY_DIMENSION > &multiMDService, unsigned int localMDSimulation)=0: Philipp ??
Member coupling::MacroscopicSolverID: I have no idea what this is @someone
Member coupling::MultiMDMediator< LinkedCell, dim >::rmMDSimulation (const unsigned int &communicator, const unsigned int &index): How to handle removal of empty places?
Member coupling::NoMomentumInsertion< LinkedCell, dim >::getTimeIntervalPerMomentumInsertion () const override: We could set this to be zero? Since it does anything
Class coupling::paralleltopology::XYZTopology< dim >: Philipp could you please take a look on this class
Class coupling::paralleltopology::ZYXTopology< dim >: Philipp could you please take a look on this class
Member coupling::solvers::AbstractCouetteSolver< dim >::~AbstractCouetteSolver (): Why a dummy destructor buut not a constructor
Member coupling::UsherParticleInsertion< LinkedCell, dim >::insertDeleteMass (coupling::datastructures::CouplingCellWithLinkedCells< LinkedCell, dim > &cell, const tarch::la::Vector< dim, double > &couplingCellPosition, const tarch::la::Vector< dim, double > &couplingCellSize, const tarch::la::Vector< dim, double > &meanVelocity, const double &temperature, const coupling::BoundaryForceController< LinkedCell, dim > &boundaryForceController): why is this here? Already declared in the ParticleInsertion.
Class coupling::VelocityGradientRelaxationTopOnly< LinkedCell, dim >: Don't know what this does, just copied the comments from above