- Apr 01, 2019
-
-
René Heß authored
-
- Feb 06, 2019
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Feb 01, 2019
-
-
Marcel Koch authored
-
- Jan 29, 2019
-
-
Dominic Kempf authored
-
Marcel Koch authored
-
- Jan 24, 2019
-
-
Dominic Kempf authored
-
- Jan 23, 2019
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Jan 16, 2019
-
-
Dominic Kempf authored
-
- Dec 11, 2018
-
-
Dominic Kempf authored
-
- Dec 10, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Dec 07, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Dec 05, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Dec 04, 2018
-
-
Dominic Kempf authored
-
- Dec 03, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Nov 28, 2018
-
-
Dominic Kempf authored
-
- Nov 22, 2018
-
-
René Heß authored
Non-fastdg: Permutation of the input happens before the sum factorization kernel when we setup the input. This is done by a method of the corresponding interface class. Fastdg: In this case the input will always be ordered according to x,y,... This means the permutation needs to happen in the sumfact kernel. Since we want to vectorize sumfact kernels with different input permutation in an upper/lower way we need to do this permutation in the corresponding interface class. This is done in the realize_direct method and in the vectorized case the corresponding methods of the scalar sumfact kernels are called.
-