[DuMux] Unknown CMake command "add_dune_alugrid_flags"

[Ranjeet kumar]

Hi

Currently, I am using dumux3.2 and it works fine. I am trying to update it
to dumux3.4 but I am getting an error:

CMake Error at cmake/modules/DumuxTestMacros.cmake:63
(add_dune_alugrid_flags):  Unknown CMake command
"add_dune_alugrid_flags".Call Stack (most recent call first):
cmake/modules/DumuxTestMacros.cmake:41 (add_dumux_all_flags)
test/common/generalproblem/CMakeLists.txt:3 (add_dumux_test)--
Configuring incomplete, errors occurred!See also
"/home/ranjeet/dumuxProjects/dumux3.4/dumux/build-cmake/CMakeFiles/CMakeOutput.log".See
also 
"/home/ranjeet/dumuxProjects/dumux3.4/dumux/build-cmake/CMakeFiles/CMakeError.log".---
Failed to build dumux ---

Regards,

Ranjeet
___
DuMux mailing list
DuMux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

[DuMux] How to modify governing equation in Dumux?

[Ranjeet kumar]

Dear Dumux Developers,
I want to develop a model for single-phase flow in deformable porous media.
For this, I am using dumux3.2, module
"dumux/test/multidomain/poromechanics/el1p".

As per my understanding, the Implementation of the governing equation for
the poroelastic model is slightly different in dumux(please see here
).
This gives little difference in values when compared to other
implementations, however, the shape/nature of the results are the same.  I
want to do little modification

in the governing equations but not sure how to do it. I will appreciate you
could explain in which file & functions, each term of mass balance equation
and momentum balance equation has been implemented in dumux3.2?


[image: dumex.png]

Modification:
https://drive.google.com/file/d/1nFbULq0Qi082LoN_iMXP2CubngUh7Y1y/view?usp=sharing
Code: https://github.com/rksin8/dumux-el1p


Regards,
Ranjeet
___
DuMux mailing list
DuMux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] Sign convention in el2p module in Dumux3.1

[Ranjeet kumar]

Hi Dennis,
Thank you for making things clear. But I still have few doubts.  I am using
dumux/test/multidomain/poromechanics/el2p example for my model. In
spatialparams_2p.hh, both deformation dependent porosity and  deformation
dependent permeability are being evaluated while in
*spatialparams_poroelastic.hh*, deformation dependent porosity is being
evaluated.  In the base class "FVSpatialParamsPoroElastic", there is no
method for the permeability calculation. Now I am confused, not sure which
case is being solved here.  Would  you please explain implementation
differences for the both cases?

Also, I really appreciate if you could point out the 3.2 branch to use
deformation-dependent porosities model.


Thanks & Regards,
Ranjeet


On Wed, Apr 1, 2020 at 7:02 PM Dennis Gläser <
dennis.glae...@iws.uni-stuttgart.de> wrote:

