dumux issueshttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues2020-09-30T07:41:34Zhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/934[periodic] Check if current implementation for box is correct2020-09-30T07:41:34ZKilian Weishaupt[periodic] Check if current implementation for box is correctFor box, we consider a "primary" and "secondary" DOFs, i.e. the secondary DOF is periodically corresponding to the primary one.
We add the value of the secondary DOF residual to the one of the primary one
```c++
res[m.first] += res[m....For box, we consider a "primary" and "secondary" DOFs, i.e. the secondary DOF is periodically corresponding to the primary one.
We add the value of the secondary DOF residual to the one of the primary one
```c++
res[m.first] += res[m.second];
```
and enforce
```c++
jac[m.first][it.index()] += (*it)
```
This makes sense, I guess.
For the secondary DOF, we adapt the matrix entries such that the is a -1 for the periodic DOF and a 1 for the own DOF.
All other entries are zero. I guess the idea is to set the secondary DOF values equal to the primary ones.
I think we should also adapt the residual of the secondary DOF such that
```c++
res[m.second] = curSol[m.second] - curSol[m.first];
```3.3Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.no2020-09-30https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/965[example] Lid-driven-cavity plot still fails on buildbot minimal2020-11-09T10:34:24ZKilian Weishaupt[example] Lid-driven-cavity plot still fails on buildbot minimalPlot test fails on this builder https://git.iws.uni-stuttgart.de/buildbot/#/builders/14
Since UMFPack is not found, the test should not even exist. The two "actual" tests (running the cases) are correctly skipped.
Is something wrong w...Plot test fails on this builder https://git.iws.uni-stuttgart.de/buildbot/#/builders/14
Since UMFPack is not found, the test should not even exist. The two "actual" tests (running the cases) are correctly skipped.
Is something wrong with the builder? Did it not pull the latest version of 3.3?
```
473/480 Test #480: example_ff_liddrivencavity_plot ............................***Failed 0.30 sec
Traceback (most recent call last):
File "/data/dumux/examples/liddrivencavity/run_and_plot.py", line 30, in <module>
y[str(re)], vx[str(re)] = np.genfromtxt('example_ff_liddrivencavity_re' + str(re) + '_vx' + '.log', skip_header= True).T
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/npyio.py", line 1749, in genfromtxt
fid = np.lib._datasource.open(fname, 'rt', encoding=encoding)
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/_datasource.py", line 195, in open
return ds.open(path, mode, encoding=encoding, newline=newline)
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/_datasource.py", line 535, in open
raise IOError("%s not found." % path)
OSError: example_ff_liddrivencavity_re1_vx.log not found.
```3.3Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/964[fluidmatrixinteraction] Temporary fluidmatrix law objects always get copied2020-11-08T10:05:26ZKilian Weishaupt[fluidmatrixinteraction] Temporary fluidmatrix law objects always get copiedWhen using
```c++
template<class ElementSolution>
auto fluidMatrixInteraction(const Element& element,
const SubControlVolume& scv,
const ElementSolution& elemSol) c...When using
```c++
template<class ElementSolution>
auto fluidMatrixInteraction(const Element& element,
const SubControlVolume& scv,
const ElementSolution& elemSol) const
{
const auto params = ....;
return makeFluidMatrixInteraction(MyTemporaryPcSwCurve(params));
}
```
the temporary object gets always copied in the `PcKrSw` constructor in `fluidmatrixinteraction.hh`
This also prevents using unique_ptrs in `MyTemporaryPcSwCurve`.
I suggest to change `PcKrSw`'s ctor such that:
```c++
template<class CtorType>
PcKrSw(CtorType&& impl) : impl_(std::forward<CtorType>(impl))
{
static_assert(std::is_same_v<std::decay_t<T>, std::decay_t<CtorType>>);
}
```
This means that `CtorType` (please feel free to suggest a better name) can be different from `T`.3.3Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/963Deprecation warning 3.3 compositional flash2020-11-08T10:15:36ZTimo Kochtimokoch@math.uio.noDeprecation warning 3.3 compositional flash```
../test/material/compositionalflash/test_compositionalflash.cc:352:116: warning: ‘static void Dumux::CompositionalFlash<Scalar, FluidSystem>::saturationFlash2p2c(FluidState&, const Scalar&, const PhaseVector&, const Scalar&, const Sc...```
../test/material/compositionalflash/test_compositionalflash.cc:352:116: warning: ‘static void Dumux::CompositionalFlash<Scalar, FluidSystem>::saturationFlash2p2c(FluidState&, const Scalar&, const PhaseVector&, const Scalar&, const Scalar&) [with FluidState = Dumux::CompositionalFluidState<double, Dumux::FluidSystems::H2ON2<double, Dumux::FluidSystems::H2ON2DefaultPolicy<true> > >; Scalar = double; FluidSystem = Dumux::FluidSystems::H2ON2<double, Dumux::FluidSystems::H2ON2DefaultPolicy<true> >; Dumux::CompositionalFlash<Scalar, FluidSystem>::PhaseVector = Dune::FieldVector<double, 2>]’ is deprecated: Use saturationFlash2p2c without porosity argument. Will be removed after 3.3 [-Wdeprecated-declarations]
352 | pressures, 0/*dummy*/, fsRef.temperature(0));
| ^
In file included from ../test/material/compositionalflash/test_compositionalflash.cc:34:
../dumux/material/constraintsolvers/compositionalflash.hh:219:17: note: declared here
219 | static void saturationFlash2p2c(FluidState &fluidState,
| ^~~~~~~~~~~~~~~~~~~
```3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/962example_liddriven_cavity fails on minimal installation2020-11-06T09:03:07ZKilian Weishauptexample_liddriven_cavity fails on minimal installation@timok @DennisGlaeser
```
473/480 Test #480: example_ff_liddrivencavity_plot ............................***Failed 0.34 sec
Traceback (most recent call last):
File "/data/build/dumux/examples/liddrivencavity/run_and_plot.py", line...@timok @DennisGlaeser
```
473/480 Test #480: example_ff_liddrivencavity_plot ............................***Failed 0.34 sec
Traceback (most recent call last):
File "/data/build/dumux/examples/liddrivencavity/run_and_plot.py", line 29, in <module>
y[str(re)], vx[str(re)] = np.genfromtxt('example_ff_liddrivencavity_re' + str(re) + '_vx' + '.log', skip_header= True).T
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/npyio.py", line 1749, in genfromtxt
fid = np.lib._datasource.open(fname, 'rt', encoding=encoding)
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/_datasource.py", line 195, in open
return ds.open(path, mode, encoding=encoding, newline=newline)
File "/usr/local/lib/python3.8/dist-packages/numpy/lib/_datasource.py", line 535, in open
raise IOError("%s not found." % path)
OSError: example_ff_liddrivencavity_re1_vx.log not found.
```3.3Kilian WeishauptKilian Weishaupthttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/961CMake errors for all tests2020-11-06T11:33:32ZBernd FlemischCMake errors for all testsWith Ubuntu 20.10, cmake 3.16.3 and Dune master, building dumux master and releases/3.3 fails with
```
CMake Error in CMakeLists.txt:
Found relative path while evaluating include directories of "dumux_fmt":
"SYSTEM"
```
and the sa...With Ubuntu 20.10, cmake 3.16.3 and Dune master, building dumux master and releases/3.3 fails with
```
CMake Error in CMakeLists.txt:
Found relative path while evaluating include directories of "dumux_fmt":
"SYSTEM"
```
and the same message for all tests. Everything is fine with Dune 2.7.
[console_output.txt](/uploads/1e84db423df3e2b6cecd9b5f9dacb850/console_output.txt)
[CMakeOutput.log](/uploads/a07c77c1b1334622dda866b0eb4e6647/CMakeOutput.log)
[CMakeError.log](/uploads/92f6ac04b9cd2f1d5f82a63396b54137/CMakeError.log)3.3Kilian WeishauptKilian Weishaupthttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/960Lid-driven cavity example fails2020-11-05T15:37:59ZKilian WeishauptLid-driven cavity example fails```
473/480 Test #480: example_ff_liddrivencavity_plot ............................***Failed 0.27 sec
Traceback (most recent call last):
File "/data/build/dumux/examples/liddrivencavity/run_and_plot.py", line 50, in <module>
imp...```
473/480 Test #480: example_ff_liddrivencavity_plot ............................***Failed 0.27 sec
Traceback (most recent call last):
File "/data/build/dumux/examples/liddrivencavity/run_and_plot.py", line 50, in <module>
import matplotlib.pyplot as plt
ModuleNotFoundError: No module named 'matplotlib'
```3.3Kilian WeishauptKilian Weishaupthttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/957dune python broken: setup-dunepy.py yields 'Invalid version' error2020-11-04T15:28:44ZKilian Weishauptdune python broken: setup-dunepy.py yields 'Invalid version' errorThis is probably only related to dune itself. See https://gitlab.dune-project.org/core/dune-common/-/issues/194
However, it would be nice to provide a workaround in the readme (something like "Change lines XX in the setup-dunepy.py ...")This is probably only related to dune itself. See https://gitlab.dune-project.org/core/dune-common/-/issues/194
However, it would be nice to provide a workaround in the readme (something like "Change lines XX in the setup-dunepy.py ...")3.3Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/956Update parameterlist.txt2020-11-05T16:06:21ZKilian WeishauptUpdate parameterlist.txt`parameterlist.txt` should be updated using the new python script (!2334)
I think @melaniel is already on this, I'm just opening this issue so we don't forget.`parameterlist.txt` should be updated using the new python script (!2334)
I think @melaniel is already on this, I'm just opening this issue so we don't forget.3.3Melanie LippMelanie Lipphttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/954test_md_embedded_1d3d_1p1p_tpfatpfa_convergence fails, no numpy on BuildBot2020-11-05T16:51:01ZTimo Kochtimokoch@math.uio.notest_md_embedded_1d3d_1p1p_tpfatpfa_convergence fails, no numpy on BuildBot3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/953Fix deprecation warnings for embedded tests2020-10-30T14:04:28ZTimo Kochtimokoch@math.uio.noFix deprecation warnings for embedded testsSome embedded test still emit deprecation warnings because of the coupling manager changes.Some embedded test still emit deprecation warnings because of the coupling manager changes.3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/948test_3pwateroil_sagd_box fails2020-10-31T14:18:25ZKilian Weishaupttest_3pwateroil_sagd_box failsFails on hal with g++ (GCC) 10.2.0
```
416: Fuzzy comparison...
416: Comparing /temp/weishaupt/Dumux_testing_master/dumux/test/references/test_3pwateroil_sagd_box-reference.vtu and /temp/weishaupt/Dumux_testing_master/dumux/build-cmake...Fails on hal with g++ (GCC) 10.2.0
```
416: Fuzzy comparison...
416: Comparing /temp/weishaupt/Dumux_testing_master/dumux/test/references/test_3pwateroil_sagd_box-reference.vtu and /temp/weishaupt/Dumux_testing_master/dumux/build-cmake/test/porousmediumflow/3pwateroil/implicit/test_3pwateroil_sagd_box-00001.vtu
416: ... with a maximum relative error of 0.01 and a maximum absolute error of 1.5e-07*max_abs_parameter_value.
416:
416: Data differs in parameter: S_aq
416: Difference is too large: 3.35% -> between: 0.371884 and 0.384759
416: Info for S_aq: max_abs_parameter_value=0.701504 and min_abs_parameter_value=0.371884.
416:
416: Data differs in parameter: S_gas
416: Difference is too large: 3.23% -> between: 0.366778 and 0.35494
416: Info for S_gas: max_abs_parameter_value=0.366778 and min_abs_parameter_value=0.0.
416:
416: Data differs in parameter: mob_aq
416: Difference is too large: 14.05% -> between: 130.979 and 152.385
416: Info for mob_aq: max_abs_parameter_value=467.458 and min_abs_parameter_value=130.979.
416:
416: Data differs in parameter: mob_gas
416: Difference is too large: 5.47% -> between: 14871.0 and 14057.1
416: Info for mob_gas: max_abs_parameter_value=14871.0 and min_abs_parameter_value=0.0.
416:
416: Data differs in parameter: mob_napl
416: Difference is too large: 4.53% -> between: 0.0152723 and 0.0145809
416: Info for mob_napl: max_abs_parameter_value=6.10674 and min_abs_parameter_value=8.86194e-05.
416:
416: Data differs in parameter: mu_gas
416: Difference is too large: 3.13% -> between: 9.50177e-08 and 9.20431e-08
416: Info for mu_gas: max_abs_parameter_value=1.77629e-05 and min_abs_parameter_value=5.87006e-09.
416:
416: Data differs in parameter: mu_napl
416: Difference is too large: 4.65% -> between: 10.7806 and 11.3068
416: Info for mu_napl: max_abs_parameter_value=1747.3 and min_abs_parameter_value=0.00550324.
416:
416: Data differs in parameter: rho_gas
416: Difference is too large: 2.48% -> between: 0.234406 and 0.228589
416: Info for rho_gas: max_abs_parameter_value=23.2395 and min_abs_parameter_value=0.0194941.
416:
416: Data differs in parameter: x^H2O_gas
416: Difference is too large: 2.93% -> between: 0.00838062 and 0.00813482
416: Info for x^H2O_gas: max_abs_parameter_value=0.999998 and min_abs_parameter_value=0.000610972.
416:
416: Data differs in parameter: x^heavyoil_gas
416: Difference is too large: 1.37% -> between: 2.17444e-06 and 2.20465e-06
416: Info for x^heavyoil_gas: max_abs_parameter_value=2.20465e-06 and min_abs_parameter_value=0.0.
416: Fuzzy comparison done (not equal)
1/1 Test #416: test_3pwateroil_sagd_box .........***Failed 9.31 sec
```3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/945[test][2p2c][implicit/waterair] material law in gnuplot2020-10-20T15:51:05ZYue Wangyue.wang@iws.uni-stuttgart.de[test][2p2c][implicit/waterair] material law in gnuplotdumux/io/plotmateriallaw.hh
is not adapted to the new material law.
@kweisdumux/io/plotmateriallaw.hh
is not adapted to the new material law.
@kweis3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/944[test][2p2c][Sequential] New material law in2020-12-29T07:07:20ZYue Wangyue.wang@iws.uni-stuttgart.de[test][2p2c][Sequential] New material law inIn /dumux/material/spatialparams/sequentialfv.hh
`{ template<class TypeTag, class MyTypeTag>
struct MaterialLaw { using type = UndefinedProperty; }; }`
the new material law is not implemented.
@kweis
related to !1607In /dumux/material/spatialparams/sequentialfv.hh
`{ template<class TypeTag, class MyTypeTag>
struct MaterialLaw { using type = UndefinedProperty; }; }`
the new material law is not implemented.
@kweis
related to !16073.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/942Weird conversion in CylinderIntegration2020-10-23T09:33:25ZChristoph GrüningerWeird conversion in CylinderIntegrationClang 11 warns:
```
In file included from /home/kiko/dune/complete/dumux/test/geometry/test_cylinderintegration.cc:12:
/home/gruech/dumux/dumux/multidomain/embedded/cylinderintegration.hh:71:72: warning: implicit conversion from 'unsigne...Clang 11 warns:
```
In file included from /home/kiko/dune/complete/dumux/test/geometry/test_cylinderintegration.cc:12:
/home/gruech/dumux/dumux/multidomain/embedded/cylinderintegration.hh:71:72: warning: implicit conversion from 'unsigned long' to 'double' changes value from 18446744073709551615 to 18446744073709551616 [-Wimplicit-const-int-float-conversion]
rSamples_ = std::max<std::size_t>(1, ceil(1.0/clamp(rStep, 1.0/std::numeric_limits<std::size_t>::max(), 1.0)));
~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
I don't understand the line of code, but I understand that using the largest long and have a type conversion to double is not a good idea. If it is intended, add an explicit cast.3.3Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/941test_vtk_staggeredfreeflowpvnames fails on buildbot2020-10-23T20:19:13ZSimon Emmerttest_vtk_staggeredfreeflowpvnames fails on buildbot`test_vtk_staggeredfreeflowpvnames` aborts on buildbot. I think (but I did not check anything yet), this is due to !2224.
From looking at `dumux/test/io/vtk/test_vtk_staggeredfreeflowpvnames.cc` it seems like the navierstokes-tests work...`test_vtk_staggeredfreeflowpvnames` aborts on buildbot. I think (but I did not check anything yet), this is due to !2224.
From looking at `dumux/test/io/vtk/test_vtk_staggeredfreeflowpvnames.cc` it seems like the navierstokes-tests work, and the KEpsilon-test is the first one to abort with the following message:
`updateStaticWallProperties:/data/dumux/dumux/freeflow/rans/zeroeq/problem.hh:91]:
Due to grid/geometric concerns, zero-eq models should only be used for flat channel geometries.`
I guess this is an easy fix for @nedc or @melaniel
Log excerpt from buildbot:
``` 150/475 Test #132: test_vtk_staggeredfreeflowpvnames ..........................Child aborted***Exception: 2.18 sec
### # # # #
# # # # ## ## # # #
# # # # # # # # # # #
### ## # # ##
Dune for Multi-{ Phase,
Component,
Scale,
Physics,
...} flow and transport in porous media
The H2O-air fluid system was configured with the following policy:
- use H2O density as liquid mixture density: false
- use ideal gas density: false
- use air viscosity as gas mixture viscosity: false
-------------------------------------------------------------------------
Initializing tables for the H2O fluid properties (20000 entries).
Temperature -> min: 2.731e+02, max: 6.231e+02, n: 100
Pressure -> min: -1.000e+01, max: 2.000e+07, n: 200
-------------------------------------------------------------------------
Writing output for problem "navierstokes". Took 3.373e-01 seconds.
Warning: gasDensity(T=0, p=0) of component 'H2O' is outside tabulation range: (273.15<=T<=623.15), (-10<=p<=2e+07). Forwarded to FluidSystem for direct evaluation of gasDensity.
Writing output for problem "navierstokesni". Took 1.604e-01 seconds.
Writing output for problem "navierstokesnc". Took 1.692e-03 seconds.
Writing output for problem "navierstokesncni". Took 2.352e-03 seconds.
terminate called after throwing an instance of 'Dune::NotImplemented'
what(): Dune::NotImplemented [updateStaticWallProperties:/data/dumux/dumux/freeflow/rans/zeroeq/problem.hh:91]:
Due to grid/geometric concerns, zero-eq models should only be used for flat channel geometries.
If your geometry is a flat channel, please set the runtime parameter RANS.IsFlatWallBounded to true. ```3.3Ned ColtmanNed Coltmanhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/939[test] Spline tests causes gnuplot timeout2020-10-02T11:09:03ZKilian Weishaupt[test] Spline tests causes gnuplot timeoutWhen running the `test_cubicspline` on a headless machine (e.g., hal),
I get the following message and the tests runs for more than 60 s due to a timeout
```
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Q...When running the `test_cubicspline` on a headless machine (e.g., hal),
I get the following message and the tests runs for more than 60 s due to a timeout
```
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
Could not connect to existing gnuplot_qt. Starting a new one.
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.
```
Not sure if some packages are missing on hal or if we need to you the gnuplot interface differently, e.g., by setting
```c++
gnuplot.setOpenPlotWindow(false);
```3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/938Consistency/Style NonWetting Nonwetting2020-10-30T18:30:21ZTimo Kochtimokoch@math.uio.noConsistency/Style NonWetting NonwettingThere is currently a mixture between `NonWetting`/`nonWetting` and `Nonwetting`/`nonwetting` forms.
We should decide for one version and use it everywhere, otherwise this is confusing.There is currently a mixture between `NonWetting`/`nonWetting` and `Nonwetting`/`nonwetting` forms.
We should decide for one version and use it everywhere, otherwise this is confusing.3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/936Dumux Day 30.09.20202020-10-28T12:23:47ZKilian WeishauptDumux Day 30.09.2020- [x] !2224 @nedc
- [x] !1490 @nedc
- [ ] !2139 @heck/@nedc
- [ ] #866 @felixw
- [ ] #573 @seitz
- [x] #915 @mathis
- [x] #920 @melaniel
- [x] #880 @timjupe
- [ ] !1822 @martins
- [ ] #837 @hanchuan
- [x] #591 @DennisGlaeser
- [ ] !227...- [x] !2224 @nedc
- [x] !1490 @nedc
- [ ] !2139 @heck/@nedc
- [ ] #866 @felixw
- [ ] #573 @seitz
- [x] #915 @mathis
- [x] #920 @melaniel
- [x] #880 @timjupe
- [ ] !1822 @martins
- [ ] #837 @hanchuan
- [x] #591 @DennisGlaeser
- [ ] !2274 Intersection Stuff @DennisGlaeser
- [ ] PNM Contact Angle Stuff @Maziar3.3https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/935Dumux Release 3.32020-11-16T14:30:22ZKilian WeishauptDumux Release 3.3### Release 3.3
- __Date:__ 6.11.20
- __Manager:__ Kilian
- __Lecture Larry:__ Ned
- __Doxygen Dude:__ Melanie #920
- __Handbook Handsome:__ Farid
- __Course Coolness:__ Roman
- __Examples Exceller:__ Dennis
### Related issues
#920
#...### Release 3.3
- __Date:__ 6.11.20
- __Manager:__ Kilian
- __Lecture Larry:__ Ned
- __Doxygen Dude:__ Melanie #920
- __Handbook Handsome:__ Farid
- __Course Coolness:__ Roman
- __Examples Exceller:__ Dennis
### Related issues
#920
#938
#930
#916
#880
#880
#837
#319
### Related merge requests
!2304
!2303
!2299
!2288
!2262
!2139
!1607
Dumux Days #936 #921 #910
__Hard Feature Freeze__ : This means any further changes should be backported to the release branch.
__To be addressed directly during release__
__Done__3.3Kilian WeishauptKilian Weishaupt