sandbox/jieyun/README

Sandbox of Jieyun Pan

Correct way to use the code from my sandbox

• Suppose that Basilisk is installed in the directory $(BASILISK).

• During your code development, you should work in a separate directory, for example ~/basilisk_dev_jieyun (as in my case). This directory should not contain any source code from the original Basilisk distribution, but only your own code. You are free to use any version control system for your work, such as Git or Darcs.

• After downloading the code from my sandbox, place all the directories and files under ~/basilisk_dev_jieyun. Next, add a Makefile in ~/basilisk_dev_jieyun/test. A basic Makefile should include at least the following two lines:

include $(BASILISK)/Makefile.defs
CFLAGS += -I../src

The first line gives you access to the header files provided by Basilisk. The second line instructs the qcc compiler to search for header files in your local source directory, i.e. ~/basilisk_dev_jieyun/src.

• DO NOT add or overwrite any files in $(BASILISK).

• By following this approach, you will avoid contaminating the Basilisk source code and maintain a clean separation between Basilisk and your own development code.

Edge-Based Interface-Tracking (EBIT) / Semushin method

The Edge-Based Interface Tracking (EBIT) method is a novel Front-Tracking method developed by Chirco and Zaleski, 2022, Pan et al., 2024. In the EBIT method, the markers are located on the grid edges and the interface can be reconstructed without storing the connectivity of the markers. This feature allows almost automatic parallelization on a quad/octree grid.

References

Header files

The main header files can be found on the following pages:

• 2D Interface advection
• 2D Interface advection with an unsplit scheme
• Two-phase flow with the EBIT method
• Fitting functions
• Helper functions for EBIT method
• EBIT method + AMR
• 3D Interface advection

Verification test cases

Verification test cases can be found on the following pages:

Benchmark test cases with the 2D EBIT method

• Stagnation flow
• Translation
• Single vortex
• Zalesak’s disk
• Capillary wave
• Rayleigh-Taylor instability
• Rising bubble

Benchmark test cases with the 3D EBIT method

• Translation
• Single vortex
• Oscillating drop
• Rising bubble
• Bubble merging

Benchmark test cases with the 2D EBIT method (Unsplit)

• Single vortex
• Zalesak’s disk

Relevant test cases with the VOF method

• Translation
• Single vortex
• Zalesak’s disk
• Rayleigh-Taylor instability

Phase change problems with the EBIT method

Please refer to Tian’s sandbox

Useful postprocessing tools

• Facets output in an MPI run
• Triangulate facets for visualization using Paraview
• Theoretical solutions of 3D oscillating drop/bubble

Documentation

I spent some time reading the source code to figure out how the tagging function in Basilisk works. I added some comments and figures to the tag.h to make it clearer.

• Tagging function in Basilisk source code

Publications