> Hi Ranjeet,
>
> regarding the formulation: there are no publications using the
> poromechanics module of Dumux 3, yet. But, you can have a look at the PhD
> thesis of Martin Beck:
>
> https://elib.uni-stuttgart.de/bitstream/11682/10435/3/Promo_MartinBeck.pdf
>
> and in particular the sections 3.1.1 and 3.1.2. Equation 3.6 states the
> momentum balance equation of the porous medium right before the
> linearization. This is what is currently solved in Dumux. This implies that
> you should have knowledge about your initial stress/deformation conditions,
> or, solve for them primarily. In other words, if you initialize your system
> with non-zero fluid pressures, you will observe stresses/deformations
> caused by the initial conditions. If gravity is neglected and
> incompressible fluids are considered, you could start your simulation with
> zero pressure and zero displacement.
>
> Regarding the deformation-dependent porosities: That depends on your
> application. Currently, there is an issue with the coupling derivatives of
> the storage term, and thus, if the porosity is chosen
> deformation-dependent, the non-linear solver convergence deteriorates
> significantly. On the other hand, deformation-dependent permeabilities work
> fine.
>
> We are planning to fix this issue very soon and hope that you want to use
> Dumux for you application. We will not be able to fix it until the 3.2
> release which is scheduled for a few weeks from now. If you want, I can
> point you to a fix branch on which the bugfix is done in an unsatisfactory
> way, but on that branch you could develop your application for now. Once we
> have solved the problem you could switch back to the release branch.
>
> Regards,
> Dennis
>
>
> On 29.03.20 15:01, Ranjeet kumar wrote:
>
> Hi All,
> I want to develop a poroelastic model using el2p module in Dumux 3.1. As
> per Dumux2.12 class documentation,  soil mechanics sign convention (i.e.
> compressive stresses are negative) has been used in el2p module. However,
> papers & thesis based on Dumux2 has used opposite sign convention. Can you
> clarify which sign convention is being used in Dumux3.1?
>
> Q2. As a linearised form of momentum balance equation is being solved in
> el2p model, the solution effective stress obtained from:
>
> const auto effSigma = StressType::effectiveStressTensor(*this, element,
> fvGeometry, elemVolVars, fluxVarsCache);
>
> is the total effective stress or change in effective stress with respect
> to initial effective stress?
>
>
> References:
> 1. p-3, Volume-Based Modelling of Fault Reactivation in Porous Media Using
> a Visco-Elastic Proxy Model.  Martin Beck1 · Gabriele Seitz1 · Holger Class1
> 2. p-3, Modelling fault reactivation with characteristic stress-drop
> terms. Martin Beck and Holger Class
> 3. p68-69, Coupling Models of Different Complexity for the Simulation of
> CO2 Storage in Deep Saline Aquifers
>
>
> Thank you,
>
> Regards,
> Ranjeet
>
>
> ___
> Dumux mailing 
> listdu...@listserv.uni-stuttgart.dehttps://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
>
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

[DuMuX] Sign convention in el2p module in Dumux3.1

[Ranjeet kumar]

Hi All,
I want to develop a poroelastic model using el2p module in Dumux 3.1. As
per Dumux2.12 class documentation,  soil mechanics sign convention (i.e.
compressive stresses are negative) has been used in el2p module. However,
papers & thesis based on Dumux2 has used opposite sign convention. Can you
clarify which sign convention is being used in Dumux3.1?

Q2. As a linearised form of momentum balance equation is being solved in
el2p model, the solution effective stress obtained from:

const auto effSigma = StressType::effectiveStressTensor(*this, element,
fvGeometry, elemVolVars, fluxVarsCache);

is the total effective stress or change in effective stress with respect to
initial effective stress?


References:
1. p-3, Volume-Based Modelling of Fault Reactivation in Porous Media Using
a Visco-Elastic Proxy Model.  Martin Beck1 · Gabriele Seitz1 · Holger Class1
2. p-3, Modelling fault reactivation with characteristic stress-drop terms.
Martin Beck and Holger Class
3. p68-69, Coupling Models of Different Complexity for the Simulation of
CO2 Storage in Deep Saline Aquifers


Thank you,

Regards,
Ranjeet
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] How to implement el2p for heterogeneous problem?

[Ranjeet kumar]

Hi Dennis,
Thank you for your reply. You got it correctly, difference in plot due to
vertex-wise output of an element-wise field.
As I haven't implemented any code to write porosity to vtk file, I think,
porosity() should returns  porosity with respect to vertex instead of cell.
if this is true, how one can construct the value at vertex from the cell
values?.

Regards,
Ranjeet



On Thu, Feb 14, 2019 at 3:54 AM Dennis Gläser <
dennis.glae...@iws.uni-stuttgart.de> wrote:

