Skip to content

Tracker - Course Ideas 2025

Setup:

  • If we manage to show a robust and quick way to use vscode for debugging, we could make sure that participants use it.
  • Remove .create_all_patches.sh @IvBu
  • Remove timestamps from patch check if possible? Removing .create_all_patches.sh should fix this
  • Show folder structure / build structure in the beginning
  • Dumux cheat sheet, see #35

Slides:

  • 20 min CMake Intro?
  • dumux application: change main2p2c.cc to main2pni.cc @IvBu
  • dumux application: show generic interfaces for boundary values in problem file @IvBu
  • dumux application: move the slide "Typical c++ build steps" after the general CMake introduction. Keep it as it is
  • runtime: update link that leads to parameter list in doxygen documentation !284 (merged) @anna_m_kostelecky
  • add link to properties exercise in the end of properties slides !285 (merged) @anna_m_kostelecky
  • in general update link to the docs. The pages have better names now.
  • in Dumux introduction: fix image where distance vector between cell center and scvf does not point to middle of scvf? (fix in slides and doxygen documentation) !289 (merged) @anna_m_kostelecky
  • in Dumux introduction: show Dumux documentation and Dumux examples and Dumux file structure
  • Parallel: Show how to run in parallel with MPI and how to tweak multi-threading options (see https://dumux.org/docs/doxygen/master/running-in-parallel.html)
  • discrete fracture modeling: fix title of "buoyancy-driven gas migration" @IvBu
  • biomineralization modeling: for link to exercise use an alias - merge request !283 (merged) @hommel
  • biomineralization modeling: use smaller font size for exercise tasks - merge request !283 (merged) @hommel
  • [basic][problem] Show the generic BC interface (Participants were not aware, that one can implement solution dependent BC) @IvBu
  • When we show code in slides, we could put in which header the code comes from. @tufan
  • Material system: Bigger figures @tufan

Documentation:

  • see above, for tpfa discretization fix distance vector in image (fix in doxygen documentation and slides) !3845 @anna_m_kostelecky
  • incosistent? image for tpfa and mpfa, one uses x in image, the other u (adapt in doxygen documentation and respectively in slides) !289 (merged) and !3845 @anna_m_kostelecky
  • Add doxygen documentation for multidomain models, reference individual models (e.g. free-flow and porous medium model) + write/state coupling conditions that are used
  • Update staggered grid picture in style of other disc schemes --> use image from dumux!3850 (merged)
  • pictures for other CVFE schemes like CR/RT --> use image from dumux!3850 (merged)
  • Add a doxygen documentation page for multidomain similar to the course introduction
  • Add an overview to doxygen doc of most common grids (YASP, YASP with TensorProductCoordinates, ...), state how they differ and which paramters (dumux specific input parameters) have to be set for initializing them. Then reference in grid slides or grid exercise to the documentation.

Exercises:

  • General for preparation: remove script that generates patches for all exercises? Ideally, a patch should not be changed if there was no change to the content of the exercise. @IvBu
  • [material/basic][mpnc] create exercise for implementation of BC in case of priVar-switch (maybe one slide showing the "flash"). Show it in the material exercise but link to to basic, or ignore in basic. @leonidas
  • For grid exercise: Mention in README what the parameters for the new grid are meaning and that the grid parameters used before can be deleted. This was not so clear for a few people.
  • coupling-ff-pm exercise: Currently, the old implementation of the staggered grid is used for the free-flow. This is because in the last sub-exercise a turbulence model is introduced, which needs a second order scheme. One can think of introducing a new example for using the turbulence models with the old staggered implementation in dumux/examples/ and kicking the turbulence model out from this exercise. Then also the newer implementation for the staggered grid (based on coupling the mass and momentum grid) can be used in this exercise, which would be more up-to-date. As well, it would shorten the exercise as it is very long.
  • for solutions could simply copy the README and explictly write which lines need to be changed to what (for those people who have no idea how to approach the exercise)

Examples:

  • Multi-domain problems with simple coupling managers for easier teaching
    • Simple coupling manager for (CVFE) Stokes problem (@timok has one implemented)
    • Simple coupling manager for (CVFE) facet matrix-facture Diffusion/Diffusion or Darcy/Darcy problem (@timok has one implemented)

Things to keep in mind for the next course:

  • The first half a day of the course could be used to setup vscode, C++ and Git reminder.
  • Intro to SFB topics should be more like a teaser.
  • Introduce exercises before doing them, give them context, what they can expect, improve transition from slides to exercises
Edited by Ivan Buntic