diff --git a/ex3/ex3_results.txt b/ex3/ex3_results.txt deleted file mode 100644 index bf4f26c..0000000 --- a/ex3/ex3_results.txt +++ /dev/null @@ -1,222 +0,0 @@ - --------------- Task 1 -------------- - -------------------------------------------------------------- -STREAM version $Revision: 5.10 $ -------------------------------------------------------------- -This system uses 8 bytes per array element. -------------------------------------------------------------- -Array size = 80000000 (elements), Offset = 0 (elements) -Memory per array = 610.4 MiB (= 0.6 GiB). -Total memory required = 1831.1 MiB (= 1.8 GiB). -Each kernel will be executed 20 times. - The *best* time for each kernel (excluding the first iteration) - will be used to compute the reported bandwidth. -------------------------------------------------------------- -Your clock granularity/precision appears to be 1 microseconds. -Each test below will take on the order of 116886 microseconds. - (= 116886 clock ticks) -Increase the size of the arrays if this shows that -you are not getting at least 20 clock ticks per test. -------------------------------------------------------------- -WARNING -- The above is only a rough guideline. -For best results, please be sure you know the -precision of your system timer. -------------------------------------------------------------- -Function Best Rate MB/s Avg time Min time Max time -Copy: 29569.4 0.048585 0.043288 0.059164 -Scale: 17644.0 0.082248 0.072546 0.102548 -Add: 21030.1 0.100620 0.091298 0.124700 -Triad: 21230.7 0.100758 0.090435 0.120631 -------------------------------------------------------------- -Solution Validates: avg error less than 1.000000e-13 on all three arrays -------------------------------------------------------------- -./flops.exe - - FLOPS C Program (Double Precision), V2.0 18 Dec 1992 - - Module Error RunTime MFLOPS - (usec) - 1 4.0146e-13 0.0024 5827.9076 - 2 -1.4166e-13 0.0007 10037.8942 - 3 4.7184e-14 0.0039 4371.9185 - 4 -1.2557e-13 0.0034 4355.5711 - 5 -1.3800e-13 0.0066 4415.6439 - 6 3.2380e-13 0.0065 4441.6299 - 7 -8.4583e-11 0.0053 2277.1707 - 8 3.4867e-13 0.0069 4367.6094 - - Iterations = 512000000 - NullTime (usec) = 0.0000 - MFLOPS(1) = 7050.6178 - MFLOPS(2) = 3461.6233 - MFLOPS(3) = 4175.0442 - MFLOPS(4) = 4389.7311 - --------------- Task 2 -------------- - -Memory needed (double 64-bit, 8 bytes): -(A) (2N + 1) * 8 bytes -(B) (M*N + M + N) * 8 bytes -(C) (M*L + L*N + M*N) * 8 bytes -(D) (N + N + p) * 8 bytes - -Floating point operations: -(A) 2N -(B) M * 2N -(C) M * 2L * N -(D) 2 * N * p (Horner Schema) - -Read/Write operations: -(A) Read: 2N Write: 1 -(B) Read: M*2N Write: M*N -(C) Read: M*2L*N Write: M*L*N -(D) Read: 2*N*p Write: N*P - --------------- Task 3 -------------- - -Functions implemented in task_3.cpp - --------------- Task 4 -------------- - ------ Benchmark (A) ----- -Memory allocated : 0.745 GByte -Duration per loop : 0.036 sec -GFLOPS : 2.579 -GiByte/s : 20.630 -------------------------- ------ Benchmark (B) ----- -Memory allocated : 0.715 GByte -Duration per loop : 0.105 sec -GFLOPS : 1.704 -GiByte/s : 6.818 -------------------------- ------ Benchmark (C) ----- -Memory allocated : 0.026 GByte -Duration per loop : 0.459 sec -GFLOPS : 4.062 -GiByte/s : 0.057 -------------------------- ------ Benchmark (D) ----- -Memory allocated : 0.015 GByte -Duration per loop : 0.310 sec -GFLOPS : 1.201 -GiByte/s : 0.048 -------------------------- - - --------------- Task 5 -------------- - ------ Benchmark norm ----- -||x|| = 897124.301552 -Memory allocated : 0.373 GByte -Duration per loop : 0.022 sec -GFLOPS : 4.222 -GiByte/s : 16.890 -------------------------- -What do you observe? Why? --> Faster per loop than scalar product, only loads elements of 1 vector, instead of 2. - --------------- Task 6 -------------- - -Benchmarks using cBLAS ------ Benchmark (A) ----- -Memory allocated : 0.745 GByte -Duration per loop : 0.023 sec -GFLOPS : 4.006 -GiByte/s : 32.052 -------------------------- ------ Benchmark (B) ----- -Memory allocated : 0.715 GByte -Duration per loop : 0.026 sec -GFLOPS : 7.010 -GiByte/s : 28.045 -------------------------- ------ Benchmark (C) ----- -Memory allocated : 0.026 GByte -Duration per loop : 0.020 sec -GFLOPS : 91.320 -GiByte/s : 1.278 -------------------------- - - --------------- Task 7 -------------- - -A = -4.000000 1.000000 0.250000 0.111111 0.062500 -1.000000 4.000000 1.000000 0.250000 0.111111 -0.250000 1.000000 4.000000 1.000000 0.250000 -0.111111 0.250000 1.000000 4.000000 1.000000 -0.062500 0.111111 0.250000 1.000000 4.000000 - - -b = -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 - - -L + U = -4.000000 1.000000 0.250000 0.111111 0.062500 -0.250000 3.750000 0.937500 0.222222 0.095486 -0.062500 0.250000 3.750000 0.937500 0.222222 -0.027778 0.059259 0.250000 3.749370 0.937050 -0.015625 0.025463 0.059259 0.249922 3.749234 - - -x = -0.000000 0.196259 -0.000000 0.148391 -0.000000 0.151272 -0.000000 0.148391 -0.000000 0.196259 - - -Check solution: -A * x = -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 -0.000000 1.000000 - - -N = | 1 | 2 | 4 | 8 | 16 | 32 ----------|--------|--------|--------|--------|--------|------- -Nrhs = 2 | 0.0047 | 0.0045 | 0.0046 | 0.0130 | 0.0203 | 0.0476 -Nrhs = 4 | 0.0027 | 0.0031 | 0.0033 | 0.0046 | 0.0085 | 0.0250 -Nrhs = 8 | 0.0035 | 0.0035 | 0.0045 | 0.0061 | 0.0119 | 0.0300 -Nrhs = 16 | 0.0085 | 0.0062 | 0.0221 | 0.0113 | 0.0599 | 0.0757 -Nrhs = 32 | 0.0122 | 0.0165 | 0.0112 | 0.0123 | 0.0238 | 0.0834 -Nrhs = 64 | 0.0072 | 0.0078 | 0.0164 | 0.0133 | 0.0421 | 0.0666 -Nrhs = 128 | 0.0073 | 0.0189 | 0.0269 | 0.0199 | 0.0337 | 0.1041 -Nrhs = 256 | 0.0107 | 0.0135 | 0.0279 | 0.0351 | 0.0582 | 0.1438 -Nrhs = 512 | 0.0276 | 0.0174 | 0.0237 | 0.1027 | 0.1113 | 0.2417 - -For fixed n, the solution time per rhs does not slow down consistently and scales very well. -Its faster than expected. - - --------------- Task 8 -------------- - - - There are 1 processes running. - -Intervalls: 100 x 100 - - Start Jacobi solver for 10201 d.o.f.s -aver. Jacobi rate : 0.997922 (1000 iter) -final error: 0.124971 (rel) 0.000194029 (abs) -JacobiSolve: timing in sec. : 0.079399 -ASCI file square_100.txt opened -17361 2 34320 3 - - Start Jacobi solver for 17361 d.o.f.s -aver. Jacobi rate : 0.998401 (1000 iter) -final error: 0.201744 (rel) 0.000265133 (abs) -JacobiSolve: timing in sec. : 0.18853 - - - diff --git a/ex3/ex3_sheet.pdf b/ex3/ex_3.pdf similarity index 100% rename from ex3/ex3_sheet.pdf rename to ex3/ex_3.pdf diff --git a/ex3/seq/CLANG_default.mk b/ex3/seq/CLANG_default.mk deleted file mode 100644 index 4bc290d..0000000 --- a/ex3/seq/CLANG_default.mk +++ /dev/null @@ -1,123 +0,0 @@ -# Basic Defintions for using GNU-compiler suite sequentially -# requires setting of COMPILER=CLANG_ - -#CLANGPATH=//usr/lib/llvm-10/bin/ -CC = ${CLANGPATH}clang -CXX = ${CLANGPATH}clang++ -#CXX = ${CLANGPATH}clang++ -lomptarget -fopenmp-targets=nvptx64-nvidia-cuda --cuda-path=/opt/pgi/linux86-64/2017/cuda/8.0 -#F77 = gfortran -LINKER = ${CXX} - -#http://clang.llvm.org/docs/UsersManual.html#options-to-control-error-and-warning-messages -WARNINGS += -Weverything -Wno-c++98-compat -Wno-sign-conversion -Wno-date-time -Wno-shorten-64-to-32 -Wno-padded -ferror-limit=1 -WARNINGS += -Wdocumentation -Wconversion -Wshadow -Wfloat-conversion -pedantic -#-fsyntax-only -Wdocumentation -Wconversion -Wshadow -Wfloat-conversion -pedantic - -CXXFLAGS += -O3 -std=c++17 -ferror-limit=1 ${WARNINGS} -# don't use -Ofast -# -ftrapv -LINKFLAGS += -O3 - -# different libraries in Ubuntu or manajaró -ifndef UBUNTU -UBUNTU=1 -endif - -# BLAS, LAPACK -LINKFLAGS += -llapack -lblas -# -lopenblas -ifeq ($(UBUNTU),1) -# ubuntu -else -# on archlinux -LINKFLAGS += -lcblas -endif - -# interprocedural optimization -CXXFLAGS += -flto -LINKFLAGS += -flto - -# very good check -# http://clang.llvm.org/extra/clang-tidy/ -# good check, see: http://llvm.org/docs/CodingStandards.html#include-style -SWITCH_OFF=,-readability-magic-numbers,-readability-redundant-control-flow,-readability-redundant-member-init -SWITCH_OFF+=,-readability-redundant-member-init,-readability-isolate-declaration -#READABILITY=,readability*${SWITCH_OFF} -#TIDYFLAGS = -checks=llvm-*,-llvm-header-guard -header-filter=.* -enable-check-profile -extra-arg="-std=c++17" -extra-arg="-fopenmp" -TIDYFLAGS = -checks=llvm-*,-llvm-header-guard${READABILITY} -header-filter=.* -enable-check-profile -extra-arg="-std=c++17" -extra-arg="-fopenmp" -#TIDYFLAGS += -checks='modernize* -# ??? -#TIDYFLAGS = -checks='cert*' -header-filter=.* -# MPI checks ?? -#TIDYFLAGS = -checks='mpi*' -# ?? -#TIDYFLAGS = -checks='performance*' -header-filter=.* -#TIDYFLAGS = -checks='portability-*' -header-filter=.* -#TIDYFLAGS = -checks='readability-*' -header-filter=.* - -default: ${PROGRAM} - -${PROGRAM}: ${OBJECTS} - $(LINKER) $^ ${LINKFLAGS} -o $@ - -clean: - @rm -f ${PROGRAM} ${OBJECTS} - -clean_all:: clean - @rm -f *_ *~ *.bak *.log *.out *.tar - -codecheck: tidy_check -tidy_check: - clang-tidy ${SOURCES} ${TIDYFLAGS} -- ${SOURCES} -# see also http://clang-developers.42468.n3.nabble.com/Error-while-trying-to-load-a-compilation-database-td4049722.html - -run: clean ${PROGRAM} -# time ./${PROGRAM} ${PARAMS} - ./${PROGRAM} ${PARAMS} - -# tar the current directory -MY_DIR = `basename ${PWD}` -tar: clean_all - @echo "Tar the directory: " ${MY_DIR} - @cd .. ;\ - tar cf ${MY_DIR}.tar ${MY_DIR} *default.mk ;\ - cd ${MY_DIR} -# tar cf `basename ${PWD}`.tar * - -doc: - doxygen Doxyfile - -######################################################################### - -.cpp.o: - $(CXX) -c $(CXXFLAGS) -o $@ $< - -.c.o: - $(CC) -c $(CFLAGS) -o $@ $< - -.f.o: - $(F77) -c $(FFLAGS) -o $@ $< - -################################################################################################## -# some tools -# Cache behaviour (CXXFLAGS += -g tracks down to source lines; no -pg in linkflags) -cache: ${PROGRAM} - valgrind --tool=callgrind --simulate-cache=yes ./$^ ${PARAMS} -# kcachegrind callgrind.out. & - kcachegrind `ls -1tr callgrind.out.* |tail -1` - -# Check for wrong memory accesses, memory leaks, ... -# use smaller data sets -mem: ${PROGRAM} - valgrind -v --leak-check=yes --tool=memcheck --undef-value-errors=yes --track-origins=yes --log-file=$^.addr.out --show-reachable=yes ./$^ ${PARAMS} - -# Simple run time profiling of your code -# CXXFLAGS += -g -pg -# LINKFLAGS += -pg -prof: ${PROGRAM} - perf record ./$^ ${PARAMS} - perf report -# gprof -b ./$^ > gp.out -# kprof -f gp.out -p gprof & - -codecheck: tidy_check diff --git a/ex3/seq/GCC_default.mk b/ex3/seq/GCC_default.mk deleted file mode 100644 index e9e0a0c..0000000 --- a/ex3/seq/GCC_default.mk +++ /dev/null @@ -1,196 +0,0 @@ -# Basic Defintions for using GNU-compiler suite sequentially -# requires setting of COMPILER=GCC_ - -CC = gcc -CXX = g++ -F77 = gfortran -LINKER = ${CXX} - -WARNINGS = -Wall -pedantic -Wextra -Weffc++ -Woverloaded-virtual -Wfloat-equal -Wshadow \ - -Wredundant-decls -fmax-errors=1 -# -Wunreachable-code -Winline -CXXFLAGS += -ffast-math -O3 -march=native -std=c++17 ${WARNINGS} -#CXXFLAGS += -Ofast -funroll-all-loops -std=c++17 ${WARNINGS} -#-msse3 -# -ftree-vectorizer-verbose=2 -DNDEBUG -# -ftree-vectorizer-verbose=5 -# -ftree-vectorize -fdump-tree-vect-blocks=foo.dump -fdump-tree-pre=stderr - -# CFLAGS = -ffast-math -O3 -DNDEBUG -msse3 -fopenmp -fdump-tree-vect-details -# CFLAGS = -ffast-math -O3 -funroll-loops -DNDEBUG -msse3 -fopenmp -ftree-vectorizer-verbose=2 -# #CFLAGS = -ffast-math -O3 -DNDEBUG -msse3 -fopenmp -# FFLAGS = -ffast-math -O3 -DNDEBUG -msse3 -fopenmp -# LFLAGS = -ffast-math -O3 -DNDEBUG -msse3 -fopenmp -LINKFLAGS += -O3 - -#architecture -#CPU = -march=znver2 -CXXFLAGS += ${CPU} -LINKFLAGS += ${CPU} - -# different libraries in Ubuntu or manajaró -ifndef UBUNTU -UBUNTU=1 -endif - -# BLAS, LAPACK -ifeq ($(UBUNTU),1) -LINKFLAGS += -llapack -lblas -# -lopenblas -else -# on archlinux -LINKFLAGS += -llapack -lopenblas -lcblas -endif - -# interprocedural optimization -#CXXFLAGS += -flto -#LINKFLAGS += -flto - -# for debugging purpose (save code) -# -fsanitize=leak # only one out the three can be used -# -fsanitize=address -# -fsanitize=thread -SANITARY = -fsanitize=address -fsanitize=undefined -fsanitize=null -fsanitize=return \ - -fsanitize=bounds -fsanitize=alignment -fsanitize=float-divide-by-zero -fsanitize=float-cast-overflow \ - -fsanitize=bool -fsanitize=enum -fsanitize=vptr -#CXXFLAGS += ${SANITARY} -#LINKFLAGS += ${SANITARY} - -# profiling tools -#CXXFLAGS += -pg -#LINKFLAGS += -pg - - -default: ${PROGRAM} - -${PROGRAM}: ${OBJECTS} - $(LINKER) $^ ${LINKFLAGS} -o $@ - -clean: - @rm -f ${PROGRAM} ${OBJECTS} - -clean_all:: clean - -@rm -f *_ *~ *.bak *.log *.out *.tar *.orig *.optrpt - -@rm -rf html - -run: clean ${PROGRAM} -#run: ${PROGRAM} -# time ./${PROGRAM} ${PARAMS} - ./${PROGRAM} ${PARAMS} - -# tar the current directory -MY_DIR = `basename ${PWD}` -tar: clean_all - @echo "Tar the directory: " ${MY_DIR} - @cd .. ;\ - tar cf ${MY_DIR}.tar ${MY_DIR} *default.mk ;\ - cd ${MY_DIR} -# tar cf `basename ${PWD}`.tar * -#find . -size +10M > large_files -#--exclude-from ${MY_DIR}/large_files - -zip: clean - @echo "Zip the directory: " ${MY_DIR} - @cd .. ;\ - zip -r ${MY_DIR}.zip ${MY_DIR} *default.mk ;\ - cd ${MY_DIR} - -doc: - doxygen Doxyfile - -######################################################################### -.SUFFIXES: .f90 - -.cpp.o: - $(CXX) -c $(CXXFLAGS) -o $@ $< -# $(CXX) -c $(CXXFLAGS) -o $@ $< 2>&1 | tee -a $<.log -# $(CXX) -c $(CXXFLAGS) -o $@ $< 2>&1 | tee -a $(<:.cpp=.log) - -.c.o: - $(CC) -c $(CFLAGS) -o $@ $< - -.f.o: - $(F77) -c $(FFLAGS) -o $@ $< - -.f90.o: - $(F77) -c $(FFLAGS) -o $@ $< - -################################################################################################## -# some tools -# Cache behaviour (CXXFLAGS += -g tracks down to source lines; no -pg in linkflags) -cache: ${PROGRAM} - valgrind --tool=callgrind --simulate-cache=yes ./$^ ${PARAMS} -# kcachegrind callgrind.out. & - kcachegrind `ls -1tr callgrind.out.* |tail -1` - -# Check for wrong memory accesses, memory leaks, ... -# use smaller data sets -# no "-pg" in compile/link options -mem: ${PROGRAM} - valgrind -v --leak-check=yes --tool=memcheck --undef-value-errors=yes --track-origins=yes --log-file=$^.addr.out --show-reachable=yes ./$^ ${PARAMS} -# Graphical interface -# valkyrie - -# Simple run time profiling of your code -CXXFLAGS += -g -pg -LINKFLAGS += -pg -prof: ${PROGRAM} - ./$^ ${PARAMS} - gprof -b ./$^ > gp.out -# kprof -f gp.out -p gprof & - -# sudo apt install gprofng-gui -# https://parallel.computer/presentations/PPoPP2023/2023-Ruud-Slides.pdf -# read §3 in https://sourceware.org/binutils/docs/gprofng.html -# /usr/bin/gp-collect-app -o test.1.er -p on -S on /home/ghaase/Lectures/Math2CPP/Codes/seq/jacobi_oo_stl/main.GCC_ -prof2: ${PROGRAM} - gprofng collect app -h auto ./$^ ${PARAMS} -# gprofng display text -functions `ls -1tdr test.*.er |tail -1` - gprofng display text -script gprofng_script2 `ls -1tdr test.*.er |tail -1` -# gprofng display text -script gprofng_script2 test.*.er -# gprofng display gui & - -prof3: ${PROGRAM} - perf record ./$^ ${PARAMS} - perf report -# perf in Ubuntu 20.04: https://www.howtoforge.com/how-to-install-perf-performance-analysis-tool-on-ubuntu-20-04/ -# * install -# * sudo vi /etc/sysctl.conf -# add kernel.perf_event_paranoid = 0 - -#Trace your heap: -#> heaptrack ./main.GCC_ -#> heaptrack_gui heaptrack.main.GCC_..gz -heap: ${PROGRAM} - heaptrack ./$^ ${PARAMS} - heaptrack_gui `ls -1tr heaptrack.$^.* |tail -1` & - -codecheck: $(SOURCES) - cppcheck --enable=all --inconclusive --std=c++17 --suppress=missingIncludeSystem $^ - - -######################################################################## -# get the detailed status of all optimization flags -info: - echo "detailed status of all optimization flags" - $(CXX) --version - $(CXX) -Q $(CXXFLAGS) --help=optimizers - lscpu - inxi -C - lstopo - -# Excellent hardware info -# hardinfo -# Life monitoring of CPU frequency etc. -# sudo i7z - -# Memory consumption -# vmstat -at -SM 3 -# xfce4-taskmanager - - -# https://www.tecmint.com/check-linux-cpu-information/ -#https://www.tecmint.com/monitor-cpu-and-gpu-temperature-in-ubuntu/ - -# Debugging: -# https://wiki.archlinux.org/index.php/Debugging diff --git a/ex3/seq/Makefile b/ex3/seq/Makefile deleted file mode 100644 index ee3c372..0000000 --- a/ex3/seq/Makefile +++ /dev/null @@ -1,36 +0,0 @@ -#DIRS=skalar skalar_stl jacobi generate_mesh jacobi_oo_stl -DIRS=skalar skalar_stl jacobi jacobi_oo_stl thread_17 densematrices_libs generate_mesh mgrid -# -#WWW_ROOT=${HOME}/public_html/Lectures/Math2CPP/Codes/seq -WWW_ROOT=../../html/Codes/seq - - -clean: - @for i in ${DIRS}; do cd $${i}; make clean_all; cd ..; done -# rm *.tar - -doc: - @for i in ${DIRS}; do cd $${i}; make doc; cd ..; done - -tar: - @for i in ${DIRS}; do cd $${i}; make tar; cd ..; done - -zip: - @for i in ${DIRS}; do cd $${i}; make zip; cd ..; done - -www: clean tar zip doc - mkdir -p ${WWW_ROOT} - cp -up *_default.mk ${WWW_ROOT} - @for i in ${DIRS};\ - do \ - mv $${i}.tar $${i}.zip ${WWW_ROOT}; \ - cp -rup $${i} ${WWW_ROOT}; \ - done - - -# @for i in ${DIRS};\ -# do \ -# tar -czf $${i}.tgz $${i} *default*.mk; \ -# mv $${i}.tgz ${WWW_ROOT}; \ -# cp -r $${i} ${WWW_ROOT}; \ -# find $${i} -name html -exec cp -r {} ${WWW_ROOT}/$${i} \; ; done diff --git a/ex3/seq/check_all b/ex3/seq/check_all deleted file mode 100755 index 0f035d7..0000000 --- a/ex3/seq/check_all +++ /dev/null @@ -1,32 +0,0 @@ -#!/bin/bash - -EXAMPLES='skalar skalar_stl jacobi jacobi_stl jacobi_oo_stl thread_17 densematrices_libs' -# EXAMPLES='template_seq' -#COMPTYPE='GCC_ CLANG_' -COMPTYPE='ONEAPI_' - -LOG_FILE='compile.log' -rm -f ${LOG_FILE} - -echo -echo ' Compile examples' -echo - - -for verz in ${EXAMPLES} - do echo 2>&1 | tee -a ${LOG_FILE} - echo '----------- ' $verz ' -----------' 2>&1 | tee -a ${LOG_FILE} - pushd $verz - echo 2>&1 | tee -a ${LOG_FILE} - pwd >> ../${LOG_FILE} - for comp in ${COMPTYPE} - do echo 2>&1 | tee -a ../${LOG_FILE} - echo '########### ' $comp ' ###########' 2>&1 | tee -a ../${LOG_FILE} - echo 2>&1 | tee -a ../${LOG_FILE} - make clean COMPILER=${comp} 2>&1 | tee -a ../${LOG_FILE} - make COMPILER=${comp} 2>&1 | tee -a ../${LOG_FILE} -# make run COMPILER=${comp} 2>&1 | tee -a ../${LOG_FILE} - done - popd - done - diff --git a/ex3/seq/compile.log b/ex3/seq/compile.log deleted file mode 100644 index 8203721..0000000 --- a/ex3/seq/compile.log +++ /dev/null @@ -1,49 +0,0 @@ - ------------ skalar ----------- -/home/dino/scf_celebic/ex3/seq/skalar - -########### ONEAPI_ ########### - -Makefile:32: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. -Makefile:32: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. - ------------ skalar_stl ----------- -/home/dino/scf_celebic/ex3/seq/skalar_stl - -########### ONEAPI_ ########### - -Makefile:30: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. -Makefile:30: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. - ------------ jacobi ----------- - - ------------ jacobi_stl ----------- - - ------------ jacobi_oo_stl ----------- -/home/dino/scf_celebic/ex3/seq/jacobi_oo_stl - -########### ONEAPI_ ########### - -Makefile:26: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. -Makefile:26: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. - ------------ thread_17 ----------- -/home/dino/scf_celebic/ex3/seq/thread_17 - -########### ONEAPI_ ########### - -Makefile:42: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. -Makefile:42: ../ONEAPI_default.mk: No such file or directory -make: *** No rule to make target '../ONEAPI_default.mk'. Stop. - ------------ densematrices_libs ----------- - diff --git a/ex3/seq/generate_mesh/L_shape.m b/ex3/seq/generate_mesh/L_shape.m deleted file mode 100644 index 268d44b..0000000 --- a/ex3/seq/generate_mesh/L_shape.m +++ /dev/null @@ -1,26 +0,0 @@ -% Copyright: Reza Mokhtari -clear all -clc -%% plot L-shape -g=[2 0 2 0 0 1 0; - 2 2 2 0 1 1 0; - 2 2 1 1 1 1 0; - 2 1 1 1 2 1 0; - 2 1 0 2 2 1 0; - 2 0 0 2 0 1 0]'; -[p,e,t] = initmesh(g,'hmax',0.5); -pdemesh(p,e,t) - -%% GH -% output from -% -% coordinates p: [2][nnode] -% connectivity t: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain - -% flatpak run org.octave.Octave -ascii_write_mesh( p, t, e, mfilename); diff --git a/ex3/seq/generate_mesh/ascii_read_meshvector.m b/ex3/seq/generate_mesh/ascii_read_meshvector.m deleted file mode 100644 index 03119db..0000000 --- a/ex3/seq/generate_mesh/ascii_read_meshvector.m +++ /dev/null @@ -1,43 +0,0 @@ -function [ xc, ia, v ] = ascii_read_meshvector( fname ) -% -% Loads the 2D triangular mesh (coordinates, vertex connectivity) -% together with values on its vertices from an ASCII file. -% Matlab indexing is stored (starts with 1). -% -% The input file format is compatible -% with Mesh_2d_3_matlab:Write_ascii_matlab(..) in jacobi_oo_stl/geom.h -% -% -% IN: fname - filename -% OUT: xc - coordinates -% ia - mesh connectivity -% v - solution vector - -DELIMETER = ' '; - -fprintf('Read file %s\n',fname) - -% Read mesh constants -nn = dlmread(fname,DELIMETER,[0 0 0 3]); %% row_1, col_1, row_2, col_2 in C indexing!!! -nnode = nn(1); -ndim = nn(2); -nelem = nn(3); -nvert = nn(4); - -% Read coordinates -row_start = 0+1; -row_end = 0+nnode; -xc = dlmread(fname,DELIMETER,[row_start 0 row_end ndim-1]); - -% Read connectivity -row_start = row_end+1; -row_end = row_end+nelem; -ia = dlmread(fname,DELIMETER,[row_start 0 row_end nvert-1]); - -% Read solution -row_start = row_end+1; -row_end = row_end+nnode; -v = dlmread(fname,DELIMETER,[row_start 0 row_end 0]); -end - - diff --git a/ex3/seq/generate_mesh/ascii_write_mesh.m b/ex3/seq/generate_mesh/ascii_write_mesh.m deleted file mode 100644 index ebead75..0000000 --- a/ex3/seq/generate_mesh/ascii_write_mesh.m +++ /dev/null @@ -1,49 +0,0 @@ -function ascii_write_mesh( xc, ia, e, basename) -% -% Saves the 2D triangular mesh in the minimal way (only coordinates, vertex connectivity, minimal boundary edge info) -% in an ASCII file. -% Matlab indexing is stored (starts with 1). -% -% The output file format is compatible with Mesh_2d_3_matlab:Mesh_2d_3_matlab(std::string const &fname) in jacobi_oo_stl/geom.h -% -% IN: -% coordinates xc: [2][nnode] -% connectivity ia: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain -% basename: file name without extension -% -% Data have been generated via . -% -fname = [basename, '.txt']; - -nnode = int32(size(xc,2)); -ndim = int32(size(xc,1)); -nelem = int32(size(ia,2)); -nvert_e = int32(3); - - -dlmwrite(fname,nnode,'delimiter','\t','precision',16) % number of nodes -dlmwrite(fname,ndim,'-append','delimiter','\t','precision',16) % space dimension -dlmwrite(fname,nelem,'-append','delimiter','\t','precision',16) % number of elements -dlmwrite(fname,nvert_e,'-append','delimiter','\t','precision',16) % number of vertices per element - -% dlmwrite(fname,xc(:),'-append','delimiter','\t','precision',16) % coordinates -dlmwrite(fname,xc([1,2],:).','-append','delimiter','\t','precision',16) % coordinates - -% no subdomain info transferred -tmp=int32(ia(1:3,:)); -% dlmwrite(fname,tmp(:),'-append','delimiter','\t','precision',16) % connectivity in Matlab indexing -dlmwrite(fname,tmp(:,:).','-append','delimiter','\t','precision',16) % connectivity in Matlab indexing - -% store only start and end point of boundary edges, -nbedges = size(e,2); -dlmwrite(fname,nbedges,'-append','delimiter','\t','precision',16) % number boundary edges -tmp=int32(e(1:2,:)); -% dlmwrite(fname,tmp(:),'-append','delimiter','\t','precision',16) % boundary edges in Matlab indexing -dlmwrite(fname,tmp(:,:).','-append','delimiter','\t','precision',16) % boundary edges in Matlab indexing - -end diff --git a/ex3/seq/generate_mesh/chip_2materials.asv b/ex3/seq/generate_mesh/chip_2materials.asv deleted file mode 100644 index 766b791..0000000 --- a/ex3/seq/generate_mesh/chip_2materials.asv +++ /dev/null @@ -1,56 +0,0 @@ -% Square: -% flatpak run org.octave.Octave -% or -% octave --no-window-system --no-gui -qf - -clear all -clc -% %% L-shape -% g=[2 0 2 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right -% 2 2 2 0 1 1 0; -% 2 2 1 1 0.5 1 0; -% 2 1 1 0.5 2 1 0; -% 2 1 0 2 2 1 0; -% 2 0 0 2 0 1 0]'; - -%% square -% g=[2 0 1 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right -% 2 1 1 0 1 1 0; -% 2 1 0 1 1 1 0; -% 2 0 0 1 0 1 0]'; - -g=[2 0.00 1.00 0.00 0.00 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right - 2 1.00 1.00 0.00 0.60 1 0; - 2 1.00 0.83 0.60 0.60 1 0; - 2 0.83 0.17 0.60 0.60 1 2; - 2 0.17 0.00 0.60 0.60 1 0; - 2 0.00 0.00 0.60 0.00 1 0; - 2 0.83 0.83 0.60 0.80 2 0; - 2 0.83 0.17 0.80 0.80 2 0; - 2 0.17 0.17 0.80 0.60 2 0; - 2 - ]'; - - -[p,e,t] = initmesh(g,'hmax',0.1); -%[p,e,t] = initmesh(g,'hmax',0.6); -pdemesh(p,e,t) -% pdemesh(p,e,t,"NodeLabels","on") - -%% GH -% output from -% -% coordinates p: [2][nnode] -% connectivity t: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain - -ascii_write_mesh( p, t, e, mfilename); - - - -% tmp=t(1:3,:) - diff --git a/ex3/seq/generate_mesh/chip_2materials.m b/ex3/seq/generate_mesh/chip_2materials.m deleted file mode 100644 index 58bf2fb..0000000 --- a/ex3/seq/generate_mesh/chip_2materials.m +++ /dev/null @@ -1,59 +0,0 @@ -% Square: -% flatpak run org.octave.Octave -% or -% octave --no-window-system --no-gui -qf - -clear all -clc -% %% L-shape -% g=[2 0 2 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right -% 2 2 2 0 1 1 0; -% 2 2 1 1 0.5 1 0; -% 2 1 1 0.5 2 1 0; -% 2 1 0 2 2 1 0; -% 2 0 0 2 0 1 0]'; - -%% square -% g=[2 0 1 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right -% 2 1 1 0 1 1 0; -% 2 1 0 1 1 1 0; -% 2 0 0 1 0 1 0]'; - -g=[2 0.00 1.00 0.00 0.00 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right - 2 1.00 1.00 0.00 0.60 1 0; - 2 1.00 0.83 0.60 0.60 1 0; - 2 0.83 0.17 0.60 0.60 1 2; - 2 0.17 0.00 0.60 0.60 1 0; - 2 0.00 0.00 0.60 0.00 1 0; - 2 0.83 0.83 0.60 0.80 2 0; - 2 0.83 0.17 0.80 0.80 2 0; - 2 0.17 0.17 0.80 0.60 2 0; - 2 0.50 0.65 0.15 0.30 1 0; - 2 0.65 0.50 0.30 0.45 1 0; - 2 0.50 0.35 0.45 0.30 1 0; - 2 0.35 0.50 0.30 0.15 1 0 - ]'; - - -[p,e,t] = initmesh(g,'hmax',0.1); -%[p,e,t] = initmesh(g,'hmax',0.6); -pdemesh(p,e,t) -% pdemesh(p,e,t,"NodeLabels","on") - -%% GH -% output from -% -% coordinates p: [2][nnode] -% connectivity t: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain - -ascii_write_mesh( p, t, e, mfilename); - - - -% tmp=t(1:3,:) - diff --git a/ex3/seq/generate_mesh/chip_2materials.txt b/ex3/seq/generate_mesh/chip_2materials.txt deleted file mode 100644 index 7861080..0000000 --- a/ex3/seq/generate_mesh/chip_2materials.txt +++ /dev/null @@ -1,442 +0,0 @@ -143 -2 -235 -3 -0 0 -1 0 -1 0.6 -0.83 0.6 -0.17 0.6 -0 0.6 -0.83 0.8 -0.17 0.8 -0.5 0.15 -0.65 0.3 -0.5 0.45 -0.35 0.3 -0.5 0.6 -0.1 0 -0.2 0 -0.3 0 -0.4 0 -0.5 0 -0.6 0 -0.7 0 -0.8 0 -0.9 0 -1 0.09999999999999999 -1 0.2 -1 0.3 -1 0.4 -1 0.5 -0.915 0.6 -0.7474999999999999 0.6 -0.665 0.6 -0.5825 0.6 -0.08500000000000001 0.6 -0 0.5 -0 0.4 -0 0.3 -0 0.2 -0 0.09999999999999998 -0.83 0.6666666666666666 -0.83 0.7333333333333334 -0.7357142857142857 0.8 -0.6414285714285715 0.8 -0.5471428571428572 0.8 -0.4528571428571429 0.8 -0.3585714285714286 0.8 -0.2642857142857143 0.8 -0.17 0.7333333333333334 -0.17 0.6666666666666667 -0.55 0.2 -0.6 0.25 -0.6 0.35 -0.55 0.4 -0.45 0.4 -0.4 0.35 -0.4 0.25 -0.45 0.2 -0.4175 0.6 -0.335 0.6 -0.2525000000000001 0.6 -0.1830860259018252 0.2575705887159407 -0.8214251519279839 0.3400910341194828 -0.7367356972768339 0.1545851641648327 -0.2747763926099513 0.4393279804701981 -0.3380125422979773 0.1490600318288089 -0.6665431110538135 0.4469555482086437 -0.296713959802076 0.6824750976249487 -0.6823887570446404 0.6988381196783868 -0.4119540982524374 0.7139680155366132 -0.5440762920546971 0.6844981967009994 -0.5488863849623231 0.08065734809935345 -0.4593284290899015 0.5303257942069471 -0.04745577342231752 0.04558193320280449 -0.9559081045112219 0.04706196837962208 -0.05571697787757442 0.5345441974182679 -0.9416966513970901 0.5479893966941878 -0.1309631118646534 0.4236995315406518 -0.8774128939624196 0.1557894847622768 -0.1554747804750385 0.1294581622541261 -0.8486232790977517 0.4679895901706703 -0.6534945367503546 0.09649470230789628 -0.3483977396498218 0.4781934195718026 -0.2483039178930304 0.335106363798257 -0.7530934478381617 0.2592989646850651 -0.7295364126041498 0.3701003238893228 -0.2683233659762636 0.2447136364527485 -0.9143800070052596 0.3450037074593404 -0.08822015826359252 0.2520686350157191 -0.4537059191295885 0.0741756455143039 -0.5413507019951419 0.5280898867902438 -0.7096450191787081 0.527961160509049 -0.6159682017017379 0.6625663124322685 -0.3592388637053299 0.07610221596732396 -0.765108404514371 0.6997816378729095 -0.4717177437761203 0.6663200430010416 -0.4854679354770992 0.7329870341912208 -0.3877365265315627 0.1908548279285711 -0.6099395334451564 0.4066137391340408 -0.2306877192446715 0.6964953882347311 -0.3598161445533513 0.6657912069407611 -0.3382100905575304 0.732458120815991 -0.1406562191310727 0.3365009009737865 -0.8627012941703919 0.2566782703816746 -0.2195359644497203 0.524181436329583 -0.2504057789554006 0.09656440959640891 -0.8609688932847446 0.07036423491723381 -0.0792332959701036 0.1598167751696082 -0.6633419637279835 0.2041432332102987 -0.7388720146622824 0.07177243733659958 -0.7591410509968218 0.4592275943922892 -0.9241864378600493 0.4352795696806243 -0.3282800786487374 0.3684755144155539 -0.6245001642495908 0.5273679175283577 -0.2130990814013797 0.1830560609252357 -0.5860181519062729 0.1635732828628243 -0.6061461985296173 0.729233213750633 -0.8749038211558559 0.5412768202367876 -0.06388571113668819 0.4576480010754793 -0.1589795129567917 0.06144175630803391 -0.9474526566112427 0.1539503712832068 -0.4177070399492428 0.4686211281102174 -0.4145875508081387 0.1396001690291554 -0.5820204934211082 0.4600303136127304 -0.6511979703975962 0.3749576639917713 -0.3372051416899794 0.2181481953330509 -0.3797444568480455 0.5346313255081716 -0.1963130627907262 0.3991956927382116 -0.1304008926063841 0.5145372655094962 -0.8068811529542688 0.1870998775716188 -0.7950607772011259 0.5328892529726835 -0.3014379962113258 0.5295700784399427 -0.936043535437924 0.2249829012752652 -0.06786843512715206 0.3723100832440311 -0.3696426508429986 0.4176130572447811 -0.8035652723323531 0.1069250059276683 -0.2809344756318412 0.1774925274550569 -0.1433346549100507 0.1960253034218661 -0.0900292624482301 0.08257958227890218 -0.8629115739649835 0.3994504619777429 -0.8044908795850402 0.4077054699969835 -0.9235971226529696 0.08805709002620099 -0.9180779212435105 0.4985449668591332 -0.9284411152026488 0.2819128596134682 -0.07377871769355998 0.3152655928916893 -0.1898942752170752 0.4604566556725514 -27 3 74 -47 5 58 -28 4 115 -58 5 102 -29 4 38 -22 2 72 -52 11 119 -50 10 122 -39 7 40 -69 9 87 -124 57 129 -71 14 136 -48 9 113 -104 22 139 -17 18 87 -51 50 96 -18 19 69 -79 20 107 -20 21 107 -21 22 104 -23 24 118 -25 26 85 -85 26 109 -54 12 123 -70 11 88 -74 28 115 -31 13 88 -37 1 71 -32 6 73 -1 14 71 -55 54 95 -14 15 117 -105 37 136 -102 5 126 -73 33 116 -33 34 116 -30 29 66 -31 30 90 -56 13 93 -66 29 92 -29 38 92 -13 31 68 -38 39 92 -45 8 46 -68 42 94 -89 30 111 -68 31 90 -66 41 114 -116 34 131 -43 44 67 -69 19 79 -2 23 72 -19 20 79 -115 4 128 -4 29 128 -67 44 99 -65 45 97 -15 16 103 -16 17 91 -45 46 97 -6 33 73 -57 56 98 -53 52 132 -81 12 110 -12 53 110 -87 9 120 -13 56 70 -30 31 111 -88 11 121 -82 10 106 -72 23 139 -70 56 124 -5 32 126 -9 55 120 -81 59 84 -11 51 121 -82 60 83 -58 57 65 -46 47 97 -40 41 66 -42 43 94 -65 57 98 -44 45 99 -41 42 114 -67 56 93 -49 48 113 -10 49 106 -56 57 124 -57 58 129 -86 36 105 -91 63 103 -118 24 130 -26 27 109 -35 36 86 -36 37 105 -3 28 74 -29 30 89 -86 59 100 -32 73 126 -85 60 101 -107 21 133 -84 59 112 -112 59 135 -96 64 121 -83 60 138 -127 61 133 -106 49 113 -81 62 125 -110 53 132 -80 62 132 -125 62 143 -79 61 106 -82 61 127 -137 78 138 -10 82 83 -103 63 134 -12 81 84 -104 76 133 -109 27 140 -100 81 125 -37 71 136 -95 54 123 -18 69 87 -96 50 122 -13 70 88 -89 64 108 -109 78 137 -30 66 90 -90 66 114 -95 63 120 -17 87 91 -39 40 92 -40 66 92 -43 67 94 -13 68 93 -93 68 94 -67 93 94 -123 84 134 -91 87 120 -83 64 122 -31 88 111 -47 58 97 -58 65 97 -45 65 99 -56 67 98 -98 67 99 -65 98 99 -59 81 100 -34 35 131 -60 82 101 -24 25 130 -116 75 126 -102 62 129 -105 77 135 -16 91 103 -22 72 139 -101 76 130 -117 77 136 -59 86 135 -9 69 113 -61 82 106 -61 79 107 -21 104 133 -64 83 108 -108 78 128 -27 74 140 -60 85 137 -11 70 119 -62 81 110 -64 89 111 -111 88 121 -112 103 134 -77 103 112 -69 79 113 -79 106 113 -42 68 114 -68 90 114 -29 89 128 -115 78 140 -100 75 131 -131 35 142 -103 77 117 -15 103 117 -130 25 141 -118 76 139 -119 70 124 -119 80 132 -63 91 120 -55 95 120 -51 96 121 -64 111 121 -10 83 122 -64 96 122 -12 84 123 -63 95 123 -62 80 129 -80 119 124 -75 100 125 -126 75 143 -62 102 143 -73 116 126 -101 82 127 -76 101 127 -89 108 128 -78 115 128 -58 102 129 -80 124 129 -25 85 141 -76 118 130 -35 86 142 -75 116 131 -62 110 132 -52 119 132 -61 107 133 -76 127 133 -84 112 134 -63 123 134 -86 105 135 -77 112 135 -77 105 136 -14 117 136 -108 83 138 -85 109 137 -78 108 138 -60 137 138 -76 104 139 -23 118 139 -78 109 140 -74 115 140 -85 101 141 -101 130 141 -86 100 142 -100 131 142 -75 125 143 -102 126 143 -59 -1 14 -14 15 -15 16 -16 17 -17 18 -18 19 -19 20 -20 21 -21 22 -22 2 -2 23 -23 24 -24 25 -25 26 -26 27 -27 3 -3 28 -28 4 -4 29 -29 30 -30 31 -31 13 -5 32 -32 6 -6 33 -33 34 -34 35 -35 36 -36 37 -37 1 -4 38 -38 39 -39 7 -7 40 -40 41 -41 42 -42 43 -43 44 -44 45 -45 8 -8 46 -46 47 -47 5 -9 48 -48 49 -49 10 -10 50 -50 51 -51 11 -11 52 -52 53 -53 12 -12 54 -54 55 -55 9 -13 56 -56 57 -57 58 -58 5 diff --git a/ex3/seq/generate_mesh/save_mesh2_mini.m b/ex3/seq/generate_mesh/save_mesh2_mini.m deleted file mode 100644 index 18b3864..0000000 --- a/ex3/seq/generate_mesh/save_mesh2_mini.m +++ /dev/null @@ -1,35 +0,0 @@ -function save_mesh2_mini( xc, ia, e, basename) -% Save the 3D triangular mesh in the minimal way (only coordinates and vertex connectivity) -% in binary file. -% The indexing in the connectivity is changed to C-style (starts with 0) -% -% coordinates xc: [2][nnode] -% connectivity ia: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain -% basename: file name without extension -% data from -% output from -% -fname = [basename, '.bin']; -offset = 1; % index difference from C to Matlab - -nnode = size(xc,2); -ndim = size(xc,1); -nelem = size(ia,2); -nvert_e = 3; - -fileID = fopen(fname,'w'); -fwrite(fileID, nnode, 'int'); % number of nodes -fwrite(fileID, ndim, 'int'); % space dimension -fwrite(fileID, nelem, 'int'); % number of elements -fwrite(fileID, nvert_e, 'int'); % number of vertices per element - -fwrite(fileID, xc(:), 'double'); % coordinates -tmp=ia(1:3,:)-offset; -fwrite(fileID, tmp(:), 'double'); % connectivity - -end diff --git a/ex3/seq/generate_mesh/square.m b/ex3/seq/generate_mesh/square.m deleted file mode 100644 index 28f5829..0000000 --- a/ex3/seq/generate_mesh/square.m +++ /dev/null @@ -1,43 +0,0 @@ -% Square: -% flatpak run org.octave.Octave -% or -% octave --no-window-system --no-gui -qf - -clear all -clc -% %% L-shape -% g=[2 0 2 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right -% 2 2 2 0 1 1 0; -% 2 2 1 1 0.5 1 0; -% 2 1 1 0.5 2 1 0; -% 2 1 0 2 2 1 0; -% 2 0 0 2 0 1 0]'; - -%% square -g=[2 0 1 0 0 1 0; % #vertices,v_1x, v_2x, v_1y, v_2y, subdomain_left, subdomain_right - 2 1 1 0 1 1 0; - 2 1 0 1 1 1 0; - 2 0 0 1 0 1 0]'; - -[p,e,t] = initmesh(g,'hmax',0.01); -%[p,e,t] = initmesh(g,'hmax',0.6); -pdemesh(p,e,t) -% pdemesh(p,e,t,"NodeLabels","on") - -%% GH -% output from -% -% coordinates p: [2][nnode] -% connectivity t: [4][nelem] with t(4,:) are the subdomain numbers -% edges e: [7][nedges] boundary edges -% e([1,2],:) - start/end vertex of edge -% e([3,4],:) - start/end values -% e(5,:) - segment number -% e([6,7],:) - left/right subdomain - -ascii_write_mesh( p, t, e, mfilename); - - - -% tmp=t(1:3,:) - diff --git a/ex3/seq/generate_mesh/square.txt b/ex3/seq/generate_mesh/square.txt deleted file mode 100644 index 789dc39..0000000 --- a/ex3/seq/generate_mesh/square.txt +++ /dev/null @@ -1,30 +0,0 @@ -9 -2 -8 -3 -0 0 -1 0 -1 1 -0 1 -0.5 0 -1 0.5 -0.5 1 -0 0.5 -0.5 0.5 -8 1 9 -5 2 9 -6 3 9 -7 4 9 -1 5 9 -2 6 9 -3 7 9 -4 8 9 -8 -1 5 -5 2 -2 6 -6 3 -3 7 -7 4 -4 8 -8 1 diff --git a/ex3/seq/generate_mesh/square_06.jpg b/ex3/seq/generate_mesh/square_06.jpg deleted file mode 100644 index db7c214..0000000 Binary files a/ex3/seq/generate_mesh/square_06.jpg and /dev/null differ diff --git a/ex3/seq/generate_mesh/square_06_0.txt b/ex3/seq/generate_mesh/square_06_0.txt deleted file mode 100644 index 789dc39..0000000 --- a/ex3/seq/generate_mesh/square_06_0.txt +++ /dev/null @@ -1,30 +0,0 @@ -9 -2 -8 -3 -0 0 -1 0 -1 1 -0 1 -0.5 0 -1 0.5 -0.5 1 -0 0.5 -0.5 0.5 -8 1 9 -5 2 9 -6 3 9 -7 4 9 -1 5 9 -2 6 9 -3 7 9 -4 8 9 -8 -1 5 -5 2 -2 6 -6 3 -3 7 -7 4 -4 8 -8 1 diff --git a/ex3/seq/generate_mesh/visualize_results.m b/ex3/seq/generate_mesh/visualize_results.m deleted file mode 100644 index e40da61..0000000 --- a/ex3/seq/generate_mesh/visualize_results.m +++ /dev/null @@ -1,20 +0,0 @@ -%% Visualize results -% -% flatpak run org.octave.Octave -% or -% octave --no-window-system --no-gui -qf -% -% or -% matlab -nosplash < - -clear all -clc - -%% -fname = 'uv.txt'; - -[xc,ia,v] = ascii_read_meshvector(fname); - -h = trisurf(ia, xc(:,1), xc(:,2), v); - -waitfor(h) % wait for closing the figure \ No newline at end of file diff --git a/ex3/seq/jacobi_oo_stl/Doxyfile b/ex3/seq/jacobi_oo_stl/Doxyfile deleted file mode 100644 index f7a3ef7..0000000 --- a/ex3/seq/jacobi_oo_stl/Doxyfile +++ /dev/null @@ -1,2877 +0,0 @@ -# Doxyfile 1.10.0 - -# This file describes the settings to be used by the documentation system -# doxygen (www.doxygen.org) for a project. -# -# All text after a double hash (##) is considered a comment and is placed in -# front of the TAG it is preceding. -# -# All text after a single hash (#) is considered a comment and will be ignored. -# The format is: -# TAG = value [value, ...] -# For lists, items can also be appended using: -# TAG += value [value, ...] -# Values that contain spaces should be placed between quotes (\" \"). -# -# Note: -# -# Use doxygen to compare the used configuration file with the template -# configuration file: -# doxygen -x [configFile] -# Use doxygen to compare the used configuration file with the template -# configuration file without replacing the environment variables or CMake type -# replacement variables: -# doxygen -x_noenv [configFile] - -#--------------------------------------------------------------------------- -# Project related configuration options -#--------------------------------------------------------------------------- - -# This tag specifies the encoding used for all characters in the configuration -# file that follow. The default is UTF-8 which is also the encoding used for all -# text before the first occurrence of this tag. Doxygen uses libiconv (or the -# iconv built into libc) for the transcoding. See -# https://www.gnu.org/software/libiconv/ for the list of possible encodings. -# The default value is: UTF-8. - -DOXYFILE_ENCODING = UTF-8 - -# The PROJECT_NAME tag is a single word (or a sequence of words surrounded by -# double-quotes, unless you are using Doxywizard) that should identify the -# project for which the documentation is generated. This name is used in the -# title of most generated pages and in a few other places. -# The default value is: My Project. - -PROJECT_NAME = jacobi_oo_STL - -# The PROJECT_NUMBER tag can be used to enter a project or revision number. This -# could be handy for archiving the generated documentation or if some version -# control system is used. - -PROJECT_NUMBER = - -# Using the PROJECT_BRIEF tag one can provide an optional one line description -# for a project that appears at the top of each page and should give viewer a -# quick idea about the purpose of the project. Keep the description short. - -PROJECT_BRIEF = - -# With the PROJECT_LOGO tag one can specify a logo or an icon that is included -# in the documentation. The maximum height of the logo should not exceed 55 -# pixels and the maximum width should not exceed 200 pixels. Doxygen will copy -# the logo to the output directory. - -PROJECT_LOGO = - -# With the PROJECT_ICON tag one can specify an icon that is included in the tabs -# when the HTML document is shown. Doxygen will copy the logo to the output -# directory. - -PROJECT_ICON = - -# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path -# into which the generated documentation will be written. If a relative path is -# entered, it will be relative to the location where doxygen was started. If -# left blank the current directory will be used. - -OUTPUT_DIRECTORY = - -# If the CREATE_SUBDIRS tag is set to YES then doxygen will create up to 4096 -# sub-directories (in 2 levels) under the output directory of each output format -# and will distribute the generated files over these directories. Enabling this -# option can be useful when feeding doxygen a huge amount of source files, where -# putting all generated files in the same directory would otherwise causes -# performance problems for the file system. Adapt CREATE_SUBDIRS_LEVEL to -# control the number of sub-directories. -# The default value is: NO. - -CREATE_SUBDIRS = NO - -# Controls the number of sub-directories that will be created when -# CREATE_SUBDIRS tag is set to YES. Level 0 represents 16 directories, and every -# level increment doubles the number of directories, resulting in 4096 -# directories at level 8 which is the default and also the maximum value. The -# sub-directories are organized in 2 levels, the first level always has a fixed -# number of 16 directories. -# Minimum value: 0, maximum value: 8, default value: 8. -# This tag requires that the tag CREATE_SUBDIRS is set to YES. - -CREATE_SUBDIRS_LEVEL = 8 - -# If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII -# characters to appear in the names of generated files. If set to NO, non-ASCII -# characters will be escaped, for example _xE3_x81_x84 will be used for Unicode -# U+3044. -# The default value is: NO. - -ALLOW_UNICODE_NAMES = NO - -# The OUTPUT_LANGUAGE tag is used to specify the language in which all -# documentation generated by doxygen is written. Doxygen will use this -# information to generate all constant output in the proper language. -# Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Bulgarian, -# Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish, Dutch, English -# (United States), Esperanto, Farsi (Persian), Finnish, French, German, Greek, -# Hindi, Hungarian, Indonesian, Italian, Japanese, Japanese-en (Japanese with -# English messages), Korean, Korean-en (Korean with English messages), Latvian, -# Lithuanian, Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, -# Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, -# Swedish, Turkish, Ukrainian and Vietnamese. -# The default value is: English. - -OUTPUT_LANGUAGE = English - -# If the BRIEF_MEMBER_DESC tag is set to YES, doxygen will include brief member -# descriptions after the members that are listed in the file and class -# documentation (similar to Javadoc). Set to NO to disable this. -# The default value is: YES. - -BRIEF_MEMBER_DESC = YES - -# If the REPEAT_BRIEF tag is set to YES, doxygen will prepend the brief -# description of a member or function before the detailed description -# -# Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the -# brief descriptions will be completely suppressed. -# The default value is: YES. - -REPEAT_BRIEF = YES - -# This tag implements a quasi-intelligent brief description abbreviator that is -# used to form the text in various listings. Each string in this list, if found -# as the leading text of the brief description, will be stripped from the text -# and the result, after processing the whole list, is used as the annotated -# text. Otherwise, the brief description is used as-is. If left blank, the -# following values are used ($name is automatically replaced with the name of -# the entity):The $name class, The $name widget, The $name file, is, provides, -# specifies, contains, represents, a, an and the. - -ABBREVIATE_BRIEF = "The $name class" \ - "The $name widget" \ - "The $name file" \ - is \ - provides \ - specifies \ - contains \ - represents \ - a \ - an \ - the - -# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then -# doxygen will generate a detailed section even if there is only a brief -# description. -# The default value is: NO. - -ALWAYS_DETAILED_SEC = NO - -# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all -# inherited members of a class in the documentation of that class as if those -# members were ordinary class members. Constructors, destructors and assignment -# operators of the base classes will not be shown. -# The default value is: NO. - -INLINE_INHERITED_MEMB = NO - -# If the FULL_PATH_NAMES tag is set to YES, doxygen will prepend the full path -# before files name in the file list and in the header files. If set to NO the -# shortest path that makes the file name unique will be used -# The default value is: YES. - -FULL_PATH_NAMES = YES - -# The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. -# Stripping is only done if one of the specified strings matches the left-hand -# part of the path. The tag can be used to show relative paths in the file list. -# If left blank the directory from which doxygen is run is used as the path to -# strip. -# -# Note that you can specify absolute paths here, but also relative paths, which -# will be relative from the directory where doxygen is started. -# This tag requires that the tag FULL_PATH_NAMES is set to YES. - -STRIP_FROM_PATH = - -# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the -# path mentioned in the documentation of a class, which tells the reader which -# header file to include in order to use a class. If left blank only the name of -# the header file containing the class definition is used. Otherwise one should -# specify the list of include paths that are normally passed to the compiler -# using the -I flag. - -STRIP_FROM_INC_PATH = - -# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but -# less readable) file names. This can be useful is your file systems doesn't -# support long names like on DOS, Mac, or CD-ROM. -# The default value is: NO. - -SHORT_NAMES = NO - -# If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the -# first line (until the first dot) of a Javadoc-style comment as the brief -# description. If set to NO, the Javadoc-style will behave just like regular Qt- -# style comments (thus requiring an explicit @brief command for a brief -# description.) -# The default value is: NO. - -JAVADOC_AUTOBRIEF = NO - -# If the JAVADOC_BANNER tag is set to YES then doxygen will interpret a line -# such as -# /*************** -# as being the beginning of a Javadoc-style comment "banner". If set to NO, the -# Javadoc-style will behave just like regular comments and it will not be -# interpreted by doxygen. -# The default value is: NO. - -JAVADOC_BANNER = NO - -# If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first -# line (until the first dot) of a Qt-style comment as the brief description. If -# set to NO, the Qt-style will behave just like regular Qt-style comments (thus -# requiring an explicit \brief command for a brief description.) -# The default value is: NO. - -QT_AUTOBRIEF = NO - -# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a -# multi-line C++ special comment block (i.e. a block of //! or /// comments) as -# a brief description. This used to be the default behavior. The new default is -# to treat a multi-line C++ comment block as a detailed description. Set this -# tag to YES if you prefer the old behavior instead. -# -# Note that setting this tag to YES also means that rational rose comments are -# not recognized any more. -# The default value is: NO. - -MULTILINE_CPP_IS_BRIEF = NO - -# By default Python docstrings are displayed as preformatted text and doxygen's -# special commands cannot be used. By setting PYTHON_DOCSTRING to NO the -# doxygen's special commands can be used and the contents of the docstring -# documentation blocks is shown as doxygen documentation. -# The default value is: YES. - -PYTHON_DOCSTRING = YES - -# If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the -# documentation from any documented member that it re-implements. -# The default value is: YES. - -INHERIT_DOCS = YES - -# If the SEPARATE_MEMBER_PAGES tag is set to YES then doxygen will produce a new -# page for each member. If set to NO, the documentation of a member will be part -# of the file/class/namespace that contains it. -# The default value is: NO. - -SEPARATE_MEMBER_PAGES = NO - -# The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen -# uses this value to replace tabs by spaces in code fragments. -# Minimum value: 1, maximum value: 16, default value: 4. - -TAB_SIZE = 8 - -# This tag can be used to specify a number of aliases that act as commands in -# the documentation. An alias has the form: -# name=value -# For example adding -# "sideeffect=@par Side Effects:^^" -# will allow you to put the command \sideeffect (or @sideeffect) in the -# documentation, which will result in a user-defined paragraph with heading -# "Side Effects:". Note that you cannot put \n's in the value part of an alias -# to insert newlines (in the resulting output). You can put ^^ in the value part -# of an alias to insert a newline as if a physical newline was in the original -# file. When you need a literal { or } or , in the value part of an alias you -# have to escape them by means of a backslash (\), this can lead to conflicts -# with the commands \{ and \} for these it is advised to use the version @{ and -# @} or use a double escape (\\{ and \\}) - -ALIASES = - -# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources -# only. Doxygen will then generate output that is more tailored for C. For -# instance, some of the names that are used will be different. The list of all -# members will be omitted, etc. -# The default value is: NO. - -OPTIMIZE_OUTPUT_FOR_C = NO - -# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or -# Python sources only. Doxygen will then generate output that is more tailored -# for that language. For instance, namespaces will be presented as packages, -# qualified scopes will look different, etc. -# The default value is: NO. - -OPTIMIZE_OUTPUT_JAVA = NO - -# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran -# sources. Doxygen will then generate output that is tailored for Fortran. -# The default value is: NO. - -OPTIMIZE_FOR_FORTRAN = NO - -# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL -# sources. Doxygen will then generate output that is tailored for VHDL. -# The default value is: NO. - -OPTIMIZE_OUTPUT_VHDL = NO - -# Set the OPTIMIZE_OUTPUT_SLICE tag to YES if your project consists of Slice -# sources only. Doxygen will then generate output that is more tailored for that -# language. For instance, namespaces will be presented as modules, types will be -# separated into more groups, etc. -# The default value is: NO. - -OPTIMIZE_OUTPUT_SLICE = NO - -# Doxygen selects the parser to use depending on the extension of the files it -# parses. With this tag you can assign which parser to use for a given -# extension. Doxygen has a built-in mapping, but you can override or extend it -# using this tag. The format is ext=language, where ext is a file extension, and -# language is one of the parsers supported by doxygen: IDL, Java, JavaScript, -# Csharp (C#), C, C++, Lex, D, PHP, md (Markdown), Objective-C, Python, Slice, -# VHDL, Fortran (fixed format Fortran: FortranFixed, free formatted Fortran: -# FortranFree, unknown formatted Fortran: Fortran. In the later case the parser -# tries to guess whether the code is fixed or free formatted code, this is the -# default for Fortran type files). For instance to make doxygen treat .inc files -# as Fortran files (default is PHP), and .f files as C (default is Fortran), -# use: inc=Fortran f=C. -# -# Note: For files without extension you can use no_extension as a placeholder. -# -# Note that for custom extensions you also need to set FILE_PATTERNS otherwise -# the files are not read by doxygen. When specifying no_extension you should add -# * to the FILE_PATTERNS. -# -# Note see also the list of default file extension mappings. - -EXTENSION_MAPPING = - -# If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments -# according to the Markdown format, which allows for more readable -# documentation. See https://daringfireball.net/projects/markdown/ for details. -# The output of markdown processing is further processed by doxygen, so you can -# mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in -# case of backward compatibilities issues. -# The default value is: YES. - -MARKDOWN_SUPPORT = YES - -# When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up -# to that level are automatically included in the table of contents, even if -# they do not have an id attribute. -# Note: This feature currently applies only to Markdown headings. -# Minimum value: 0, maximum value: 99, default value: 5. -# This tag requires that the tag MARKDOWN_SUPPORT is set to YES. - -TOC_INCLUDE_HEADINGS = 5 - -# The MARKDOWN_ID_STYLE tag can be used to specify the algorithm used to -# generate identifiers for the Markdown headings. Note: Every identifier is -# unique. -# Possible values are: DOXYGEN use a fixed 'autotoc_md' string followed by a -# sequence number starting at 0 and GITHUB use the lower case version of title -# with any whitespace replaced by '-' and punctuation characters removed. -# The default value is: DOXYGEN. -# This tag requires that the tag MARKDOWN_SUPPORT is set to YES. - -MARKDOWN_ID_STYLE = DOXYGEN - -# When enabled doxygen tries to link words that correspond to documented -# classes, or namespaces to their corresponding documentation. Such a link can -# be prevented in individual cases by putting a % sign in front of the word or -# globally by setting AUTOLINK_SUPPORT to NO. -# The default value is: YES. - -AUTOLINK_SUPPORT = YES - -# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want -# to include (a tag file for) the STL sources as input, then you should set this -# tag to YES in order to let doxygen match functions declarations and -# definitions whose arguments contain STL classes (e.g. func(std::string); -# versus func(std::string) {}). This also make the inheritance and collaboration -# diagrams that involve STL classes more complete and accurate. -# The default value is: NO. - -BUILTIN_STL_SUPPORT = NO - -# If you use Microsoft's C++/CLI language, you should set this option to YES to -# enable parsing support. -# The default value is: NO. - -CPP_CLI_SUPPORT = NO - -# Set the SIP_SUPPORT tag to YES if your project consists of sip (see: -# https://www.riverbankcomputing.com/software/sip/intro) sources only. Doxygen -# will parse them like normal C++ but will assume all classes use public instead -# of private inheritance when no explicit protection keyword is present. -# The default value is: NO. - -SIP_SUPPORT = NO - -# For Microsoft's IDL there are propget and propput attributes to indicate -# getter and setter methods for a property. Setting this option to YES will make -# doxygen to replace the get and set methods by a property in the documentation. -# This will only work if the methods are indeed getting or setting a simple -# type. If this is not the case, or you want to show the methods anyway, you -# should set this option to NO. -# The default value is: YES. - -IDL_PROPERTY_SUPPORT = YES - -# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC -# tag is set to YES then doxygen will reuse the documentation of the first -# member in the group (if any) for the other members of the group. By default -# all members of a group must be documented explicitly. -# The default value is: NO. - -DISTRIBUTE_GROUP_DOC = NO - -# If one adds a struct or class to a group and this option is enabled, then also -# any nested class or struct is added to the same group. By default this option -# is disabled and one has to add nested compounds explicitly via \ingroup. -# The default value is: NO. - -GROUP_NESTED_COMPOUNDS = NO - -# Set the SUBGROUPING tag to YES to allow class member groups of the same type -# (for instance a group of public functions) to be put as a subgroup of that -# type (e.g. under the Public Functions section). Set it to NO to prevent -# subgrouping. Alternatively, this can be done per class using the -# \nosubgrouping command. -# The default value is: YES. - -SUBGROUPING = YES - -# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions -# are shown inside the group in which they are included (e.g. using \ingroup) -# instead of on a separate page (for HTML and Man pages) or section (for LaTeX -# and RTF). -# -# Note that this feature does not work in combination with -# SEPARATE_MEMBER_PAGES. -# The default value is: NO. - -INLINE_GROUPED_CLASSES = NO - -# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions -# with only public data fields or simple typedef fields will be shown inline in -# the documentation of the scope in which they are defined (i.e. file, -# namespace, or group documentation), provided this scope is documented. If set -# to NO, structs, classes, and unions are shown on a separate page (for HTML and -# Man pages) or section (for LaTeX and RTF). -# The default value is: NO. - -INLINE_SIMPLE_STRUCTS = NO - -# When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or -# enum is documented as struct, union, or enum with the name of the typedef. So -# typedef struct TypeS {} TypeT, will appear in the documentation as a struct -# with name TypeT. When disabled the typedef will appear as a member of a file, -# namespace, or class. And the struct will be named TypeS. This can typically be -# useful for C code in case the coding convention dictates that all compound -# types are typedef'ed and only the typedef is referenced, never the tag name. -# The default value is: NO. - -TYPEDEF_HIDES_STRUCT = NO - -# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This -# cache is used to resolve symbols given their name and scope. Since this can be -# an expensive process and often the same symbol appears multiple times in the -# code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small -# doxygen will become slower. If the cache is too large, memory is wasted. The -# cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range -# is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 -# symbols. At the end of a run doxygen will report the cache usage and suggest -# the optimal cache size from a speed point of view. -# Minimum value: 0, maximum value: 9, default value: 0. - -LOOKUP_CACHE_SIZE = 0 - -# The NUM_PROC_THREADS specifies the number of threads doxygen is allowed to use -# during processing. When set to 0 doxygen will based this on the number of -# cores available in the system. You can set it explicitly to a value larger -# than 0 to get more control over the balance between CPU load and processing -# speed. At this moment only the input processing can be done using multiple -# threads. Since this is still an experimental feature the default is set to 1, -# which effectively disables parallel processing. Please report any issues you -# encounter. Generating dot graphs in parallel is controlled by the -# DOT_NUM_THREADS setting. -# Minimum value: 0, maximum value: 32, default value: 1. - -NUM_PROC_THREADS = 1 - -# If the TIMESTAMP tag is set different from NO then each generated page will -# contain the date or date and time when the page was generated. Setting this to -# NO can help when comparing the output of multiple runs. -# Possible values are: YES, NO, DATETIME and DATE. -# The default value is: NO. - -TIMESTAMP = YES - -#--------------------------------------------------------------------------- -# Build related configuration options -#--------------------------------------------------------------------------- - -# If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in -# documentation are documented, even if no documentation was available. Private -# class members and static file members will be hidden unless the -# EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. -# Note: This will also disable the warnings about undocumented members that are -# normally produced when WARNINGS is set to YES. -# The default value is: NO. - -EXTRACT_ALL = YES - -# If the EXTRACT_PRIVATE tag is set to YES, all private members of a class will -# be included in the documentation. -# The default value is: NO. - -EXTRACT_PRIVATE = NO - -# If the EXTRACT_PRIV_VIRTUAL tag is set to YES, documented private virtual -# methods of a class will be included in the documentation. -# The default value is: NO. - -EXTRACT_PRIV_VIRTUAL = NO - -# If the EXTRACT_PACKAGE tag is set to YES, all members with package or internal -# scope will be included in the documentation. -# The default value is: NO. - -EXTRACT_PACKAGE = NO - -# If the EXTRACT_STATIC tag is set to YES, all static members of a file will be -# included in the documentation. -# The default value is: NO. - -EXTRACT_STATIC = NO - -# If the EXTRACT_LOCAL_CLASSES tag is set to YES, classes (and structs) defined -# locally in source files will be included in the documentation. If set to NO, -# only classes defined in header files are included. Does not have any effect -# for Java sources. -# The default value is: YES. - -EXTRACT_LOCAL_CLASSES = YES - -# This flag is only useful for Objective-C code. If set to YES, local methods, -# which are defined in the implementation section but not in the interface are -# included in the documentation. If set to NO, only methods in the interface are -# included. -# The default value is: NO. - -EXTRACT_LOCAL_METHODS = NO - -# If this flag is set to YES, the members of anonymous namespaces will be -# extracted and appear in the documentation as a namespace called -# 'anonymous_namespace{file}', where file will be replaced with the base name of -# the file that contains the anonymous namespace. By default anonymous namespace -# are hidden. -# The default value is: NO. - -EXTRACT_ANON_NSPACES = NO - -# If this flag is set to YES, the name of an unnamed parameter in a declaration -# will be determined by the corresponding definition. By default unnamed -# parameters remain unnamed in the output. -# The default value is: YES. - -RESOLVE_UNNAMED_PARAMS = YES - -# If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all -# undocumented members inside documented classes or files. If set to NO these -# members will be included in the various overviews, but no documentation -# section is generated. This option has no effect if EXTRACT_ALL is enabled. -# The default value is: NO. - -HIDE_UNDOC_MEMBERS = NO - -# If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all -# undocumented classes that are normally visible in the class hierarchy. If set -# to NO, these classes will be included in the various overviews. This option -# will also hide undocumented C++ concepts if enabled. This option has no effect -# if EXTRACT_ALL is enabled. -# The default value is: NO. - -HIDE_UNDOC_CLASSES = NO - -# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend -# declarations. If set to NO, these declarations will be included in the -# documentation. -# The default value is: NO. - -HIDE_FRIEND_COMPOUNDS = NO - -# If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any -# documentation blocks found inside the body of a function. If set to NO, these -# blocks will be appended to the function's detailed documentation block. -# The default value is: NO. - -HIDE_IN_BODY_DOCS = NO - -# The INTERNAL_DOCS tag determines if documentation that is typed after a -# \internal command is included. If the tag is set to NO then the documentation -# will be excluded. Set it to YES to include the internal documentation. -# The default value is: NO. - -INTERNAL_DOCS = NO - -# With the correct setting of option CASE_SENSE_NAMES doxygen will better be -# able to match the capabilities of the underlying filesystem. In case the -# filesystem is case sensitive (i.e. it supports files in the same directory -# whose names only differ in casing), the option must be set to YES to properly -# deal with such files in case they appear in the input. For filesystems that -# are not case sensitive the option should be set to NO to properly deal with -# output files written for symbols that only differ in casing, such as for two -# classes, one named CLASS and the other named Class, and to also support -# references to files without having to specify the exact matching casing. On -# Windows (including Cygwin) and MacOS, users should typically set this option -# to NO, whereas on Linux or other Unix flavors it should typically be set to -# YES. -# Possible values are: SYSTEM, NO and YES. -# The default value is: SYSTEM. - -CASE_SENSE_NAMES = NO - -# If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with -# their full class and namespace scopes in the documentation. If set to YES, the -# scope will be hidden. -# The default value is: NO. - -HIDE_SCOPE_NAMES = NO - -# If the HIDE_COMPOUND_REFERENCE tag is set to NO (default) then doxygen will -# append additional text to a page's title, such as Class Reference. If set to -# YES the compound reference will be hidden. -# The default value is: NO. - -HIDE_COMPOUND_REFERENCE= NO - -# If the SHOW_HEADERFILE tag is set to YES then the documentation for a class -# will show which file needs to be included to use the class. -# The default value is: YES. - -SHOW_HEADERFILE = YES - -# If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of -# the files that are included by a file in the documentation of that file. -# The default value is: YES. - -SHOW_INCLUDE_FILES = YES - -# If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each -# grouped member an include statement to the documentation, telling the reader -# which file to include in order to use the member. -# The default value is: NO. - -SHOW_GROUPED_MEMB_INC = NO - -# If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include -# files with double quotes in the documentation rather than with sharp brackets. -# The default value is: NO. - -FORCE_LOCAL_INCLUDES = NO - -# If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the -# documentation for inline members. -# The default value is: YES. - -INLINE_INFO = YES - -# If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the -# (detailed) documentation of file and class members alphabetically by member -# name. If set to NO, the members will appear in declaration order. -# The default value is: YES. - -SORT_MEMBER_DOCS = YES - -# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief -# descriptions of file, namespace and class members alphabetically by member -# name. If set to NO, the members will appear in declaration order. Note that -# this will also influence the order of the classes in the class list. -# The default value is: NO. - -SORT_BRIEF_DOCS = NO - -# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the -# (brief and detailed) documentation of class members so that constructors and -# destructors are listed first. If set to NO the constructors will appear in the -# respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. -# Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief -# member documentation. -# Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting -# detailed member documentation. -# The default value is: NO. - -SORT_MEMBERS_CTORS_1ST = NO - -# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy -# of group names into alphabetical order. If set to NO the group names will -# appear in their defined order. -# The default value is: NO. - -SORT_GROUP_NAMES = NO - -# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by -# fully-qualified names, including namespaces. If set to NO, the class list will -# be sorted only by class name, not including the namespace part. -# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. -# Note: This option applies only to the class list, not to the alphabetical -# list. -# The default value is: NO. - -SORT_BY_SCOPE_NAME = NO - -# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper -# type resolution of all parameters of a function it will reject a match between -# the prototype and the implementation of a member function even if there is -# only one candidate or it is obvious which candidate to choose by doing a -# simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still -# accept a match between prototype and implementation in such cases. -# The default value is: NO. - -STRICT_PROTO_MATCHING = NO - -# The GENERATE_TODOLIST tag can be used to enable (YES) or disable (NO) the todo -# list. This list is created by putting \todo commands in the documentation. -# The default value is: YES. - -GENERATE_TODOLIST = YES - -# The GENERATE_TESTLIST tag can be used to enable (YES) or disable (NO) the test -# list. This list is created by putting \test commands in the documentation. -# The default value is: YES. - -GENERATE_TESTLIST = YES - -# The GENERATE_BUGLIST tag can be used to enable (YES) or disable (NO) the bug -# list. This list is created by putting \bug commands in the documentation. -# The default value is: YES. - -GENERATE_BUGLIST = YES - -# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or disable (NO) -# the deprecated list. This list is created by putting \deprecated commands in -# the documentation. -# The default value is: YES. - -GENERATE_DEPRECATEDLIST= YES - -# The ENABLED_SECTIONS tag can be used to enable conditional documentation -# sections, marked by \if ... \endif and \cond -# ... \endcond blocks. - -ENABLED_SECTIONS = - -# The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the -# initial value of a variable or macro / define can have for it to appear in the -# documentation. If the initializer consists of more lines than specified here -# it will be hidden. Use a value of 0 to hide initializers completely. The -# appearance of the value of individual variables and macros / defines can be -# controlled using \showinitializer or \hideinitializer command in the -# documentation regardless of this setting. -# Minimum value: 0, maximum value: 10000, default value: 30. - -MAX_INITIALIZER_LINES = 30 - -# Set the SHOW_USED_FILES tag to NO to disable the list of files generated at -# the bottom of the documentation of classes and structs. If set to YES, the -# list will mention the files that were used to generate the documentation. -# The default value is: YES. - -SHOW_USED_FILES = YES - -# Set the SHOW_FILES tag to NO to disable the generation of the Files page. This -# will remove the Files entry from the Quick Index and from the Folder Tree View -# (if specified). -# The default value is: YES. - -SHOW_FILES = YES - -# Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces -# page. This will remove the Namespaces entry from the Quick Index and from the -# Folder Tree View (if specified). -# The default value is: YES. - -SHOW_NAMESPACES = YES - -# The FILE_VERSION_FILTER tag can be used to specify a program or script that -# doxygen should invoke to get the current version for each file (typically from -# the version control system). Doxygen will invoke the program by executing (via -# popen()) the command command input-file, where command is the value of the -# FILE_VERSION_FILTER tag, and input-file is the name of an input file provided -# by doxygen. Whatever the program writes to standard output is used as the file -# version. For an example see the documentation. - -FILE_VERSION_FILTER = - -# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed -# by doxygen. The layout file controls the global structure of the generated -# output files in an output format independent way. To create the layout file -# that represents doxygen's defaults, run doxygen with the -l option. You can -# optionally specify a file name after the option, if omitted DoxygenLayout.xml -# will be used as the name of the layout file. See also section "Changing the -# layout of pages" for information. -# -# Note that if you run doxygen from a directory containing a file called -# DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE -# tag is left empty. - -LAYOUT_FILE = - -# The CITE_BIB_FILES tag can be used to specify one or more bib files containing -# the reference definitions. This must be a list of .bib files. The .bib -# extension is automatically appended if omitted. This requires the bibtex tool -# to be installed. See also https://en.wikipedia.org/wiki/BibTeX for more info. -# For LaTeX the style of the bibliography can be controlled using -# LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the -# search path. See also \cite for info how to create references. - -CITE_BIB_FILES = - -#--------------------------------------------------------------------------- -# Configuration options related to warning and progress messages -#--------------------------------------------------------------------------- - -# The QUIET tag can be used to turn on/off the messages that are generated to -# standard output by doxygen. If QUIET is set to YES this implies that the -# messages are off. -# The default value is: NO. - -QUIET = NO - -# The WARNINGS tag can be used to turn on/off the warning messages that are -# generated to standard error (stderr) by doxygen. If WARNINGS is set to YES -# this implies that the warnings are on. -# -# Tip: Turn warnings on while writing the documentation. -# The default value is: YES. - -WARNINGS = YES - -# If the WARN_IF_UNDOCUMENTED tag is set to YES then doxygen will generate -# warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag -# will automatically be disabled. -# The default value is: YES. - -WARN_IF_UNDOCUMENTED = YES - -# If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for -# potential errors in the documentation, such as documenting some parameters in -# a documented function twice, or documenting parameters that don't exist or -# using markup commands wrongly. -# The default value is: YES. - -WARN_IF_DOC_ERROR = YES - -# If WARN_IF_INCOMPLETE_DOC is set to YES, doxygen will warn about incomplete -# function parameter documentation. If set to NO, doxygen will accept that some -# parameters have no documentation without warning. -# The default value is: YES. - -WARN_IF_INCOMPLETE_DOC = YES - -# This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that -# are documented, but have no documentation for their parameters or return -# value. If set to NO, doxygen will only warn about wrong parameter -# documentation, but not about the absence of documentation. If EXTRACT_ALL is -# set to YES then this flag will automatically be disabled. See also -# WARN_IF_INCOMPLETE_DOC -# The default value is: NO. - -WARN_NO_PARAMDOC = NO - -# If WARN_IF_UNDOC_ENUM_VAL option is set to YES, doxygen will warn about -# undocumented enumeration values. If set to NO, doxygen will accept -# undocumented enumeration values. If EXTRACT_ALL is set to YES then this flag -# will automatically be disabled. -# The default value is: NO. - -WARN_IF_UNDOC_ENUM_VAL = NO - -# If the WARN_AS_ERROR tag is set to YES then doxygen will immediately stop when -# a warning is encountered. If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS -# then doxygen will continue running as if WARN_AS_ERROR tag is set to NO, but -# at the end of the doxygen process doxygen will return with a non-zero status. -# If the WARN_AS_ERROR tag is set to FAIL_ON_WARNINGS_PRINT then doxygen behaves -# like FAIL_ON_WARNINGS but in case no WARN_LOGFILE is defined doxygen will not -# write the warning messages in between other messages but write them at the end -# of a run, in case a WARN_LOGFILE is defined the warning messages will be -# besides being in the defined file also be shown at the end of a run, unless -# the WARN_LOGFILE is defined as - i.e. standard output (stdout) in that case -# the behavior will remain as with the setting FAIL_ON_WARNINGS. -# Possible values are: NO, YES, FAIL_ON_WARNINGS and FAIL_ON_WARNINGS_PRINT. -# The default value is: NO. - -WARN_AS_ERROR = NO - -# The WARN_FORMAT tag determines the format of the warning messages that doxygen -# can produce. The string should contain the $file, $line, and $text tags, which -# will be replaced by the file and line number from which the warning originated -# and the warning text. Optionally the format may contain $version, which will -# be replaced by the version of the file (if it could be obtained via -# FILE_VERSION_FILTER) -# See also: WARN_LINE_FORMAT -# The default value is: $file:$line: $text. - -WARN_FORMAT = "$file:$line: $text" - -# In the $text part of the WARN_FORMAT command it is possible that a reference -# to a more specific place is given. To make it easier to jump to this place -# (outside of doxygen) the user can define a custom "cut" / "paste" string. -# Example: -# WARN_LINE_FORMAT = "'vi $file +$line'" -# See also: WARN_FORMAT -# The default value is: at line $line of file $file. - -WARN_LINE_FORMAT = "at line $line of file $file" - -# The WARN_LOGFILE tag can be used to specify a file to which warning and error -# messages should be written. If left blank the output is written to standard -# error (stderr). In case the file specified cannot be opened for writing the -# warning and error messages are written to standard error. When as file - is -# specified the warning and error messages are written to standard output -# (stdout). - -WARN_LOGFILE = - -#--------------------------------------------------------------------------- -# Configuration options related to the input files -#--------------------------------------------------------------------------- - -# The INPUT tag is used to specify the files and/or directories that contain -# documented source files. You may enter file names like myfile.cpp or -# directories like /usr/src/myproject. Separate the files or directories with -# spaces. See also FILE_PATTERNS and EXTENSION_MAPPING -# Note: If this tag is empty the current directory is searched. - -INPUT = - -# This tag can be used to specify the character encoding of the source files -# that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses -# libiconv (or the iconv built into libc) for the transcoding. See the libiconv -# documentation (see: -# https://www.gnu.org/software/libiconv/) for the list of possible encodings. -# See also: INPUT_FILE_ENCODING -# The default value is: UTF-8. - -INPUT_ENCODING = UTF-8 - -# This tag can be used to specify the character encoding of the source files -# that doxygen parses The INPUT_FILE_ENCODING tag can be used to specify -# character encoding on a per file pattern basis. Doxygen will compare the file -# name with each pattern and apply the encoding instead of the default -# INPUT_ENCODING) if there is a match. The character encodings are a list of the -# form: pattern=encoding (like *.php=ISO-8859-1). See cfg_input_encoding -# "INPUT_ENCODING" for further information on supported encodings. - -INPUT_FILE_ENCODING = - -# If the value of the INPUT tag contains directories, you can use the -# FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and -# *.h) to filter out the source-files in the directories. -# -# Note that for custom extensions or not directly supported extensions you also -# need to set EXTENSION_MAPPING for the extension otherwise the files are not -# read by doxygen. -# -# Note the list of default checked file patterns might differ from the list of -# default file extension mappings. -# -# If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cxxm, -# *.cpp, *.cppm, *.ccm, *.c++, *.c++m, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, -# *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, *.h++, *.ixx, *.l, *.cs, *.d, -# *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, *.md, *.mm, *.dox (to -# be provided as doxygen C comment), *.py, *.pyw, *.f90, *.f95, *.f03, *.f08, -# *.f18, *.f, *.for, *.vhd, *.vhdl, *.ucf, *.qsf and *.ice. - -FILE_PATTERNS = *.c \ - *.cc \ - *.cxx \ - *.cpp \ - *.c++ \ - *.d \ - *.java \ - *.ii \ - *.ixx \ - *.ipp \ - *.i++ \ - *.inl \ - *.h \ - *.hh \ - *.hxx \ - *.hpp \ - *.h++ \ - *.idl \ - *.odl \ - *.cs \ - *.php \ - *.php3 \ - *.inc \ - *.m \ - *.markdown \ - *.md \ - *.mm \ - *.dox \ - *.py \ - *.f90 \ - *.f \ - *.for \ - *.vhd \ - *.vhdl - -# The RECURSIVE tag can be used to specify whether or not subdirectories should -# be searched for input files as well. -# The default value is: NO. - -RECURSIVE = NO - -# The EXCLUDE tag can be used to specify files and/or directories that should be -# excluded from the INPUT source files. This way you can easily exclude a -# subdirectory from a directory tree whose root is specified with the INPUT tag. -# -# Note that relative paths are relative to the directory from which doxygen is -# run. - -EXCLUDE = - -# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or -# directories that are symbolic links (a Unix file system feature) are excluded -# from the input. -# The default value is: NO. - -EXCLUDE_SYMLINKS = NO - -# If the value of the INPUT tag contains directories, you can use the -# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude -# certain files from those directories. -# -# Note that the wildcards are matched against the file with absolute path, so to -# exclude all test directories for example use the pattern */test/* - -EXCLUDE_PATTERNS = - -# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names -# (namespaces, classes, functions, etc.) that should be excluded from the -# output. The symbol name can be a fully qualified name, a word, or if the -# wildcard * is used, a substring. Examples: ANamespace, AClass, -# ANamespace::AClass, ANamespace::*Test - -EXCLUDE_SYMBOLS = - -# The EXAMPLE_PATH tag can be used to specify one or more files or directories -# that contain example code fragments that are included (see the \include -# command). - -EXAMPLE_PATH = - -# If the value of the EXAMPLE_PATH tag contains directories, you can use the -# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and -# *.h) to filter out the source-files in the directories. If left blank all -# files are included. - -EXAMPLE_PATTERNS = * - -# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be -# searched for input files to be used with the \include or \dontinclude commands -# irrespective of the value of the RECURSIVE tag. -# The default value is: NO. - -EXAMPLE_RECURSIVE = NO - -# The IMAGE_PATH tag can be used to specify one or more files or directories -# that contain images that are to be included in the documentation (see the -# \image command). - -IMAGE_PATH = - -# The INPUT_FILTER tag can be used to specify a program that doxygen should -# invoke to filter for each input file. Doxygen will invoke the filter program -# by executing (via popen()) the command: -# -# -# -# where is the value of the INPUT_FILTER tag, and is the -# name of an input file. Doxygen will then use the output that the filter -# program writes to standard output. If FILTER_PATTERNS is specified, this tag -# will be ignored. -# -# Note that the filter must not add or remove lines; it is applied before the -# code is scanned, but not when the output code is generated. If lines are added -# or removed, the anchors will not be placed correctly. -# -# Note that doxygen will use the data processed and written to standard output -# for further processing, therefore nothing else, like debug statements or used -# commands (so in case of a Windows batch file always use @echo OFF), should be -# written to standard output. -# -# Note that for custom extensions or not directly supported extensions you also -# need to set EXTENSION_MAPPING for the extension otherwise the files are not -# properly processed by doxygen. - -INPUT_FILTER = - -# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern -# basis. Doxygen will compare the file name with each pattern and apply the -# filter if there is a match. The filters are a list of the form: pattern=filter -# (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how -# filters are used. If the FILTER_PATTERNS tag is empty or if none of the -# patterns match the file name, INPUT_FILTER is applied. -# -# Note that for custom extensions or not directly supported extensions you also -# need to set EXTENSION_MAPPING for the extension otherwise the files are not -# properly processed by doxygen. - -FILTER_PATTERNS = - -# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using -# INPUT_FILTER) will also be used to filter the input files that are used for -# producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). -# The default value is: NO. - -FILTER_SOURCE_FILES = NO - -# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file -# pattern. A pattern will override the setting for FILTER_PATTERN (if any) and -# it is also possible to disable source filtering for a specific pattern using -# *.ext= (so without naming a filter). -# This tag requires that the tag FILTER_SOURCE_FILES is set to YES. - -FILTER_SOURCE_PATTERNS = - -# If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that -# is part of the input, its contents will be placed on the main page -# (index.html). This can be useful if you have a project on for instance GitHub -# and want to reuse the introduction page also for the doxygen output. - -USE_MDFILE_AS_MAINPAGE = - -# The Fortran standard specifies that for fixed formatted Fortran code all -# characters from position 72 are to be considered as comment. A common -# extension is to allow longer lines before the automatic comment starts. The -# setting FORTRAN_COMMENT_AFTER will also make it possible that longer lines can -# be processed before the automatic comment starts. -# Minimum value: 7, maximum value: 10000, default value: 72. - -FORTRAN_COMMENT_AFTER = 72 - -#--------------------------------------------------------------------------- -# Configuration options related to source browsing -#--------------------------------------------------------------------------- - -# If the SOURCE_BROWSER tag is set to YES then a list of source files will be -# generated. Documented entities will be cross-referenced with these sources. -# -# Note: To get rid of all source code in the generated output, make sure that -# also VERBATIM_HEADERS is set to NO. -# The default value is: NO. - -SOURCE_BROWSER = YES - -# Setting the INLINE_SOURCES tag to YES will include the body of functions, -# multi-line macros, enums or list initialized variables directly into the -# documentation. -# The default value is: NO. - -INLINE_SOURCES = NO - -# Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any -# special comment blocks from generated source code fragments. Normal C, C++ and -# Fortran comments will always remain visible. -# The default value is: YES. - -STRIP_CODE_COMMENTS = YES - -# If the REFERENCED_BY_RELATION tag is set to YES then for each documented -# entity all documented functions referencing it will be listed. -# The default value is: NO. - -REFERENCED_BY_RELATION = NO - -# If the REFERENCES_RELATION tag is set to YES then for each documented function -# all documented entities called/used by that function will be listed. -# The default value is: NO. - -REFERENCES_RELATION = NO - -# If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set -# to YES then the hyperlinks from functions in REFERENCES_RELATION and -# REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will -# link to the documentation. -# The default value is: YES. - -REFERENCES_LINK_SOURCE = YES - -# If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the -# source code will show a tooltip with additional information such as prototype, -# brief description and links to the definition and documentation. Since this -# will make the HTML file larger and loading of large files a bit slower, you -# can opt to disable this feature. -# The default value is: YES. -# This tag requires that the tag SOURCE_BROWSER is set to YES. - -SOURCE_TOOLTIPS = YES - -# If the USE_HTAGS tag is set to YES then the references to source code will -# point to the HTML generated by the htags(1) tool instead of doxygen built-in -# source browser. The htags tool is part of GNU's global source tagging system -# (see https://www.gnu.org/software/global/global.html). You will need version -# 4.8.6 or higher. -# -# To use it do the following: -# - Install the latest version of global -# - Enable SOURCE_BROWSER and USE_HTAGS in the configuration file -# - Make sure the INPUT points to the root of the source tree -# - Run doxygen as normal -# -# Doxygen will invoke htags (and that will in turn invoke gtags), so these -# tools must be available from the command line (i.e. in the search path). -# -# The result: instead of the source browser generated by doxygen, the links to -# source code will now point to the output of htags. -# The default value is: NO. -# This tag requires that the tag SOURCE_BROWSER is set to YES. - -USE_HTAGS = NO - -# If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a -# verbatim copy of the header file for each class for which an include is -# specified. Set to NO to disable this. -# See also: Section \class. -# The default value is: YES. - -VERBATIM_HEADERS = YES - -# If the CLANG_ASSISTED_PARSING tag is set to YES then doxygen will use the -# clang parser (see: -# http://clang.llvm.org/) for more accurate parsing at the cost of reduced -# performance. This can be particularly helpful with template rich C++ code for -# which doxygen's built-in parser lacks the necessary type information. -# Note: The availability of this option depends on whether or not doxygen was -# generated with the -Duse_libclang=ON option for CMake. -# The default value is: NO. - -CLANG_ASSISTED_PARSING = NO - -# If the CLANG_ASSISTED_PARSING tag is set to YES and the CLANG_ADD_INC_PATHS -# tag is set to YES then doxygen will add the directory of each input to the -# include path. -# The default value is: YES. -# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. - -CLANG_ADD_INC_PATHS = YES - -# If clang assisted parsing is enabled you can provide the compiler with command -# line options that you would normally use when invoking the compiler. Note that -# the include paths will already be set by doxygen for the files and directories -# specified with INPUT and INCLUDE_PATH. -# This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. - -CLANG_OPTIONS = - -# If clang assisted parsing is enabled you can provide the clang parser with the -# path to the directory containing a file called compile_commands.json. This -# file is the compilation database (see: -# http://clang.llvm.org/docs/HowToSetupToolingForLLVM.html) containing the -# options used when the source files were built. This is equivalent to -# specifying the -p option to a clang tool, such as clang-check. These options -# will then be passed to the parser. Any options specified with CLANG_OPTIONS -# will be added as well. -# Note: The availability of this option depends on whether or not doxygen was -# generated with the -Duse_libclang=ON option for CMake. - -CLANG_DATABASE_PATH = - -#--------------------------------------------------------------------------- -# Configuration options related to the alphabetical class index -#--------------------------------------------------------------------------- - -# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all -# compounds will be generated. Enable this if the project contains a lot of -# classes, structs, unions or interfaces. -# The default value is: YES. - -ALPHABETICAL_INDEX = YES - -# The IGNORE_PREFIX tag can be used to specify a prefix (or a list of prefixes) -# that should be ignored while generating the index headers. The IGNORE_PREFIX -# tag works for classes, function and member names. The entity will be placed in -# the alphabetical list under the first letter of the entity name that remains -# after removing the prefix. -# This tag requires that the tag ALPHABETICAL_INDEX is set to YES. - -IGNORE_PREFIX = - -#--------------------------------------------------------------------------- -# Configuration options related to the HTML output -#--------------------------------------------------------------------------- - -# If the GENERATE_HTML tag is set to YES, doxygen will generate HTML output -# The default value is: YES. - -GENERATE_HTML = YES - -# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a -# relative path is entered the value of OUTPUT_DIRECTORY will be put in front of -# it. -# The default directory is: html. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_OUTPUT = html - -# The HTML_FILE_EXTENSION tag can be used to specify the file extension for each -# generated HTML page (for example: .htm, .php, .asp). -# The default value is: .html. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_FILE_EXTENSION = .html - -# The HTML_HEADER tag can be used to specify a user-defined HTML header file for -# each generated HTML page. If the tag is left blank doxygen will generate a -# standard header. -# -# To get valid HTML the header file that includes any scripts and style sheets -# that doxygen needs, which is dependent on the configuration options used (e.g. -# the setting GENERATE_TREEVIEW). It is highly recommended to start with a -# default header using -# doxygen -w html new_header.html new_footer.html new_stylesheet.css -# YourConfigFile -# and then modify the file new_header.html. See also section "Doxygen usage" -# for information on how to generate the default header that doxygen normally -# uses. -# Note: The header is subject to change so you typically have to regenerate the -# default header when upgrading to a newer version of doxygen. For a description -# of the possible markers and block names see the documentation. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_HEADER = - -# The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each -# generated HTML page. If the tag is left blank doxygen will generate a standard -# footer. See HTML_HEADER for more information on how to generate a default -# footer and what special commands can be used inside the footer. See also -# section "Doxygen usage" for information on how to generate the default footer -# that doxygen normally uses. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_FOOTER = - -# The HTML_STYLESHEET tag can be used to specify a user-defined cascading style -# sheet that is used by each HTML page. It can be used to fine-tune the look of -# the HTML output. If left blank doxygen will generate a default style sheet. -# See also section "Doxygen usage" for information on how to generate the style -# sheet that doxygen normally uses. -# Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as -# it is more robust and this tag (HTML_STYLESHEET) will in the future become -# obsolete. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_STYLESHEET = - -# The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined -# cascading style sheets that are included after the standard style sheets -# created by doxygen. Using this option one can overrule certain style aspects. -# This is preferred over using HTML_STYLESHEET since it does not replace the -# standard style sheet and is therefore more robust against future updates. -# Doxygen will copy the style sheet files to the output directory. -# Note: The order of the extra style sheet files is of importance (e.g. the last -# style sheet in the list overrules the setting of the previous ones in the -# list). -# Note: Since the styling of scrollbars can currently not be overruled in -# Webkit/Chromium, the styling will be left out of the default doxygen.css if -# one or more extra stylesheets have been specified. So if scrollbar -# customization is desired it has to be added explicitly. For an example see the -# documentation. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_EXTRA_STYLESHEET = - -# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or -# other source files which should be copied to the HTML output directory. Note -# that these files will be copied to the base HTML output directory. Use the -# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these -# files. In the HTML_STYLESHEET file, use the file name only. Also note that the -# files will be copied as-is; there are no commands or markers available. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_EXTRA_FILES = - -# The HTML_COLORSTYLE tag can be used to specify if the generated HTML output -# should be rendered with a dark or light theme. -# Possible values are: LIGHT always generate light mode output, DARK always -# generate dark mode output, AUTO_LIGHT automatically set the mode according to -# the user preference, use light mode if no preference is set (the default), -# AUTO_DARK automatically set the mode according to the user preference, use -# dark mode if no preference is set and TOGGLE allow to user to switch between -# light and dark mode via a button. -# The default value is: AUTO_LIGHT. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_COLORSTYLE = AUTO_LIGHT - -# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen -# will adjust the colors in the style sheet and background images according to -# this color. Hue is specified as an angle on a color-wheel, see -# https://en.wikipedia.org/wiki/Hue for more information. For instance the value -# 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 -# purple, and 360 is red again. -# Minimum value: 0, maximum value: 359, default value: 220. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_COLORSTYLE_HUE = 220 - -# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors -# in the HTML output. For a value of 0 the output will use gray-scales only. A -# value of 255 will produce the most vivid colors. -# Minimum value: 0, maximum value: 255, default value: 100. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_COLORSTYLE_SAT = 100 - -# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the -# luminance component of the colors in the HTML output. Values below 100 -# gradually make the output lighter, whereas values above 100 make the output -# darker. The value divided by 100 is the actual gamma applied, so 80 represents -# a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not -# change the gamma. -# Minimum value: 40, maximum value: 240, default value: 80. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_COLORSTYLE_GAMMA = 80 - -# If the HTML_DYNAMIC_MENUS tag is set to YES then the generated HTML -# documentation will contain a main index with vertical navigation menus that -# are dynamically created via JavaScript. If disabled, the navigation index will -# consists of multiple levels of tabs that are statically embedded in every HTML -# page. Disable this option to support browsers that do not have JavaScript, -# like the Qt help browser. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_DYNAMIC_MENUS = YES - -# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML -# documentation will contain sections that can be hidden and shown after the -# page has loaded. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_DYNAMIC_SECTIONS = NO - -# If the HTML_CODE_FOLDING tag is set to YES then classes and functions can be -# dynamically folded and expanded in the generated HTML source code. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_CODE_FOLDING = YES - -# If the HTML_COPY_CLIPBOARD tag is set to YES then doxygen will show an icon in -# the top right corner of code and text fragments that allows the user to copy -# its content to the clipboard. Note this only works if supported by the browser -# and the web page is served via a secure context (see: -# https://www.w3.org/TR/secure-contexts/), i.e. using the https: or file: -# protocol. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_COPY_CLIPBOARD = YES - -# Doxygen stores a couple of settings persistently in the browser (via e.g. -# cookies). By default these settings apply to all HTML pages generated by -# doxygen across all projects. The HTML_PROJECT_COOKIE tag can be used to store -# the settings under a project specific key, such that the user preferences will -# be stored separately. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_PROJECT_COOKIE = - -# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries -# shown in the various tree structured indices initially; the user can expand -# and collapse entries dynamically later on. Doxygen will expand the tree to -# such a level that at most the specified number of entries are visible (unless -# a fully collapsed tree already exceeds this amount). So setting the number of -# entries 1 will produce a full collapsed tree by default. 0 is a special value -# representing an infinite number of entries and will result in a full expanded -# tree by default. -# Minimum value: 0, maximum value: 9999, default value: 100. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_INDEX_NUM_ENTRIES = 100 - -# If the GENERATE_DOCSET tag is set to YES, additional index files will be -# generated that can be used as input for Apple's Xcode 3 integrated development -# environment (see: -# https://developer.apple.com/xcode/), introduced with OSX 10.5 (Leopard). To -# create a documentation set, doxygen will generate a Makefile in the HTML -# output directory. Running make will produce the docset in that directory and -# running make install will install the docset in -# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at -# startup. See https://developer.apple.com/library/archive/featuredarticles/Doxy -# genXcode/_index.html for more information. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -GENERATE_DOCSET = NO - -# This tag determines the name of the docset feed. A documentation feed provides -# an umbrella under which multiple documentation sets from a single provider -# (such as a company or product suite) can be grouped. -# The default value is: Doxygen generated docs. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_FEEDNAME = "Doxygen generated docs" - -# This tag determines the URL of the docset feed. A documentation feed provides -# an umbrella under which multiple documentation sets from a single provider -# (such as a company or product suite) can be grouped. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_FEEDURL = - -# This tag specifies a string that should uniquely identify the documentation -# set bundle. This should be a reverse domain-name style string, e.g. -# com.mycompany.MyDocSet. Doxygen will append .docset to the name. -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_BUNDLE_ID = org.doxygen.Project - -# The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify -# the documentation publisher. This should be a reverse domain-name style -# string, e.g. com.mycompany.MyDocSet.documentation. -# The default value is: org.doxygen.Publisher. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_PUBLISHER_ID = org.doxygen.Publisher - -# The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. -# The default value is: Publisher. -# This tag requires that the tag GENERATE_DOCSET is set to YES. - -DOCSET_PUBLISHER_NAME = Publisher - -# If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three -# additional HTML index files: index.hhp, index.hhc, and index.hhk. The -# index.hhp is a project file that can be read by Microsoft's HTML Help Workshop -# on Windows. In the beginning of 2021 Microsoft took the original page, with -# a.o. the download links, offline the HTML help workshop was already many years -# in maintenance mode). You can download the HTML help workshop from the web -# archives at Installation executable (see: -# http://web.archive.org/web/20160201063255/http://download.microsoft.com/downlo -# ad/0/A/9/0A939EF6-E31C-430F-A3DF-DFAE7960D564/htmlhelp.exe). -# -# The HTML Help Workshop contains a compiler that can convert all HTML output -# generated by doxygen into a single compiled HTML file (.chm). Compiled HTML -# files are now used as the Windows 98 help format, and will replace the old -# Windows help format (.hlp) on all Windows platforms in the future. Compressed -# HTML files also contain an index, a table of contents, and you can search for -# words in the documentation. The HTML workshop also contains a viewer for -# compressed HTML files. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -GENERATE_HTMLHELP = NO - -# The CHM_FILE tag can be used to specify the file name of the resulting .chm -# file. You can add a path in front of the file if the result should not be -# written to the html output directory. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -CHM_FILE = - -# The HHC_LOCATION tag can be used to specify the location (absolute path -# including file name) of the HTML help compiler (hhc.exe). If non-empty, -# doxygen will try to run the HTML help compiler on the generated index.hhp. -# The file has to be specified with full path. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -HHC_LOCATION = - -# The GENERATE_CHI flag controls if a separate .chi index file is generated -# (YES) or that it should be included in the main .chm file (NO). -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -GENERATE_CHI = NO - -# The CHM_INDEX_ENCODING is used to encode HtmlHelp index (hhk), content (hhc) -# and project file content. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -CHM_INDEX_ENCODING = - -# The BINARY_TOC flag controls whether a binary table of contents is generated -# (YES) or a normal table of contents (NO) in the .chm file. Furthermore it -# enables the Previous and Next buttons. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -BINARY_TOC = NO - -# The TOC_EXPAND flag can be set to YES to add extra items for group members to -# the table of contents of the HTML help documentation and to the tree view. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTMLHELP is set to YES. - -TOC_EXPAND = NO - -# The SITEMAP_URL tag is used to specify the full URL of the place where the -# generated documentation will be placed on the server by the user during the -# deployment of the documentation. The generated sitemap is called sitemap.xml -# and placed on the directory specified by HTML_OUTPUT. In case no SITEMAP_URL -# is specified no sitemap is generated. For information about the sitemap -# protocol see https://www.sitemaps.org -# This tag requires that the tag GENERATE_HTML is set to YES. - -SITEMAP_URL = - -# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and -# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that -# can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help -# (.qch) of the generated HTML documentation. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -GENERATE_QHP = NO - -# If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify -# the file name of the resulting .qch file. The path specified is relative to -# the HTML output folder. -# This tag requires that the tag GENERATE_QHP is set to YES. - -QCH_FILE = - -# The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help -# Project output. For more information please see Qt Help Project / Namespace -# (see: -# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#namespace). -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHP_NAMESPACE = org.doxygen.Project - -# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt -# Help Project output. For more information please see Qt Help Project / Virtual -# Folders (see: -# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#virtual-folders). -# The default value is: doc. -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHP_VIRTUAL_FOLDER = doc - -# If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom -# filter to add. For more information please see Qt Help Project / Custom -# Filters (see: -# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHP_CUST_FILTER_NAME = - -# The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the -# custom filter to add. For more information please see Qt Help Project / Custom -# Filters (see: -# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#custom-filters). -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHP_CUST_FILTER_ATTRS = - -# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this -# project's filter section matches. Qt Help Project / Filter Attributes (see: -# https://doc.qt.io/archives/qt-4.8/qthelpproject.html#filter-attributes). -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHP_SECT_FILTER_ATTRS = - -# The QHG_LOCATION tag can be used to specify the location (absolute path -# including file name) of Qt's qhelpgenerator. If non-empty doxygen will try to -# run qhelpgenerator on the generated .qhp file. -# This tag requires that the tag GENERATE_QHP is set to YES. - -QHG_LOCATION = - -# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be -# generated, together with the HTML files, they form an Eclipse help plugin. To -# install this plugin and make it available under the help contents menu in -# Eclipse, the contents of the directory containing the HTML and XML files needs -# to be copied into the plugins directory of eclipse. The name of the directory -# within the plugins directory should be the same as the ECLIPSE_DOC_ID value. -# After copying Eclipse needs to be restarted before the help appears. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -GENERATE_ECLIPSEHELP = NO - -# A unique identifier for the Eclipse help plugin. When installing the plugin -# the directory name containing the HTML and XML files should also have this -# name. Each documentation set should have its own identifier. -# The default value is: org.doxygen.Project. -# This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. - -ECLIPSE_DOC_ID = org.doxygen.Project - -# If you want full control over the layout of the generated HTML pages it might -# be necessary to disable the index and replace it with your own. The -# DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top -# of each HTML page. A value of NO enables the index and the value YES disables -# it. Since the tabs in the index contain the same information as the navigation -# tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -DISABLE_INDEX = NO - -# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index -# structure should be generated to display hierarchical information. If the tag -# value is set to YES, a side panel will be generated containing a tree-like -# index structure (just like the one that is generated for HTML Help). For this -# to work a browser that supports JavaScript, DHTML, CSS and frames is required -# (i.e. any modern browser). Windows users are probably better off using the -# HTML help feature. Via custom style sheets (see HTML_EXTRA_STYLESHEET) one can -# further fine tune the look of the index (see "Fine-tuning the output"). As an -# example, the default style sheet generated by doxygen has an example that -# shows how to put an image at the root of the tree instead of the PROJECT_NAME. -# Since the tree basically has the same information as the tab index, you could -# consider setting DISABLE_INDEX to YES when enabling this option. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -GENERATE_TREEVIEW = NO - -# When both GENERATE_TREEVIEW and DISABLE_INDEX are set to YES, then the -# FULL_SIDEBAR option determines if the side bar is limited to only the treeview -# area (value NO) or if it should extend to the full height of the window (value -# YES). Setting this to YES gives a layout similar to -# https://docs.readthedocs.io with more room for contents, but less room for the -# project logo, title, and description. If either GENERATE_TREEVIEW or -# DISABLE_INDEX is set to NO, this option has no effect. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -FULL_SIDEBAR = NO - -# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that -# doxygen will group on one line in the generated HTML documentation. -# -# Note that a value of 0 will completely suppress the enum values from appearing -# in the overview section. -# Minimum value: 0, maximum value: 20, default value: 4. -# This tag requires that the tag GENERATE_HTML is set to YES. - -ENUM_VALUES_PER_LINE = 4 - -# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used -# to set the initial width (in pixels) of the frame in which the tree is shown. -# Minimum value: 0, maximum value: 1500, default value: 250. -# This tag requires that the tag GENERATE_HTML is set to YES. - -TREEVIEW_WIDTH = 250 - -# If the EXT_LINKS_IN_WINDOW option is set to YES, doxygen will open links to -# external symbols imported via tag files in a separate window. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -EXT_LINKS_IN_WINDOW = NO - -# If the OBFUSCATE_EMAILS tag is set to YES, doxygen will obfuscate email -# addresses. -# The default value is: YES. -# This tag requires that the tag GENERATE_HTML is set to YES. - -OBFUSCATE_EMAILS = YES - -# If the HTML_FORMULA_FORMAT option is set to svg, doxygen will use the pdf2svg -# tool (see https://github.com/dawbarton/pdf2svg) or inkscape (see -# https://inkscape.org) to generate formulas as SVG images instead of PNGs for -# the HTML output. These images will generally look nicer at scaled resolutions. -# Possible values are: png (the default) and svg (looks nicer but requires the -# pdf2svg or inkscape tool). -# The default value is: png. -# This tag requires that the tag GENERATE_HTML is set to YES. - -HTML_FORMULA_FORMAT = png - -# Use this tag to change the font size of LaTeX formulas included as images in -# the HTML documentation. When you change the font size after a successful -# doxygen run you need to manually remove any form_*.png images from the HTML -# output directory to force them to be regenerated. -# Minimum value: 8, maximum value: 50, default value: 10. -# This tag requires that the tag GENERATE_HTML is set to YES. - -FORMULA_FONTSIZE = 10 - -# The FORMULA_MACROFILE can contain LaTeX \newcommand and \renewcommand commands -# to create new LaTeX commands to be used in formulas as building blocks. See -# the section "Including formulas" for details. - -FORMULA_MACROFILE = - -# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see -# https://www.mathjax.org) which uses client side JavaScript for the rendering -# instead of using pre-rendered bitmaps. Use this if you do not have LaTeX -# installed or if you want to formulas look prettier in the HTML output. When -# enabled you may also need to install MathJax separately and configure the path -# to it using the MATHJAX_RELPATH option. -# The default value is: NO. -# This tag requires that the tag GENERATE_HTML is set to YES. - -USE_MATHJAX = YES - -# With MATHJAX_VERSION it is possible to specify the MathJax version to be used. -# Note that the different versions of MathJax have different requirements with -# regards to the different settings, so it is possible that also other MathJax -# settings have to be changed when switching between the different MathJax -# versions. -# Possible values are: MathJax_2 and MathJax_3. -# The default value is: MathJax_2. -# This tag requires that the tag USE_MATHJAX is set to YES. - -MATHJAX_VERSION = MathJax_2 - -# When MathJax is enabled you can set the default output format to be used for -# the MathJax output. For more details about the output format see MathJax -# version 2 (see: -# http://docs.mathjax.org/en/v2.7-latest/output.html) and MathJax version 3 -# (see: -# http://docs.mathjax.org/en/latest/web/components/output.html). -# Possible values are: HTML-CSS (which is slower, but has the best -# compatibility. This is the name for Mathjax version 2, for MathJax version 3 -# this will be translated into chtml), NativeMML (i.e. MathML. Only supported -# for NathJax 2. For MathJax version 3 chtml will be used instead.), chtml (This -# is the name for Mathjax version 3, for MathJax version 2 this will be -# translated into HTML-CSS) and SVG. -# The default value is: HTML-CSS. -# This tag requires that the tag USE_MATHJAX is set to YES. - -MATHJAX_FORMAT = HTML-CSS - -# When MathJax is enabled you need to specify the location relative to the HTML -# output directory using the MATHJAX_RELPATH option. The destination directory -# should contain the MathJax.js script. For instance, if the mathjax directory -# is located at the same level as the HTML output directory, then -# MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax -# Content Delivery Network so you can quickly see the result without installing -# MathJax. However, it is strongly recommended to install a local copy of -# MathJax from https://www.mathjax.org before deployment. The default value is: -# - in case of MathJax version 2: https://cdn.jsdelivr.net/npm/mathjax@2 -# - in case of MathJax version 3: https://cdn.jsdelivr.net/npm/mathjax@3 -# This tag requires that the tag USE_MATHJAX is set to YES. - -MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest - -# The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax -# extension names that should be enabled during MathJax rendering. For example -# for MathJax version 2 (see -# https://docs.mathjax.org/en/v2.7-latest/tex.html#tex-and-latex-extensions): -# MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols -# For example for MathJax version 3 (see -# http://docs.mathjax.org/en/latest/input/tex/extensions/index.html): -# MATHJAX_EXTENSIONS = ams -# This tag requires that the tag USE_MATHJAX is set to YES. - -MATHJAX_EXTENSIONS = - -# The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces -# of code that will be used on startup of the MathJax code. See the MathJax site -# (see: -# http://docs.mathjax.org/en/v2.7-latest/output.html) for more details. For an -# example see the documentation. -# This tag requires that the tag USE_MATHJAX is set to YES. - -MATHJAX_CODEFILE = - -# When the SEARCHENGINE tag is enabled doxygen will generate a search box for -# the HTML output. The underlying search engine uses javascript and DHTML and -# should work on any modern browser. Note that when using HTML help -# (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) -# there is already a search function so this one should typically be disabled. -# For large projects the javascript based search engine can be slow, then -# enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to -# search using the keyboard; to jump to the search box use + S -# (what the is depends on the OS and browser, but it is typically -# , /