> Hi Ranjeet,
>
> I don't get the "issue" you mentioned. What exactly is the problem? To me
> your implementation seems fine.
>
> If you refer to the porosity output you obtained in the el-problem, it
> just looks like this is because you are using vertex-wise output of an
> element-wise field.
>
> Best wishes,
> Dennis
>
>
> On 13.02.19 05:00, Ranjeet kumar wrote:
>
> Dear All,
> I am trying to implement multidoamin/poromechanics/el2p for heterogeneous
> problem.
> Considering the value of porosity and permeability are stored in vector
> initPoro_ and initK_ respectively.  Porosity and permeability is returned
> using element Idx in their respective methods.
>
> //! Returns the porosity of the porous medium.
> template
> Scalar porosity(const Element& element,
> const SubControlVolume& scv,
> const ElementSolution& elemSol) const
> {
> const auto eIdx =
> this->fvGridGeometry().elementMapper().index(element);
> return
> PorosityDeformation::evaluatePorosity(this->fvGridGeometry(),
> element, scv, elemSol, initPoro_[eIdx]);
> }
>
> The porosity output for 2p and poroelastic are different (can be viewed
> using below link):
> https://home.iitb.ac.in/index.php/s/M7b0ZpTNFt5Wesr (2p)
> https://home.iitb.ac.in/index.php/s/uJFpUoq6rtxQo25  (el)
>
> Could you please give some idea the fix the above issue?
>
> Thank You,
>
> Regards,
> Ranjeet
>
>
>
>
>
>
>
>
>
>
> ___
> Dumux mailing 
> listdu...@listserv.uni-stuttgart.dehttps://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
>
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

[DuMuX] How to implement el2p for heterogeneous problem?

[Ranjeet kumar]

Dear All,
I am trying to implement multidoamin/poromechanics/el2p for heterogeneous
problem.
Considering the value of porosity and permeability are stored in vector
initPoro_ and initK_ respectively.  Porosity and permeability is returned
using element Idx in their respective methods.

//! Returns the porosity of the porous medium.
template
Scalar porosity(const Element& element,
const SubControlVolume& scv,
const ElementSolution& elemSol) const
{
const auto eIdx =
this->fvGridGeometry().elementMapper().index(element);
return
PorosityDeformation::evaluatePorosity(this->fvGridGeometry(),
element, scv, elemSol, initPoro_[eIdx]);
}

The porosity output for 2p and poroelastic are different (can be viewed
using below link):
https://home.iitb.ac.in/index.php/s/M7b0ZpTNFt5Wesr (2p)
https://home.iitb.ac.in/index.php/s/uJFpUoq6rtxQo25  (el)

Could you please give some idea the fix the above issue?

Thank You,

Regards,
Ranjeet
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] Fwd: Re: how to add stresses to output file for multidomain-el2p problem

[Ranjeet kumar]

Dear Dennis,
Thank you for your response. Implementing binding using couplingManager
solved the issue.

Also, Initially problem was mailed to the dumux mailing list. I should have
replied to all, sorry for that. Thank you for sharing this with me, I'll
keep it in mind.

Regards,
Ranjeet


On Tue, Jan 29, 2019 at 9:55 PM Dennis Gläser <
dennis.glae...@iws.uni-stuttgart.de> wrote:

