-
Notifications
You must be signed in to change notification settings - Fork 52
Tips
We collect general tips and tricks for t8code developers
When writing a new test you do not have to run make check
every time to compile your single test.
make check
will compile and run all tests which is rather time consuming.
Instead you can compile and run your tests individually:
make test/path/to/test
./test/path/to/test
If you are developing and running make check
often, waiting for sc and p4est tests to compile and run can be tedious.
Especially since you do not change anything in sc and p4est and hence know that the test cases will pass.
Open sc/Makefile.am
and p4est/Makefile.am
in an editor.
Comment the lines
include test/Makefile.am
by adding a #
in front.
Installation Guide
Configure Options
Setup t8code on JUWELS and other Slurm based systems
Setup t8code for VTK
General
Step 0 Hello World
Step 1 Creating a coarse mesh
Step 2 Creating a uniform forest
Step 3 Adapting a forest
Step 4 Partition,-Balance,-Ghost
Step 5 Store element data
Step 6 Computing stencils
Step 7 Interpolation
Features
Documentation
Tree Indexing
Element Indexing
Running on JUWELS using Slurm
Overview of the most used API functions
Known issues
Workflow - FreeCAD to t8code
Reproducing Scaling Resluts
Coding Guidelines
Tips
Debugging with gdb
Debugging with valgrind
Test driven development
Testing with GoogleTest
Writing C interface code