dumux issueshttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues2019-04-24T09:59:48Zhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/687CCTpfaFluxVariablesCacheFiller is too specific for porous medium applications2019-04-24T09:59:48ZTimo Kochtimokoch@math.uio.noCCTpfaFluxVariablesCacheFiller is too specific for porous medium applications!1525 shows that the `CCTpfaFluxVariablesCacheFiller` is specific for porous medium flow. It expects stuff like `enableMolecularDiffusion`.
Maybe such information could be moved into the Cache? Or into some physics specific property, se...!1525 shows that the `CCTpfaFluxVariablesCacheFiller` is specific for porous medium flow. It expects stuff like `enableMolecularDiffusion`.
Maybe such information could be moved into the Cache? Or into some physics specific property, set by the individual models?
@DennisGlaeser any idea?3.1Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/688[shallow water] Add friction laws (Manning and Nikuradse)2019-07-01T09:45:38ZMartin Utz[shallow water] Add friction laws (Manning and Nikuradse)The friction laws give she shear stress at the bottom caused by the roughness of the river bed. Within this issue the frictions laws after Manning and Nikuradse are added, but there are also others, which can be added in future.The friction laws give she shear stress at the bottom caused by the roughness of the river bed. Within this issue the frictions laws after Manning and Nikuradse are added, but there are also others, which can be added in future.3.1Martin UtzMartin Utzhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/689Create meaningful new 2pncmin NI test2019-10-09T07:40:46ZSimon EmmertCreate meaningful new 2pncmin NI testWe forgot to add the thermal conductivity law for the 2pncmin **NI** cases because there is no test available. This is addressed in !1560
We should come up with a (in my opinion) **new** test that uses the NI. I think a new test would ...We forgot to add the thermal conductivity law for the 2pncmin **NI** cases because there is no test available. This is addressed in !1560
We should come up with a (in my opinion) **new** test that uses the NI. I think a new test would be beneficial, because the current 2pncmin test is already relatively unstable.3.1Theresa SchollenbergerTheresa Schollenbergerhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/690[material][co2] create co2 tables with pressures less than 1 bar2022-03-30T09:17:22ZKatharina Heck[material][co2] create co2 tables with pressures less than 1 barthe current co2 tables start at 1 bar pressure but in the fluidsystems e.g. brineco2 we calculate e.g. the gas density based on partial pressure (which can be less than 1 bar). That can lead to wrong results if the partial pressure is le...the current co2 tables start at 1 bar pressure but in the fluidsystems e.g. brineco2 we calculate e.g. the gas density based on partial pressure (which can be less than 1 bar). That can lead to wrong results if the partial pressure is less than 1 bar. Then the value of 1 bar is taken from the table and added to the density calculation (which is especially wrong if no co2 is present at all)
Possibly this could be a task for a Hiwi to look into a meaningful relationship for densities etc for co2 and create new tables.3.5Johannes HommelJohannes Hommelhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/691Staggered Lingo Unification2019-04-26T07:09:20ZNed ColtmanStaggered Lingo UnificationWe waste a lot of time getting confused with terms like "lateral", "normal", "parallel", "staggered", "sub-", "frontal", "tangential", and there are of course a few remaining.
Many of these terms actually refer to the same thing. It wou...We waste a lot of time getting confused with terms like "lateral", "normal", "parallel", "staggered", "sub-", "frontal", "tangential", and there are of course a few remaining.
Many of these terms actually refer to the same thing. It would be nice to have rules for when each of these words is used, and to unify their use within the staggered discretization and the freeflow models.
Is this possible?3.1Ned ColtmanNed Coltmanhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/692[staggered] Passing the object of partial(sol) to VtkWriter leads to segfault2019-04-24T10:15:41ZKilian Weishaupt[staggered] Passing the object of partial(sol) to VtkWriter leads to segfaultWhen using the staggered scheme in a multi-domain context, initializing the VtkWriter like
```cpp
auto partialSol = partial(sol);
StaggeredVtkOutputModule<GridVariables,
GetPropType<TypeTag, Properties::Solut...When using the staggered scheme in a multi-domain context, initializing the VtkWriter like
```cpp
auto partialSol = partial(sol);
StaggeredVtkOutputModule<GridVariables,
GetPropType<TypeTag, Properties::SolutionVector>> vtkWriter(*gridVariables, partialSol, name);
```
leads to a segfault.
If the writer is instead initialized like
```cpp
auto partialSol = partial(sol);
StaggeredVtkOutputModule<GridVariables,
decltype(partialSol)> vtkWriter(*gridVariables, partialSol, name);
```
everything works as expected.
Could be related to the fact that `partialSol` only stores references to the actual solution sub-vectors.
It indeed has a different type than `SolutionVector`.
C++17 probably would elegantly fix this, since we could just remove `SolutionVector` from the class template list because it could be inferred from the constructor.3.1Kilian WeishauptKilian Weishaupthttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/693Small timesteps after check points in the time loop2019-05-20T06:28:38ZJohannes HommelSmall timesteps after check points in the time loopRunning some of the lecture exercises, I noticed that when simulations are run with checkpoints in the time loop, it happens that more often than not the time step sizes after the check points are quite small, because the time step size ...Running some of the lecture exercises, I noticed that when simulations are run with checkpoints in the time loop, it happens that more often than not the time step sizes after the check points are quite small, because the time step size before the check point was reduced so it end at the time of the check point. The new time step after the check point may thus start with a minuscule time step size, unnecessarily increasing the number of time steps and thereby simulation time.
In DUMUX 2.12 and older versions, it was possible to use the time step size of the last "full" time step before the check point, back then called episode, to estimate the time step size when continuing after the check point. Thus, for all setups with check points in the time loop, not only the current, but also the previous time step size would need to be stored and the previous time step size would need to be used when estimating the time step size of the time step after a check point.
It might be good to reintroduce such a feature for setups / main.cc-files using check point time loops. However, since this would now need to be done in each .cc file separately, it might be a bit time consuming and repetitive, an ideal DUMUX-day or HIWI task.Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/694replace preprocessor switch USE_PCMAX2019-05-06T17:34:41ZBernd Flemischreplace preprocessor switch USE_PCMAXThere's a preprocessor switch `USE_PCMAX` used in `dumux/porousmediumflow/nonequilibrium/volumevariables.hh` that is set to `1` in `test/porousmediumflow/mpnc/implicit/kinetic/problem.hh`. We should avoid this. Probably by introducing a ...There's a preprocessor switch `USE_PCMAX` used in `dumux/porousmediumflow/nonequilibrium/volumevariables.hh` that is set to `1` in `test/porousmediumflow/mpnc/implicit/kinetic/problem.hh`. We should avoid this. Probably by introducing a flag in the traits of these volume variables?3.1Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/695Failing non-equil tests after merging !14962019-05-04T13:49:31ZTimo Kochtimokoch@math.uio.noFailing non-equil tests after merging !1496After merging !1496 `test_1p2c_nonequilibrium_tpfa` `test_mpnc_kinetic_box` fail now on buildbot.
In the case of `test_1p2c_nonequilibrium_tpfa` an fv geometry cache is accessed which is not in the stencil.
```
Test command: /data/src/...After merging !1496 `test_1p2c_nonequilibrium_tpfa` `test_mpnc_kinetic_box` fail now on buildbot.
In the case of `test_1p2c_nonequilibrium_tpfa` an fv geometry cache is accessed which is not in the stencil.
```
Test command: /data/src/dumux/bin/testing/runtest.py "--script" "fuzzy" "--files" "/data/src/dumux/test/references/test_1p2c_nonequilibrium_tpfa-reference.vtu" "/data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa-00044.vtu" "--command" "/data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa params.input -Problem.Name test_1p2c_nonequilibrium_tpfa" "--zeroThreshold" "{"velocity_liq (m/s)_1":1e-15}"
Test timeout computed to be: 300
You idiot! You signed the order to destroy Earth!
- Douglas Adams, HGttG
Reading parameters from file params.input.
The H2O-N2 fluid system was configured with the following policy:
- use H2O density as liquid mixture density: true
- use ideal gas density: true
- use N2 viscosity as gas mixture viscosity: true
- use N2 heat conductivity as gas mixture heat conductivity: true
- use ideal gas heat capacities: true
-------------------------------------------------------------------------
Initializing tables for the H2O fluid properties (20000 entries).
Temperature -> min: 2.731e+02, max: 6.231e+02, n: 100
Pressure -> min: 0.000e+00, max: 2.000e+07, n: 200
-------------------------------------------------------------------------
problem uses mole fractions
Writing output for problem "test_1p2c_nonequilibrium_tpfa". Took 8.889e-01 seconds.
Assemble: r(x^k) = dS/dt + div F - q; M = grad rtest_1p2c_nonequilibrium_tpfa: /data/src/dumux/dumux/discretization/cellcentered/tpfa/fvelementgeometry.hh:536: const LocalIndexType Dumux::CCTpfaFVElementGeometry::findLocalIndex(Dumux::CCTpfaFVElementGeometry::GridIndexType, const std::vector::GridIndex>&) const [with GG = Dumux::CCTpfaFVGridGeometry > >, false, Dumux::CCTpfaDefaultGridGeometryTraits > >, Dumux::DefaultMapperTraits > >, Dune::MultipleCodimMultipleGeomTypeMapper > >, Dune::Impl::MCMGFailLayout>, Dune::MultipleCodimMultipleGeomTypeMapper > >, Dune::Impl::MCMGFailLayout> > > >; Dumux::CCTpfaFVElementGeometry::LocalIndexType = unsigned int; Dumux::CCTpfaFVElementGeometry::GridIndexType = unsigned int; typename Dumux::IndexTraits::GridIndex = unsigned int]: Assertion `it != indices.end() && "Could not find the scv/scvf! Make sure to properly bind this class!"' failed.
[behandla:19637] *** Process received signal ***
[behandla:19637] Signal: Aborted (6)
[behandla:19637] Signal code: (-6)
[behandla:19637] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890)[0x7f3fc9448890]
[behandla:19637] [ 1] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f3fc9083e97]
[behandla:19637] [ 2] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f3fc9085801]
[behandla:19637] [ 3] /lib/x86_64-linux-gnu/libc.so.6(+0x3039a)[0x7f3fc907539a]
[behandla:19637] [ 4] /lib/x86_64-linux-gnu/libc.so.6(+0x30412)[0x7f3fc9075412]
[behandla:19637] [ 5] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(+0xd0faf)[0x55c4b4287faf]
[behandla:19637] [ 6] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZNK5Dumux41NonEquilibriumLocalResidualImplementationINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaELb0EE11computeFluxERKNS_36OnePTwoCThermalNonequilibriumProblemIS3_EERKN4Dune6EntityILi0ELi2EKNS9_8YaspGridILi2ENS9_22EquidistantCoordinatesIdLi2EEEEENS9_10YaspEntityEEERKNS_23CCTpfaFVElementGeometryINS_20CCTpfaFVGridGeometryINS9_8GridViewINS9_25DefaultLeafGridViewTraitsISF_EEEELb0ENS_31CCTpfaDefaultGridGeometryTraitsISP_NS_19DefaultMapperTraitsISP_NS9_35MultipleCodimMultipleGeomTypeMapperISP_NS9_4Impl14MCMGFailLayoutEEESV_EEEEEELb0EEERKNS_28CCTpfaElementVolumeVariablesINS_21CCGridVolumeVariablesINS_38CCTpfaDefaultGridVolumeVariablesTraitsIS6_NS_43NonEquilibriumVolumeVariablesImplementationINS_27OnePNCVolumeVariablesTraitsINS9_11FieldVectorIdLi4EEENS_12FluidSystems11OnePAdapterINS19_5H2ON2IdNS19_18H2ON2DefaultPolicyILb1EEEEELi0EEENS_24NonEquilibriumFluidStateIdS1F_EENS_12SolidSystems15InertSolidPhaseIdNS_10Components8ConstantILi1EdEEEENS_15InertSolidStateIdS1N_EEdNS_25NonEquilibriumModelTraitsINS_30OnePNCUnconstrainedModelTraitsINS_17OnePNCModelTraitsILi2ELb1ELi2EEEEELb0ELb1ELi1ELi1ELNS_18NusseltFormulationE1ELNS_19SherwoodFormulationE0EEEEENS_21OnePNCVolumeVariablesIS1Y_EELb0ELb1ELi1EEEEELb0EEELb0EEERKNS_26CCTpfaSubControlVolumeFaceISP_NS_31CCTpfaDefaultScvfGeometryTraitsISP_EEEERKNS_31CCTpfaElementFluxVariablesCacheINS_28CCTpfaGridFluxVariablesCacheIS6_NS_44PorousMediumFluxVariablesCacheImplementationIS3_LNS_20DiscretizationMethodE2EEENS_50PorousMediumFluxVariablesCacheFillerImplementationIS3_LS2G_2EEELb0ENS_26CCTpfaDefaultGridFVCTraitsIS6_S2H_S2J_EEEELb0EEE+0x1713)[0x55c4b431b873]
[behandla:19637] [ 7] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZNK5Dumux15CCLocalResidualINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaEE8evalFluxERKNS_36OnePTwoCThermalNonequilibriumProblemIS3_EERKN4Dune6EntityILi0ELi2EKNS9_8YaspGridILi2ENS9_22EquidistantCoordinatesIdLi2EEEEENS9_10YaspEntityEEERKNS_23CCTpfaFVElementGeometryINS_20CCTpfaFVGridGeometryINS9_8GridViewINS9_25DefaultLeafGridViewTraitsISF_EEEELb0ENS_31CCTpfaDefaultGridGeometryTraitsISP_NS_19DefaultMapperTraitsISP_NS9_35MultipleCodimMultipleGeomTypeMapperISP_NS9_4Impl14MCMGFailLayoutEEESV_EEEEEELb0EEERKNS_28CCTpfaElementVolumeVariablesINS_21CCGridVolumeVariablesINS_38CCTpfaDefaultGridVolumeVariablesTraitsIS6_NS_43NonEquilibriumVolumeVariablesImplementationINS_27OnePNCVolumeVariablesTraitsINS9_11FieldVectorIdLi4EEENS_12FluidSystems11OnePAdapterINS19_5H2ON2IdNS19_18H2ON2DefaultPolicyILb1EEEEELi0EEENS_24NonEquilibriumFluidStateIdS1F_EENS_12SolidSystems15InertSolidPhaseIdNS_10Components8ConstantILi1EdEEEENS_15InertSolidStateIdS1N_EEdNS_25NonEquilibriumModelTraitsINS_30OnePNCUnconstrainedModelTraitsINS_17OnePNCModelTraitsILi2ELb1ELi2EEEEELb0ELb1ELi1ELi1ELNS_18NusseltFormulationE1ELNS_19SherwoodFormulationE0EEEEENS_21OnePNCVolumeVariablesIS1Y_EELb0ELb1ELi1EEEEELb0EEELb0EEERKNS_31CCTpfaElementFluxVariablesCacheINS_28CCTpfaGridFluxVariablesCacheIS6_NS_44PorousMediumFluxVariablesCacheImplementationIS3_LNS_20DiscretizationMethodE2EEENS_50PorousMediumFluxVariablesCacheFillerImplementationIS3_LS2A_2EEELb0ENS_26CCTpfaDefaultGridFVCTraitsIS6_S2B_S2D_EEEELb0EEERKNS_26CCTpfaSubControlVolumeFaceISP_NS_31CCTpfaDefaultScvfGeometryTraitsISP_EEEE+0x2e3)[0x55c4b431bf03]
[behandla:19637] [ 8] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZNK5Dumux15FVLocalResidualINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaEE17evalFluxAndSourceERKN4Dune6EntityILi0ELi2EKNS5_8YaspGridILi2ENS5_22EquidistantCoordinatesIdLi2EEEEENS5_10YaspEntityEEERKNS_23CCTpfaFVElementGeometryINS_20CCTpfaFVGridGeometryINS5_8GridViewINS5_25DefaultLeafGridViewTraitsISB_EEEELb0ENS_31CCTpfaDefaultGridGeometryTraitsISL_NS_19DefaultMapperTraitsISL_NS5_35MultipleCodimMultipleGeomTypeMapperISL_NS5_4Impl14MCMGFailLayoutEEESR_EEEEEELb0EEERKNS_28CCTpfaElementVolumeVariablesINS_21CCGridVolumeVariablesINS_38CCTpfaDefaultGridVolumeVariablesTraitsINS_36OnePTwoCThermalNonequilibriumProblemIS3_EENS_43NonEquilibriumVolumeVariablesImplementationINS_27OnePNCVolumeVariablesTraitsINS5_11FieldVectorIdLi4EEENS_12FluidSystems11OnePAdapterINS17_5H2ON2IdNS17_18H2ON2DefaultPolicyILb1EEEEELi0EEENS_24NonEquilibriumFluidStateIdS1D_EENS_12SolidSystems15InertSolidPhaseIdNS_10Components8ConstantILi1EdEEEENS_15InertSolidStateIdS1L_EEdNS_25NonEquilibriumModelTraitsINS_30OnePNCUnconstrainedModelTraitsINS_17OnePNCModelTraitsILi2ELb1ELi2EEEEELb0ELb1ELi1ELi1ELNS_18NusseltFormulationE1ELNS_19SherwoodFormulationE0EEEEENS_21OnePNCVolumeVariablesIS1W_EELb0ELb1ELi1EEEEELb0EEELb0EEERKNS_31CCTpfaElementFluxVariablesCacheINS_28CCTpfaGridFluxVariablesCacheIS12_NS_44PorousMediumFluxVariablesCacheImplementationIS3_LNS_20DiscretizationMethodE2EEENS_50PorousMediumFluxVariablesCacheFillerImplementationIS3_LS28_2EEELb0ENS_26CCTpfaDefaultGridFVCTraitsIS12_S29_S2B_EEEELb0EEERKNS_22CCElementBoundaryTypesE+0x341)[0x55c4b431c3e1]
[behandla:19637] [ 9] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZNK5Dumux20FVLocalAssemblerBaseINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaENS_11FVAssemblerIS3_LNS_10DiffMethodE0ELb1EEENS_16CCLocalAssemblerIS3_S6_LS5_0ELb1EEELb1EE17evalLocalResidualEv+0xd6)[0x55c4b431ccb6]
[behandla:19637] [10] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZN5Dumux16CCLocalAssemblerINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaENS_11FVAssemblerIS3_LNS_10DiffMethodE0ELb1EEELS5_0ELb1EE31assembleJacobianAndResidualImplERN4Dune10BCRSMatrixINS8_11FieldMatrixIdLi4ELi4EEESaISB_EEERNS_27NonEquilibriumGridVariablesIS3_EE+0x74d)[0x55c4b433ef4d]
[behandla:19637] [11] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_ZNK5Dumux11FVAssemblerINS_10Properties4TTag35OnePTwoCThermalNonequilibriumCCTpfaELNS_10DiffMethodE0ELb1EE9assemble_IZNS5_27assembleJacobianAndResidualINS_18PartialReassemblerIS5_EEEEvRKN4Dune11BlockVectorINSA_11FieldVectorIdLi4EEESaISD_EEEPKT_EUlRKNSA_6EntityILi0ELi2EKNSA_8YaspGridILi2ENSA_22EquidistantCoordinatesIdLi2EEEEENSA_10YaspEntityEEEE_EEvOSI_+0x132)[0x55c4b4340b52]
[behandla:19637] [12] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(main+0xeb3)[0x55c4b4282c53]
[behandla:19637] [13] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f3fc9066b97]
[behandla:19637] [14] /data/build/dumux/test/porousmediumflow/1pnc/implicit/nonequilibrium/test_1p2c_nonequilibrium_tpfa(_start+0x2a)[0x55c4b4286a2a]
[behandla:19637] *** End of error message ***
63/186 Test #63: test_1p2c_nonequilibrium_tpfa .....................***Failed 1.82 sec
```
```
Test command: /data/src/dumux/bin/testing/runtest.py "--script" "fuzzy" "--files" "/data/src/dumux/test/references/test_mpnc_kinetic_box-reference.vtu" "/data/build/dumux/test/porousmediumflow/mpnc/implicit/kinetic/test_mpnc_kinetic_box-00011.vtu" "--command" "/data/build/dumux/test/porousmediumflow/mpnc/implicit/kinetic/test_mpnc_kinetic_box params.input -Problem.Name test_mpnc_kinetic_box"
Test timeout computed to be: 300
Chuck Norris has successfully compiled DuMuX.
Reading parameters from file params.input.
The H2O-N2 fluid system was configured with the following policy:
- use H2O density as liquid mixture density: true
- use ideal gas density: true
- use N2 viscosity as gas mixture viscosity: true
- use N2 heat conductivity as gas mixture heat conductivity: true
- use ideal gas heat capacities: true
-------------------------------------------------------------------------
Initializing tables for the H2O fluid properties (10000 entries).
Temperature -> min: 2.780e+02, max: 4.531e+02, n: 100
Pressure -> min: 7.500e+04, max: 2.250e+05, n: 100
-------------------------------------------------------------------------
Writing output for problem "test_mpnc_kinetic_box". Took 6.039e-01 seconds.
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.278e+00(4.768e+01%)/1.402e+00(5.231e+01%)/3.405e-04(1.270e-02%)
Writing output for problem "test_mpnc_kinetic_box". Took 4.812e-02 seconds.
[ 1%] Time step 1 done in 2.736643 seconds. Wall clock time: 2.785, time: 0.05000, time step size: 0.05000000
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 0.95099143(48.46939834%)/1.01091940(51.52376100%)/0.00013422(0.00684067%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04853347 seconds.
[ 1%] Time step 2 done in 2.051791 seconds. Wall clock time: 4.837, time: 0.12500, time step size: 0.07500000
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 0.94914820(48.59345643%)/1.00394319(51.39879041%)/0.00015144(0.00775316%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04807224 seconds.
[ 2%] Time step 3 done in 2.043512 seconds. Wall clock time: 6.880, time: 0.24375, time step size: 0.11875000
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 0.95115055(48.39749146%)/1.01398697(51.59480356%)/0.00015143(0.00770497%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04845110 seconds.
[ 4%] Time step 4 done in 2.055532 seconds. Wall clock time: 8.936, time: 0.43177, time step size: 0.18802083
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 0.95967631(48.69862390%)/1.01083155(51.29448896%)/0.00013572(0.00688714%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04814657 seconds.
[ 7%] Time step 5 done in 2.060660 seconds. Wall clock time: 10.996, time: 0.72947, time step size: 0.29769965
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.26521772(48.89266931%)/1.32233187(51.09977040%)/0.00019564(0.00756029%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04806234 seconds.
[ 12%] Time step 6 done in 2.691426 seconds. Wall clock time: 13.688, time: 1.20083, time step size: 0.47135778
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.27771621(48.82405213%)/1.33907903(51.16884610%)/0.00018585(0.00710177%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04817870 seconds.
[ 19%] Time step 7 done in 2.720932 seconds. Wall clock time: 16.409, time: 1.90786, time step size: 0.70703668
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.27635560(48.32649627%)/1.36457241(51.66663862%)/0.00018132(0.00686511%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04837157 seconds.
[ 30%] Time step 8 done in 2.745505 seconds. Wall clock time: 19.154, time: 2.96842, time step size: 1.06055501
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.28703688(48.70908916%)/1.35506024(51.28349543%)/0.00019594(0.00741542%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04841897 seconds.
[ 46%] Time step 9 done in 2.747992 seconds. Wall clock time: 21.902, time: 4.55925, time step size: 1.59083252
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.27011454(48.08293266%)/1.37121299(51.91023325%)/0.00018052(0.00683409%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04838746 seconds.
[ 69%] Time step 10 done in 2.745616 seconds. Wall clock time: 24.648, time: 6.94550, time step size: 2.38624878
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble: r(x^k) = dS/dt + div F - q; M = grad r
Assemble/solve/update time: 1.27372658(48.61208584%)/1.34627708(51.38099319%)/0.00018134(0.00692096%)
Writing output for problem "test_mpnc_kinetic_box". Took 0.04840041 seconds.
[100%] Time step 11 done in 2.725102 seconds. Wall clock time: 27.373, time: 10.00000, time step size: 3.05449874
Simulation took 27.37315323 seconds on 1 processes.
The cumulative CPU time was 27.37315323 seconds.
# Runtime-specified parameters used:
[ BoundaryConditions ]
TInject = "293"
massFluxInjectedPhase = "0.75"
percentOfEquil = ".1"
[ Component ]
SolidDensity = "2600"
SolidHeatCapacity = "817"
SolidThermalConductivity = "3"
[ FluidSystem ]
nPressure = "100"
nTemperature = "100"
[ Grid ]
Cells0 = "14"
Cells1 = "15 15"
Grading0 = "1.0"
Grading1 = "-0.833333 0.833333"
Positions0 = "0.0 1.0"
Positions1 = "0.0 0.25 0.5"
[ InitialConditions ]
SwFFInitial = "1e-4"
SwPMInitial = "0.8"
TInitial = "293"
pnInitial = "1e5"
pnInjection = "100003"
[ Problem ]
Name = "test_mpnc_kinetic_box"
[ SpatialParams ]
[ SpatialParams.FreeFlow ]
meanPoreSize = "1e-2"
permeability = "1e-6"
porosity = "0.99"
[ SpatialParams.PorousMedium ]
factorEnergyTransfer = "1"
factorMassTransfer = "1"
meanPoreSize = "1e-4"
permeability = "1e-11"
porosity = "0.4"
[ SpatialParams.soil ]
BCPd = "2.290e+03"
BClambda = "2.740e+00"
Snr = "0"
Swr = "0"
aNonWettingSolidA1 = "1.369e+03"
aNonWettingSolidA2 = "-3.782e+00"
aNonWettingSolidA3 = "1.063e-09"
aWettingNonWettingA1 = "-1.603e-01"
aWettingNonWettingA2 = "1.429e-05"
aWettingNonWettingA3 = "1.915e-01"
[ TimeLoop ]
DtInitial = "0.05"
TEnd = "10"
[ Vtk ]
AddVelocity = "1"
# Global default parameters used:
[ Assembly ]
NumericDifferenceMethod = "1"
[ Flux ]
UpwindWeight = "1.0"
[ LinearSolver ]
MaxIterations = "250"
PreconditionerIterations = "1"
PreconditionerRelaxation = "1.0"
ResidualReduction = "1e-13"
Verbosity = "0"
[ Newton ]
EnableAbsoluteResidualCriterion = "false"
EnableChop = "false"
EnablePartialReassembly = "false"
EnableResidualCriterion = "false"
EnableShiftCriterion = "true"
MaxAbsoluteResidual = "1e-5"
MaxRelativeShift = "1e-8"
MaxSteps = "18"
ResidualReduction = "1e-5"
SatisfyResidualAndShiftCriterion = "false"
TargetSteps = "10"
UseLineSearch = "false"
[ Problem ]
EnableGravity = "true"
[ TimeLoop ]
MaxTimeStepSize = "1e300"
[ Vtk ]
AddProcessRank = "true"
# Unused parameters:
SpatialParams.soil.VGAlpha = "3.512e-04"
SpatialParams.soil.VGN = "4.716e+00"
SpatialParams.soil.specificSolidsurface = "4022.994"
SourceSink.heatIntoSolid = "0"
Constants.nRestart = "100"
FluidSystem.hammer = "1e4"
Chuck Norris has compiled DuMuX even two times in a row!
Fuzzy comparison...
Comparing /data/src/dumux/test/references/test_mpnc_kinetic_box-reference.vtu and /data/build/dumux/test/porousmediumflow/mpnc/implicit/kinetic/test_mpnc_kinetic_box-00011.vtu
... with a maximum relative error of 0.01 and a maximum absolute error of 1.5e-07*max_abs_parameter_value.
Data differs in parameter: velocity_gas (m/s)_1
Difference is too large: 8.70% -> between: 1.91128e-06 and 1.74495e-06
Info for velocity_gas (m/s)_1: max_abs_parameter_value=0.564606 and min_abs_parameter_value=1.74495e-06.
Data differs in parameter: velocity_liq (m/s)_0
Difference is too large: 1.00% -> between: 6.90209e-08 and 6.97191e-08
Info for velocity_liq (m/s)_0: max_abs_parameter_value=7.2564e-08 and min_abs_parameter_value=8.35171e-16.
Data differs in parameter: x^H2O_gas
Difference is too large: 55.46% -> between: 0.023197 and 0.0103322
Info for x^H2O_gas: max_abs_parameter_value=0.0232059 and min_abs_parameter_value=0.00232059.
Data differs in parameter: x^N2_gas
Difference is too large: 1.30% -> between: 0.976803 and 0.989668
Info for x^N2_gas: max_abs_parameter_value=0.997679 and min_abs_parameter_value=0.976794.
Test #155: test_mpnc_kinetic_box .............................***Failed 29.19 sec
```3.1Katharina HeckKatharina Heckhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/696Move gravity to spatial parameters?2019-05-03T07:19:19ZTimo Kochtimokoch@math.uio.noMove gravity to spatial parameters?Gravity is part of the porous medium problem interface. I don't see why though..
Should we better move the interface to the spatial params?Gravity is part of the porous medium problem interface. I don't see why though..
Should we better move the interface to the spatial params?Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/697[shallowwater] Complete the doxygen documentation2019-05-13T14:33:48ZMartin Utz[shallowwater] Complete the doxygen documentationThe doxygen documentation for the shallow water part does not work properly, because the modules.txt is not updated. After fixing that, in general the shallowwater doxygen documentation shall be tested.
* [x] Add entry in modules.txt fo...The doxygen documentation for the shallow water part does not work properly, because the modules.txt is not updated. After fixing that, in general the shallowwater doxygen documentation shall be tested.
* [x] Add entry in modules.txt for ShallowWater
* [x] Check that all classes and functions have a docstring
* [x] Document ShallowWaterFlux classMartin UtzMartin Utzhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/698Installation2019-05-30T23:32:27ZLarry FranksInstallationGents I have just completed a DUMUX installation but it took a long time. The script on you web site did not work, it has errors. I eventually used the git method in your manual and the Dumux coarse finally installed everything and wor...Gents I have just completed a DUMUX installation but it took a long time. The script on you web site did not work, it has errors. I eventually used the git method in your manual and the Dumux coarse finally installed everything and worked. You also need to tell people that they need Paraview, gnuplot and gfortran installed before it all works, I only found this from the error files.https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/699VTKReader can't read polydata with lines with more than 2 points2019-05-13T15:25:55ZTimo Kochtimokoch@math.uio.noVTKReader can't read polydata with lines with more than 2 pointsThe format allows to specify poly lines with many points. The reader currently expects each line to be a line element with two points.The format allows to specify poly lines with many points. The reader currently expects each line to be a line element with two points.Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/700Test virtual interface for Problem2019-10-30T10:02:28ZTimo Kochtimokoch@math.uio.noTest virtual interface for ProblemGetting rid of the problem template would be a huge improvement in the code.
We should do performance measurement and check what run-time penalty a virtual problem interface would bring.
For that we have to first check which functions ac...Getting rid of the problem template would be a huge improvement in the code.
We should do performance measurement and check what run-time penalty a virtual problem interface would bring.
For that we have to first check which functions actually need to be virtual, add the virtual keyword, we could then exchange templates for a base class pointer one-by-one, and check for performance penalties.
The highest penalty is probably expected for a grid with a high boundary to internal cell ratio, and simple boundary and initial conditions so that the possible virtual function call would actually matter.Dennis GläserDennis Gläserhttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/701[fluidsystems] TwoPImmiscible returns the same phase name when used with two ...2019-05-17T13:46:02ZKilian Weishaupt[fluidsystems] TwoPImmiscible returns the same phase name when used with two OnePLiquid<ConstantComponent> systemsWhen using
```cpp
template<class TypeTag>
struct FluidSystem<TypeTag, TTag::MyProblem>
{
using Scalar = GetPropType<TypeTag, Properties::Scalar>;
using Component1 = Components::Constant<1, Scalar>;
using Component2 = Comp...When using
```cpp
template<class TypeTag>
struct FluidSystem<TypeTag, TTag::MyProblem>
{
using Scalar = GetPropType<TypeTag, Properties::Scalar>;
using Component1 = Components::Constant<1, Scalar>;
using Component2 = Components::Constant<2, Scalar>;
using Phase1 = Dumux::FluidSystems::OnePLiquid<Scalar, Component1>;
using Phase2 = Dumux::FluidSystems::OnePLiquid<Scalar, Component2>;
using type = Dumux::FluidSystems::TwoPImmiscible<Scalar, Phase1, Phase2>;
};
```
The phase name returned by `TwoPImmiscible` is always `napl` due to the trait
``` cpp
template <class Component>
struct IsAqueous : public std::false_type {};
```
defined in `dumux/material/components/constant.hh`
This makes the fluid system unusable, because ParaView segfaults when attempting to load to vtk file.
Should we include the choice to specify names as runtime parameters?3.1https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/702[boxAssembly] Setting Dirichlet BCs fails for explicit box assembly2019-05-17T13:46:19ZKilian Weishaupt[boxAssembly] Setting Dirichlet BCs fails for explicit box assemblyFor box, Dirichlet BCs are applied in `BoxLocalAssemblerBase`
```cpp
res[scvI.dofIndex()][eqIdx] = this->curElemVolVars()[scvI].priVars()[pvIdx] - dirichletValues[pvIdx];
for (const auto& scvJ : scvs(this->fvGeom...For box, Dirichlet BCs are applied in `BoxLocalAssemblerBase`
```cpp
res[scvI.dofIndex()][eqIdx] = this->curElemVolVars()[scvI].priVars()[pvIdx] - dirichletValues[pvIdx];
for (const auto& scvJ : scvs(this->fvGeometry()))
{
jac[scvI.dofIndex()][scvJ.dofIndex()][eqIdx] = 0.0;
if (scvI.localDofIndex() == scvJ.localDofIndex())
jac[scvI.dofIndex()][scvI.dofIndex()][eqIdx][pvIdx] = 1.0;
}
```
The offending line is `jac[scvI.dofIndex()][scvJ.dofIndex()][eqIdx] = 0.0;` since in the explicit case, there are only diagonal entries in Jacobian. A dune-istl error will be raised.3.1https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/703Spatial parameters cannot be time dependent if not solution-dependent2023-02-22T08:58:07ZTimo Kochtimokoch@math.uio.noSpatial parameters cannot be time dependent if not solution-dependentIf we compute the tracer model in combination with a fluid that changes properties over time, we
need the old properties to evaluate the storage.
The problem is, the volvars currently don't know anything about time, so we can't pass tha...If we compute the tracer model in combination with a fluid that changes properties over time, we
need the old properties to evaluate the storage.
The problem is, the volvars currently don't know anything about time, so we can't pass that information
to the spatial params. That's why we currently assume that all secondary variables are either constant
or solution-dependent but not time-dependent without being solution-dependent. This is a big drawback
in general and a bug or at least an imprecision in the tracer model.https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/704Multiphase tracer produces singular matrix if saturation is zero2020-03-30T20:16:38ZTimo Kochtimokoch@math.uio.noMultiphase tracer produces singular matrix if saturation is zeroA case that is like in two-phase models is that one phase disappears. If the tracer only exists in this
phase, the tracer also disappear, however that means that the local equation/residual degenerates.
This is automatically the case fo...A case that is like in two-phase models is that one phase disappears. If the tracer only exists in this
phase, the tracer also disappear, however that means that the local equation/residual degenerates.
This is automatically the case for all dofs where saturation is zero (over the whole time integration interval, see #703).
A robust solution could be to check for zero saturation and replace the equation for those dofs with the Dirichlet constraint that the concentration is zero. For that it would need to be possible to set Dirichlet for every dof even when not on the boundary, see #704.3.2Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/705Additional Dirichlet constraints2019-07-15T12:06:44ZTimo Kochtimokoch@math.uio.noAdditional Dirichlet constraintsI would be nice to be able to set Dirichlet constraints for any dof in the problem.
The assembler could ask the problem if it defines additional constraints (constexpr bool func or by member function inspection (probably too magical)) an...I would be nice to be able to set Dirichlet constraints for any dof in the problem.
The assembler could ask the problem if it defines additional constraints (constexpr bool func or by member function inspection (probably too magical)) and if yes implement these constraints after the assembly.
This feature could fix e.g. #704. However I'm having problems to come up with other used cases, maybe some overlapping domain decomposition stuff.Timo Kochtimokoch@math.uio.noTimo Kochtimokoch@math.uio.nohttps://git.iws.uni-stuttgart.de/dumux-repositories/dumux/-/issues/706Add turbulent diffusion to shallow water model2021-02-26T21:39:05ZFrank PlatzekAdd turbulent diffusion to shallow water modelThe preliminary turbulent diffusion implementation in the shallow water model from Issue #657
(Turbulent diffusion in shallow water equations), is to be merged in the new structure for the shallow water model as part of the Freeflow model.The preliminary turbulent diffusion implementation in the shallow water model from Issue #657
(Turbulent diffusion in shallow water equations), is to be merged in the new structure for the shallow water model as part of the Freeflow model.Frank PlatzekFrank Platzek