> Dear Ranjeet,
>
> please ask your questions to the mailing list so that other people can
> profit from this discussion, too.
>
> If you implemented your stress output similar to the way as it is done in
> the UNCOUPLED poroelastic test case (which does not use multidomain), then
> it is clear where the error comes from.
>
> Currently, in the multidomain framework, a "coupling context" is
> precomputed prior to element-local calculations. This is done in the
> assembler before starting the assembly of element-local entries in the
> global system matrix. This concept was introduced to speed up the
> computations and it is somewhat similar to what you do with the geometry
> and the volume variables, i.e.:
>
> fvGeometry.bind( ... )
>
> elemVolVars.bind( ... )
>
> For the coupling context the call is done on the coupling manager:
>
> couplingManager.bindCouplingContext(domainId, element, assembler)
>
>
> This precomputes all variables of the other domain that are necessary for
> computations on the element of your current domain. So in your element loop
> of the stress computation you would have to do this call PRIOR to the
> element volume variables bind() call.
>
> We are not happy with this and are currently working on getting rid of the
> necessity of this call. Until then, you will have to pass the assembler to
> your stress computation routine in order to realize the
> bindCouplingContext() call before computing the element stresses. Sorry
> about that!
>
> Let us know if this fixes your problem!
>
> Best wishes,
> Dennis
>
>
>
>
> On 29.01.19 10:25, Timo Koch wrote:
>
>
>
>
> ---- Forwarded Message 
> Subject: Re: [DuMuX] how to add stresses to output file for
> multidomain-el2p problem
> Date: Tue, 29 Jan 2019 19:52:41 +1100
> From: Ranjeet kumar  
> To: Timo Koch 
> 
>
> Thank you for the reply.
>
> As per gdb & valgrind, problem seems coming from the:
> const auto effPress = problem.effectivePorePressure(element, fvGeometry,
> elemVolVars, fluxVarsCache); and hence from:
> const auto sigma = StressType::stressTensor(problem, element, fvGeometry,
> elemVolVars, fluxVarsCache);
>
> I have attached the valgrind log file. If you could give some idea to
> solve this, it will be great helpful.
>
>
>
> On Thu, Jan 24, 2019 at 7:18 PM Timo Koch 
> wrote:
>
>> Hi Ranjeet,
>>
>> please use a debugging tool like valgrind to find where your segmentation
>> fault comes from. Maybe then we can help.
>>
>> Timo
>>
>> > Am 24.01.2019 um 08:08 schrieb Ranjeet kumar :
>> >
>> > Hi All,
>> > I want to add stresses value to the vtu file for the el2p problem.
>> Based on geomechanics/poroselastic/main.cc, I tried to implementing the
>> same for el2p problem. But I getting error segmentation fault error.
>> >
>> > // function to evaluate the element stresses
>> > template< class StressType,
>> >   class Problem,
>> >   class GridGeometry,
>> >   class GridVariables,
>> >   class SolutionVector,
>> >   class SigmaStorage>
>> > void assembleElementStresses(SigmaStorage& sigmaStorage,
>> >  SigmaStorage& effSigmaStorage,
>> >  const Problem& problem,
>> >  const GridGeometry& fvGridGeometry,
>> >  const GridVariables& gridVariables,
>> >  const SolutionVector& x)
>> > {
>> > for (const auto& element : elements(fvGridGeometry.gridView()))
>> > {
>> > auto fvGeometry = localView(fvGridGeometry);
>> > auto elemVolVars = localView(gridVariables.curGridVolVars());
>> >
>> > fvGeometry.bind(element);
>> > elemVolVars.bind(element, fvGeometry, x);
>> >
>> > // evaluate flux variables cache at cell center
>> > using FluxVarsCache = typename
>> GridVariables::GridFluxVariablesCache::FluxVariablesCache;
>> > FluxVarsCache fluxVarsCache;
>> > fluxVarsCache.update(problem, element, fvGeome

[DuMuX] how to add stresses to output file for multidomain-el2p problem

[Ranjeet kumar]

Hi All,
I want to add stresses value to the vtu file for the el2p problem. Based on
geomechanics/poroselastic/main.cc, I tried to implementing the same for
el2p problem. But I getting error segmentation fault error.

// function to evaluate the element stresses
template< class StressType,
  class Problem,
  class GridGeometry,
  class GridVariables,
  class SolutionVector,
  class SigmaStorage>
void assembleElementStresses(SigmaStorage& sigmaStorage,
 SigmaStorage& effSigmaStorage,
 const Problem& problem,
 const GridGeometry& fvGridGeometry,
 const GridVariables& gridVariables,
 const SolutionVector& x)
{
for (const auto& element : elements(fvGridGeometry.gridView()))
{
auto fvGeometry = localView(fvGridGeometry);
auto elemVolVars = localView(gridVariables.curGridVolVars());

fvGeometry.bind(element);
elemVolVars.bind(element, fvGeometry, x);

// evaluate flux variables cache at cell center
using FluxVarsCache = typename
GridVariables::GridFluxVariablesCache::FluxVariablesCache;
FluxVarsCache fluxVarsCache;
fluxVarsCache.update(problem, element, fvGeometry, elemVolVars,
element.geometry().center());

//get lame parameters, the pressure and compute stress tensor
const auto sigma = StressType::stressTensor(problem, element,
fvGeometry, elemVolVars, fluxVarsCache);  // this gives error
const auto effSigma = StressType::effectiveStressTensor(problem,
element, fvGeometry, elemVolVars, fluxVarsCache);


//std::vector v{1,2,3};
const auto eIdx = fvGridGeometry.elementMapper().index(element);

// pass values into storage container
using FVGridGeometry = typename GridVariables::GridGeometry;
for (int dir = 0; dir < FVGridGeometry::GridView::dimension; ++dir)
{
sigmaStorage[dir][eIdx] = sigma[dir];
//sigmaStorage[dir][eIdx] = v[dir];//sigma[dir];
effSigmaStorage[dir][eIdx] = effSigma[dir];
//effSigmaStorage[dir][eIdx] = v[dir];   //effSigma[dir];
}
}
}

In main method,

//containers to store the sigma
std::array, dim> sigmaStorage;
std::array, dim> effSigmaStorage;
const auto numCells = poroMechFvGridGeometry->gridView().size(0);
std::for_each(sigmaStorage.begin(), sigmaStorage.end(),
[numCells](auto& sigma){sigma.resize(numCells);});
std::for_each(effSigmaStorage.begin(), effSigmaStorage.end(),
[numCells](auto& effSigma){effSigma.resize(numCells);});

for (int dir = 0; dir < dim; ++dir)
{
poroMechVtkWriter.addField(sigmaStorage[dir], "sigma_" +
std::to_string(dir), PoroMechVtkOutputModule::FieldType::element);
poroMechVtkWriter.addField(sigmaStorage[dir], "effSigma_" +
std::to_string(dir), PoroMechVtkOutputModule::FieldType::element);
}

using StressType = GetPropType;
assembleElementStresses(sigmaStorage, effSigmaStorage,
*poroMechProblem, *poroMechFvGridGeometry,
*poroMechGridVariables, x[poroMechId]);

Any help is appreciated.
Thank You!,

Regards,
Ranjeet
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] Dumux Digest, Vol 94, Issue 13

[Ranjeet kumar]

Hi Timo,
Thank you for the reply. Documents generated successfully.

Regards,
Ranjeet


On Tue, Dec 11, 2018 at 10:00 PM 
wrote:

> Send Dumux mailing list submissions to
> dumux@listserv.uni-stuttgart.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> or, via email, send a message with subject or body 'help' to
> dumux-requ...@listserv.uni-stuttgart.de
>
> You can reach the person managing the list at
> dumux-ow...@listserv.uni-stuttgart.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dumux digest..."
>
>
> Today's Topics:
>
>1. Re: Permission to access Dumux document (Timo Koch)
>
>
> --
>
> Message: 1
> Date: Tue, 11 Dec 2018 09:10:20 +0100
> From: Timo Koch 
> To: DuMuX User Forum 
> Subject: Re: [DuMuX] Permission to access Dumux document
> Message-ID:
> 
> Content-Type: text/plain;   charset=utf-8
>
> Hi Ranjeet,
>
> it should be just the search that is not working because of some wrong
> internal link. Thanks for reporting the issue. We are working on fixing
> this soon. In the meantime you can always locally build the doc (you need
> doxygen installed) by ?make doc? in the build folder.  The doxygen website
> should then be in build-cmake/doc/doxygen/html/index.html.
>
> Best wishes
> Timo
>
> > Am 11.12.2018 um 07:41 schrieb Ranjeet kumar :
> >
> > Hi,
> > Does access to docs restricted to outside users? Earlier it was
> accessible.
> >
> > Regards,
> > Ranjeet
> > 
> > ___
> > Dumux mailing list
> > Dumux@listserv.uni-stuttgart.de
> > https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
>
>
> --
>
> Subject: Digest Footer
>
> ___
> Dumux mailing list
> Dumux@listserv.uni-stuttgart.de
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
>
> --
>
> End of Dumux Digest, Vol 94, Issue 13
> *
>
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] Dumux Digest, Vol 93, Issue 20

[Ranjeet kumar]

Thank you for the reply, I rebuild as you suggested, Now, it's working
fine.


On Fri, Nov 30, 2018 at 2:38 AM 
wrote:

> Send Dumux mailing list submissions to
> dumux@listserv.uni-stuttgart.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> or, via email, send a message with subject or body 'help' to
> dumux-requ...@listserv.uni-stuttgart.de
>
> You can reach the person managing the list at
> dumux-ow...@listserv.uni-stuttgart.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dumux digest..."
>
>
> Today's Topics:
>
>1. Re:  error: ?UMFPackBackend? does not name a type (Timo Koch)
>
>
> --
>
> Message: 1
> Date: Thu, 29 Nov 2018 16:38:35 +0100
> From: Timo Koch 
> To: DuMuX User Forum , Ranjeet kumar
> 
> Subject: Re: [DuMuX]  error: ?UMFPackBackend? does not name a type
> Message-ID:
> 
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
> Hi Ranjeet,
>
> it looks like UMFPack wasn't found by Dune. Can you remove the
> build-directories, rerun dunecontrol and post the output in the attachment?
>
> Best wishes,
>
> Timo
>
>
> On 29.11.18 16:09, Ranjeet kumar wrote:
> > Hi, I am getting an error message "error: ?UMFPackBackend? does not
> > name a type using LinearSolver = UMFPackBackend;" when building
> > dumux/test/multidomain/poromechanics/el2p/test_el2p.
> > Could you please tell me how to resolve this? UMFPACK/SuiteSparse is
> > installed in my system.
> >
> > Thank you !
> >
> > Regards,
> > Ranjeet
> >
> > Screenshot:
> > image.png
> >
> >
> >
> > ___
> > Dumux mailing list
> > Dumux@listserv.uni-stuttgart.de
> > https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
> --
> ___
>
> Timo Koch  phone: +49 711 685 64676
> IWS, Universit?t Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: timo.k...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> ___
>
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://listserv.uni-stuttgart.de/pipermail/dumux/attachments/20181129/3e727dfd/attachment.html
> >
> -- next part --
> A non-text attachment was scrubbed...
> Name: image.png
> Type: image/png
> Size: 51454 bytes
> Desc: not available
> URL: <
> http://listserv.uni-stuttgart.de/pipermail/dumux/attachments/20181129/3e727dfd/attachment.png
> >
>
> --
>
> Subject: Digest Footer
>
> ___
> Dumux mailing list
> Dumux@listserv.uni-stuttgart.de
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>
>
> --
>
> End of Dumux Digest, Vol 93, Issue 20
> *
>
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

[DuMuX] error: ‘UMFPackBackend’ does not name a type

[Ranjeet kumar]

Hi, I am getting an error message "error: ‘UMFPackBackend’ does not name a
type using LinearSolver = UMFPackBackend;" when building
dumux/test/multidomain/poromechanics/el2p/test_el2p.
Could you please tell me how to resolve this? UMFPACK/SuiteSparse is
installed in my system.

Thank you !

Regards,
Ranjeet

Screenshot:
[image: image.png]
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

Re: [DuMuX] Dumux Digest, Vol 93, Issue 8

[Ranjeet kumar]

Dear Dennis & Kilian,
 Thank you for reply. You are right, it's better to implement  OOIP in .cc
or problem file.

Regards,
Ranjeet






On Fri, Nov 9, 2018 at 10:00 PM 
wrote:

> Send Dumux mailing list submissions to
> dumux@listserv.uni-stuttgart.de
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> or, via email, send a message with subject or body 'help' to
> dumux-requ...@listserv.uni-stuttgart.de
>
> You can reach the person managing the list at
> dumux-ow...@listserv.uni-stuttgart.de
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dumux digest..."
>
>
> Today's Topics:
>
>1. Re: Calculation of Original Oil in Place(OOIP) (Gl?ser)
>2. Re: Calculation of Original Oil in Place(OOIP) (Weishaupt, Kilian)
>
>
> --
>
> Message: 1
> Date: Thu, 8 Nov 2018 17:16:09 +
> From: Gl?ser, Dennis 
> To: "dumux@listserv.uni-stuttgart.de"
> ,  "ranjeet...@gmail.com"
> 
> Subject: Re: [DuMuX] Calculation of Original Oil in Place(OOIP)
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Ranjeet,
>
>
> you better obtain the element index using the mapper provided in the
> FvGridGeometry, i.e.:
>
>
> const auto eIdx = this->fvGridGeometry().elementMapper().index(element)
>
>
> then it also works for grids that have several geometry types. Does your
> code compile and run? It looks okay as long as your porosity field
> (porosity_) is a container of the size of number of elements with all
> values initialized properly.
>
>
> Also, this only works if your initial water saturation is 0.4 in the
> entire domain (as you hard-coded this into you constructor). I furthermore
> wonder why you do this in the spatial parameters, I would rather do it in
> the problem where you have access to the spatial parameters (and thus the
> porosity) as well as the initial saturation values. This way you can
> compute this depending on your choice for the initial saturations.
>
>
> Best wishes,
> Dennis
>
>
> 
> Von: Dumux  im Auftrag von
> Ranjeet kumar 
> Gesendet: Donnerstag, 8. November 2018 07:54:15
> An: dumux@listserv.uni-stuttgart.de
> Betreff: [DuMuX] Calculation of Original Oil in Place(OOIP)
>
> Hi all,
> I want to calculate original oil in place for 2p problem where
> OOIP = 10^4 * element.volume()*phi*(1-Sw)/Bo.
>
> I have implemented as follow in the constructor of spatialparams.hh file:
>
> Sw_ = 0.4;
> for (const auto& element : elements(gridView)) {
> auto geo = element.geometry();
> //get cell index
>  int eIdx = gridView.indexSet().index(element);
> OOIP_ += geo.volume()*porosity_[eIdx] *(1-Sw);  //assumed Bo =
> 1;
> }
> OOIP_ = OOIP_*1;
> std::cout << "OOIP =" << OOIP_ << " m^3." << std::endl;
> Is this correct?
>
>
> -- next part --
> An HTML attachment was scrubbed...
> URL: <
> http://listserv.uni-stuttgart.de/pipermail/dumux/attachments/20181108/735ba36a/attachment-0001.html
> >
>
> --
>
> Message: 2
> Date: Fri, 9 Nov 2018 07:09:49 +
> From: "Weishaupt, Kilian" 
> To: "dumux@listserv.uni-stuttgart.de"
> 
> Subject: Re: [DuMuX] Calculation of Original Oil in Place(OOIP)
> Message-ID: <95d590d668564ea99363eb0873505...@iws.uni-stuttgart.de>
> Content-Type: text/plain; charset="us-ascii"
>
> Hi Ranjeet,
>
>
> this seems to be correct to me.
>
>
> You could slightly change your loop so that it also works for a
> non-constant saturation or at any given time, assuming
> FluidSystem::phase1Idx refers to your oil phase. However, this should then
> be rather done in your main (.cc) file, where you have access to your
> gridVariables.
>
>
> for (const auto& element : elements(fvGridGeometry.gridView()))
>
> {
> auto fvGeometry = localView(fvGridGeometry);
> fvGeometry.bindElement(element);
>
> auto elemVolVars = localView(gridVariables.curGridVolVars());
> elemVolVars.bindElement(element, fvGeometry, curSol);
>
> for (auto&& scv : scvs(fvGeometry))
> {
> const auto& volVars = elemVolVars[scv];
> OOIP +=  volVars.saturatio

[DuMuX] Calculation of Original Oil in Place(OOIP)

[Ranjeet kumar]

Hi all,
I want to calculate original oil in place for 2p problem where
OOIP = 10^4 * element.volume()*phi*(1-Sw)/Bo.

I have implemented as follow in the constructor of spatialparams.hh file:

Sw_ = 0.4;
for (const auto& element : elements(gridView)) {
auto geo = element.geometry();
//get cell index
 int eIdx = gridView.indexSet().index(element);
OOIP_ += geo.volume()*porosity_[eIdx] *(1-Sw);  //assumed Bo =
1;
}
OOIP_ = OOIP_*1;
std::cout << "OOIP =" << OOIP_ << " m^3." << std::endl;
Is this correct?
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

[DuMuX] Implementation of solDependentSource() for "el2problem"

[Ranjeet kumar]

Hi, I implemented  solDependentSource() method for  "el2problem"  using
DuMuX(2.12).  When i run the model, I get an error message:

Dune::InvalidStateException
[sourceAtPos:/usr/local/include/dumux/implicit/problem.hh:443]: The problem
does not provide a sourceAtPos() method.

Do I need to implement sourceAtPos() method as I already implemented the
solDependentSource() method?

Thank You!


Regards,
Ranjeet
PhD Student
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux