Hi Nikolai,

this should lead you directly to the commit where this was fixed:


https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/commit/1fb7860720c08942c4166070b27bb138815a1be5


By prescribing both pressure and saturation at a Dirichlet boundary, pn will be constant at the boundary. In fact it will be the prescribed pressure + the capillary pressure resulting from the given boundary saturation. So you should not need the changes to darcys law that you have made. However, as Timo mentioned already, when using a cell-centered scheme you will not see the exact boundary value in your vtu files.


I would strongly recommend you use the unmodified Darcy's law and make sure to cherry-pick the commit I mentioned or pull the newest dumux version. Hopefully this solves the issue!


Best wishes,
Dennis



On 20.08.2018 11:17, Nikolai Andrianov wrote:

Hi Dennis,


I just modified my local discretization/cellcentered/tpfa/darcyslaw.hh as follows near line 207:


            // Obtain inside and outside pressures
            //const auto pInside = insideVolVars.pressure(phaseIdx);
            //const auto pOutside = outsideVolVars.pressure(phaseIdx);

            Scalar pInside, pOutside;
            if (!scvf.boundary()) {

                // Inside the domain calculate the phase flux using phase pressures (with pn = pw + pc)
                pInside = insideVolVars.pressure(phaseIdx);
                pOutside = outsideVolVars.pressure(phaseIdx);
            }
            else {
                // Do not include the contributions from capillary forces for boundary fluxes //static_assert( (VolumeVariables::priVarFormulation() == TwoPFormulation::p0s1), "darcyslaw.hh: BC implemented for p0s1 formulation only!");       // uncommenting this yields an error
                // WARNING: implemented for p1s0 formulation only!
                pInside = insideVolVars.pressure(1);
                pOutside = outsideVolVars.pressure(1);
            }

Without this modification, I was not able to keep pn constant at Dirichlet boundaries. As you see, the modification is hard-coded for the p1s0 formulation.


No, I did not pull any recent dumux versions because I did not want to get stuck with compiling of possible incompatibilities 😊 (I work with the version from the dumux-course). Can you please point out which files have been modified to fix the bug you are mentioning? Or which commit should I be looking for?


Thanks,

Nikolai


------------------------------------------------------------------------
*From:* Dumux <[email protected]> on behalf of Dennis Gläser <[email protected]>
*Sent:* Monday, August 20, 2018 10:25:06 AM
*To:* [email protected]
*Subject:* Re: [DuMuX] Linear solver crashes in release mode, but not in debug mode

Hi Nikolai,


I am sorry if I missed your previous posts and this question is obsolete, but can you tell us what you mean by having corrected darcyslaw.hh? I checked your repository but couldn't find a modified version of the file, neither a respective branch in the dumux repository. So I assume you have a locally modified version of the file on your system?


There used to be a bug in the two-phase model with respect to the p1s0 formulation. That has been fixed about three weeks ago, have you pulled dumux eversince?


Let us know if this helps!


Cheers,
Dennis



On 17.08.2018 19:49, Nikolai Andrianov wrote:

Dear DuMuX experts,


Please advise what can cause the following bizarre error: the code compiled with debug options runs smoothly but the same code compiled with release options crashes in the linear solver with the following message:


Solve: M deltax^k = rNewton: Caught exception: "SolverAbort [apply:/home/nikolai/dumux/dune-istl/dune/istl/solvers.hh:628]: breakdown in BiCGSTAB - rho 0 <= EPSILON 1e-80 after 87.5 iterations"


This error pops up when working on a modified version of the exercise-fractures test cases from dumux-course. Apart from modifying the -problem.hh and -spatialparams.hh files, I have also corrected darcyslaw.hh and switched the formulation to p1s0 (as described in my previous post).


Compilation .opts files are attached.


May thanks,

Nikolai




_______________________________________________
Dumux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux



_______________________________________________
Dumux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

_______________________________________________
Dumux mailing list
[email protected]
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Reply via email to