- Feb 04, 2019
-
-
Dominic Kempf authored
-
- Jan 31, 2019
-
-
Dominic Kempf authored
-
- Jan 29, 2019
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Jan 28, 2019
- Jan 24, 2019
-
-
René Heß authored
The realize_output interface method was not really necessary and just adds a layer of indiretion.
-
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
-
- Jan 07, 2019
-
-
René Heß authored
-
- Dec 21, 2018
-
-
René Heß authored
-
- Dec 18, 2018
- Dec 17, 2018
-
-
René Heß authored
-
- Dec 14, 2018
-
-
René Heß authored
-
- Dec 13, 2018
- Dec 12, 2018
-
-
René Heß authored
-
- Dec 11, 2018
-
-
Dominic Kempf authored
-
- Dec 10, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Dec 07, 2018
-
-
Dominic Kempf authored
-
Dominic Kempf authored
-
Dominic Kempf authored
-
- Dec 05, 2018
-
-
Dominic Kempf authored
-
- Dec 04, 2018
-
-
Dominic Kempf authored
-
- Dec 03, 2018
-
-
Dominic Kempf authored
-
- Nov 28, 2018
-
-
Dominic Kempf authored
-
- Nov 26, 2018
-
-
Dominic Kempf authored
-
- Nov 23, 2018
-
-
René Heß authored
Introduce different methods for realize_input/output realize_direct_input/output and setup_input/output. The setup methods cover code generation outside the sumfact kernel function (creating input array or accumulating result). realize and realize_direct handle the input/output in the nonfastdg and fastdg code branch. Seperate interface methods make it a lot easier to find out where each of those methods will be applied. Besides that most interface classes need to provide more that two of those methods anyway...
-
- Nov 22, 2018