Re: [DuMuX] How to get intersections from scvf and element?

2019-04-10 Thread Flemisch, Bernd
To me, it seems that using boundaryIds should rather be the exception. 
Shouldn't we then provide this custom FVGridGeometry with the boundaryIds and 
use it in the CO2 test?

Bernd



On Wed, Apr 10, 2019 at 8:13 PM +0200, "Timo Koch" 
mailto:timo.k...@iws.uni-stuttgart.de>> wrote:

You can‘t know if it‘s a dgf file. It could be in any custom group in the input 
file, or not specified in the input file at all.

Timo



Viele Grüße,
Timo
Am 10.04.2019 um 19:08 schrieb Flemisch, Bernd 
mailto:bernd.flemi...@iws.uni-stuttgart.de>>:

Would the best default be that it uses boundaryId if this is supported and a 
DGF file is present, otherwise it uses boundarySegmentIndex?

Can you open an issue?

Kind regards
Bernd



On Wed, Apr 10, 2019 at 5:52 PM +0200, "Timo Koch" 
mailto:timo.k...@iws.uni-stuttgart.de>> wrote:


Hi Samuel,

ok if they do that then there is no better solution...

The clean solution is to use a custom FVGridGeometry. The BoundaryFlag class is 
set somewhere in the sub control volume traits. You have to replace it by your 
own implementation of this class.

Have a look at the discretization folder to see how the FVGridGeometry and it‘s 
traits are defined.

Another solution would be to convert your grid file to dgf.

However, we should think about a better out-of-the-box solution.  Unfortunately 
the use of boundaryId and boundarySegmentIndex is not streamlined throughout 
the different grid managers in Dune. They have slightly different meanings.

Best wishes
Timo


> Am 09.04.2019 um 14:53 schrieb Samuel Scherrer :
>
> Hi Timo,
>
> I ran
>
> find . -wholename '*/build-cmake/*' -delete
>
> inside the directory where all my dune modules are before rerunning
> dunecontrol and removed the line as you said. Is there anything else I
> have to do? I still get the same warning.
>
> I found that dune-grid/config.h.cmake contains the line:
>
> #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
>
> Setting this to 0 removes the warning, but I assume there are better
> solutions.
>
> Best regards,
> Samuel
>
>
>> On Tue, 2019-04-09 at 12:04 +0200, Timo Koch wrote:
>> Hi Samuel,
>>
>> did you delete the build folders before you reran dunecontrol?
>>
>> Also you can just leave out the whole line  with
>> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS
>>
>> because the default should be false.
>>
>> Timo
>>
>>> On 09.04.19 11:49, Samuel Scherrer wrote:
>>> Hi Bernd,
>>>
>>> Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
>>> cmake.opts and ran
>>>
>>> dune-common/bin/dunecontrol --opts=cmake.opts all
>>>
>>> Kind regards,
>>> Samuel
>>>
>>>
>>>
 On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
 Did you leave the ":BOOL" like in
 -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
 ?

 Kind regards
 Bernd


 --
 ___

 Bernd Flemisch phone: +49 711 685 69162
 IWS, Universität Stuttgart fax:   +49 711 685 60430
 Pfaffenwaldring 61email: 
 be...@iws.uni-stuttgart.de
 D-70569 Stuttgarturl: 
 www.hydrosys.uni-stuttgart.de
 ___
 Von: Samuel Scherrer
 Gesendet: Dienstag, 9. April 2019 10:49:39
 An: Flemisch, Bernd; DuMuX User Forum
 Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
 element?

 Hi Bernd,

 I had trouble installing UGGrid, so I would prefer using ALUGrid.
 However, disabling the code for ALUGrid in boundaryflag.hh does
 the
 trick, but I'm having trouble setting
 DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I
 just

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


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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-10 Thread Timo Koch
You can‘t know if it‘s a dgf file. It could be in any custom group in the input 
file, or not specified in the input file at all. 

Timo



Viele Grüße,
Timo
> Am 10.04.2019 um 19:08 schrieb Flemisch, Bernd 
> :
> 
> Would the best default be that it uses boundaryId if this is supported and a 
> DGF file is present, otherwise it uses boundarySegmentIndex?
> 
> Can you open an issue?
> 
> Kind regards
> Bernd
> 
> 
> 
> On Wed, Apr 10, 2019 at 5:52 PM +0200, "Timo Koch" 
>  wrote:
> 
>> Hi Samuel,
>> 
>> ok if they do that then there is no better solution...
>> 
>> The clean solution is to use a custom FVGridGeometry. The BoundaryFlag class 
>> is set somewhere in the sub control volume traits. You have to replace it by 
>> your own implementation of this class. 
>> 
>> Have a look at the discretization folder to see how the FVGridGeometry and 
>> it‘s traits are defined. 
>> 
>> Another solution would be to convert your grid file to dgf.
>> 
>> However, we should think about a better out-of-the-box solution.  
>> Unfortunately the use of boundaryId and boundarySegmentIndex is not 
>> streamlined throughout the different grid managers in Dune. They have 
>> slightly different meanings. 
>> 
>> Best wishes
>> Timo
>> 
>> 
>> > Am 09.04.2019 um 14:53 schrieb Samuel Scherrer :
>> > 
>> > Hi Timo,
>> > 
>> > I ran
>> > 
>> > find . -wholename '*/build-cmake/*' -delete
>> > 
>> > inside the directory where all my dune modules are before rerunning
>> > dunecontrol and removed the line as you said. Is there anything else I
>> > have to do? I still get the same warning.
>> > 
>> > I found that dune-grid/config.h.cmake contains the line:
>> > 
>> > #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
>> > 
>> > Setting this to 0 removes the warning, but I assume there are better
>> > solutions.
>> > 
>> > Best regards,
>> > Samuel
>> > 
>> > 
>> >> On Tue, 2019-04-09 at 12:04 +0200, Timo Koch wrote:
>> >> Hi Samuel,
>> >> 
>> >> did you delete the build folders before you reran dunecontrol?
>> >> 
>> >> Also you can just leave out the whole line  with 
>> >> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS
>> >> 
>> >> because the default should be false.
>> >> 
>> >> Timo
>> >> 
>> >>> On 09.04.19 11:49, Samuel Scherrer wrote:
>> >>> Hi Bernd,
>> >>> 
>> >>> Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
>> >>> cmake.opts and ran
>> >>> 
>> >>> dune-common/bin/dunecontrol --opts=cmake.opts all
>> >>> 
>> >>> Kind regards,
>> >>> Samuel
>> >>> 
>> >>> 
>> >>> 
>>  On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
>>  Did you leave the ":BOOL" like in
>>  -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
>>  ?
>>  
>>  Kind regards
>>  Bernd
>>  
>>  
>>  --
>>  ___
>>  
>>  Bernd Flemisch phone: +49 711 685 69162
>>  IWS, Universität Stuttgart fax:   +49 711 685 60430
>>  Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
>>  D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
>>  ___
>>  Von: Samuel Scherrer 
>>  Gesendet: Dienstag, 9. April 2019 10:49:39
>>  An: Flemisch, Bernd; DuMuX User Forum
>>  Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
>>  element?
>>  
>>  Hi Bernd,
>>  
>>  I had trouble installing UGGrid, so I would prefer using ALUGrid.
>>  However, disabling the code for ALUGrid in boundaryflag.hh does
>>  the
>>  trick, but I'm having trouble setting
>>  DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I
>>  just
>> 
>> ___
>> Dumux mailing list
>> Dumux@listserv.uni-stuttgart.de
>> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> ___
> Dumux mailing list
> Dumux@listserv.uni-stuttgart.de
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
___
Dumux mailing list
Dumux@listserv.uni-stuttgart.de
https://listserv.uni-stuttgart.de/mailman/listinfo/dumux


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-10 Thread Flemisch, Bernd
Would the best default be that it uses boundaryId if this is supported and a 
DGF file is present, otherwise it uses boundarySegmentIndex?

Can you open an issue?

Kind regards
Bernd



On Wed, Apr 10, 2019 at 5:52 PM +0200, "Timo Koch" 
mailto:timo.k...@iws.uni-stuttgart.de>> wrote:


Hi Samuel,

ok if they do that then there is no better solution...

The clean solution is to use a custom FVGridGeometry. The BoundaryFlag class is 
set somewhere in the sub control volume traits. You have to replace it by your 
own implementation of this class.

Have a look at the discretization folder to see how the FVGridGeometry and it‘s 
traits are defined.

Another solution would be to convert your grid file to dgf.

However, we should think about a better out-of-the-box solution.  Unfortunately 
the use of boundaryId and boundarySegmentIndex is not streamlined throughout 
the different grid managers in Dune. They have slightly different meanings.

Best wishes
Timo


> Am 09.04.2019 um 14:53 schrieb Samuel Scherrer :
>
> Hi Timo,
>
> I ran
>
> find . -wholename '*/build-cmake/*' -delete
>
> inside the directory where all my dune modules are before rerunning
> dunecontrol and removed the line as you said. Is there anything else I
> have to do? I still get the same warning.
>
> I found that dune-grid/config.h.cmake contains the line:
>
> #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
>
> Setting this to 0 removes the warning, but I assume there are better
> solutions.
>
> Best regards,
> Samuel
>
>
>> On Tue, 2019-04-09 at 12:04 +0200, Timo Koch wrote:
>> Hi Samuel,
>>
>> did you delete the build folders before you reran dunecontrol?
>>
>> Also you can just leave out the whole line  with
>> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS
>>
>> because the default should be false.
>>
>> Timo
>>
>>> On 09.04.19 11:49, Samuel Scherrer wrote:
>>> Hi Bernd,
>>>
>>> Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
>>> cmake.opts and ran
>>>
>>> dune-common/bin/dunecontrol --opts=cmake.opts all
>>>
>>> Kind regards,
>>> Samuel
>>>
>>>
>>>
 On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
 Did you leave the ":BOOL" like in
 -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
 ?

 Kind regards
 Bernd


 --
 ___

 Bernd Flemisch phone: +49 711 685 69162
 IWS, Universität Stuttgart fax:   +49 711 685 60430
 Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
 D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
 ___
 Von: Samuel Scherrer
 Gesendet: Dienstag, 9. April 2019 10:49:39
 An: Flemisch, Bernd; DuMuX User Forum
 Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
 element?

 Hi Bernd,

 I had trouble installing UGGrid, so I would prefer using ALUGrid.
 However, disabling the code for ALUGrid in boundaryflag.hh does
 the
 trick, but I'm having trouble setting
 DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I
 just

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

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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-10 Thread Timo Koch
Hi Samuel,

ok if they do that then there is no better solution...

The clean solution is to use a custom FVGridGeometry. The BoundaryFlag class is 
set somewhere in the sub control volume traits. You have to replace it by your 
own implementation of this class. 

Have a look at the discretization folder to see how the FVGridGeometry and it‘s 
traits are defined. 

Another solution would be to convert your grid file to dgf.

However, we should think about a better out-of-the-box solution.  Unfortunately 
the use of boundaryId and boundarySegmentIndex is not streamlined throughout 
the different grid managers in Dune. They have slightly different meanings. 

Best wishes
Timo


> Am 09.04.2019 um 14:53 schrieb Samuel Scherrer :
> 
> Hi Timo,
> 
> I ran
> 
> find . -wholename '*/build-cmake/*' -delete
> 
> inside the directory where all my dune modules are before rerunning
> dunecontrol and removed the line as you said. Is there anything else I
> have to do? I still get the same warning.
> 
> I found that dune-grid/config.h.cmake contains the line:
> 
> #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
> 
> Setting this to 0 removes the warning, but I assume there are better
> solutions.
> 
> Best regards,
> Samuel
> 
> 
>> On Tue, 2019-04-09 at 12:04 +0200, Timo Koch wrote:
>> Hi Samuel,
>> 
>> did you delete the build folders before you reran dunecontrol?
>> 
>> Also you can just leave out the whole line  with 
>> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS
>> 
>> because the default should be false.
>> 
>> Timo
>> 
>>> On 09.04.19 11:49, Samuel Scherrer wrote:
>>> Hi Bernd,
>>> 
>>> Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
>>> cmake.opts and ran
>>> 
>>> dune-common/bin/dunecontrol --opts=cmake.opts all
>>> 
>>> Kind regards,
>>> Samuel
>>> 
>>> 
>>> 
 On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
 Did you leave the ":BOOL" like in
 -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
 ?
 
 Kind regards
 Bernd
 
 
 --
 ___
 
 Bernd Flemisch phone: +49 711 685 69162
 IWS, Universität Stuttgart fax:   +49 711 685 60430
 Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
 D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
 ___
 Von: Samuel Scherrer 
 Gesendet: Dienstag, 9. April 2019 10:49:39
 An: Flemisch, Bernd; DuMuX User Forum
 Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
 element?
 
 Hi Bernd,
 
 I had trouble installing UGGrid, so I would prefer using ALUGrid.
 However, disabling the code for ALUGrid in boundaryflag.hh does
 the
 trick, but I'm having trouble setting
 DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I
 just

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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Samuel Scherrer
Hi Timo,

I ran

find . -wholename '*/build-cmake/*' -delete

inside the directory where all my dune modules are before rerunning
dunecontrol and removed the line as you said. Is there anything else I
have to do? I still get the same warning.

I found that dune-grid/config.h.cmake contains the line:

#define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1

Setting this to 0 removes the warning, but I assume there are better
solutions.

Best regards,
Samuel


On Tue, 2019-04-09 at 12:04 +0200, Timo Koch wrote:
> Hi Samuel,
> 
> did you delete the build folders before you reran dunecontrol?
> 
> Also you can just leave out the whole line  with 
> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS
> 
> because the default should be false.
> 
> Timo
> 
> On 09.04.19 11:49, Samuel Scherrer wrote:
> > Hi Bernd,
> > 
> > Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
> > cmake.opts and ran
> > 
> > dune-common/bin/dunecontrol --opts=cmake.opts all
> > 
> > Kind regards,
> > Samuel
> > 
> > 
> > 
> > On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
> > > Did you leave the ":BOOL" like in
> > > -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
> > > ?
> > > 
> > > Kind regards
> > > Bernd
> > > 
> > > 
> > > --
> > > ___
> > > 
> > > Bernd Flemisch phone: +49 711 685 69162
> > > IWS, Universität Stuttgart fax:   +49 711 685 60430
> > > Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> > > D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> > > ___
> > > Von: Samuel Scherrer 
> > > Gesendet: Dienstag, 9. April 2019 10:49:39
> > > An: Flemisch, Bernd; DuMuX User Forum
> > > Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
> > > element?
> > >   
> > > Hi Bernd,
> > > 
> > > I had trouble installing UGGrid, so I would prefer using ALUGrid.
> > > However, disabling the code for ALUGrid in boundaryflag.hh does
> > > the
> > > trick, but I'm having trouble setting
> > > DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I
> > > just
> > > added '&& 0' in dumux/common/boundaryflag.hh.
> > > 
> > > When I add COMPILE_DEFINITIONS
> > > DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
> > > in the dune_add_test section of my CMakeLists.txt I get the
> > > following
> > > warning:
> > > 
> > > /home/samuel/dumux/dumux-vegas-geothermal/build-
> > > cmake/config.h:269:0:
> > > warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
> > >   #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
> > > 
> > > Best regards,
> > > Samuel
> > > 
> > > 
> > > On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:
> > > > Actually, it might work also for ALUGrid
> > > > if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_
> > > > because
> > > > that triggers the default behavior of boundaryFlag().
> > > > 
> > > > Bernd
> > > > 
> > > > 
> > > > --
> > > > ___
> > > > 
> > > > Bernd Flemisch phone: +49 711 685 69162
> > > > IWS, Universität Stuttgart fax:   +49 711 685 60430
> > > > Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> > > > D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> > > > ___
> > > > Von: Dumux  im Auftrag
> > > > von
> > > > Flemisch, Bernd 
> > > > Gesendet: Montag, 8. April 2019 23:55:11
> > > > An: DuMuX User Forum; Samuel Scherrer
> > > > Betreff: Re: [DuMuX] How to get intersections from scvf and
> > > 
> > > element?
> > > >   
> > > > Martin is right about the boundaryId. I guess that means it
> > > > doesn't
> > > > work with ALUGrid like this at the moment. For other grids,
> > > > scvf.boundaryFlag()
> > > > should return the boundarySegmentIndex, so
> > > > gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
> > > > should return the right thing.

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Timo Koch

Hi Samuel,

did you delete the build folders before you reran dunecontrol?

Also you can just leave out the whole line  with 
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS


because the default should be false.

Timo

On 09.04.19 11:49, Samuel Scherrer wrote:

Hi Bernd,

Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
cmake.opts and ran

dune-common/bin/dunecontrol --opts=cmake.opts all

Kind regards,
Samuel



On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:

Did you leave the ":BOOL" like in
-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
?

Kind regards
Bernd


--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Samuel Scherrer 
Gesendet: Dienstag, 9. April 2019 10:49:39
An: Flemisch, Bernd; DuMuX User Forum
Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
element?
  
Hi Bernd,


I had trouble installing UGGrid, so I would prefer using ALUGrid.
However, disabling the code for ALUGrid in boundaryflag.hh does the
trick, but I'm having trouble setting
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I just
added '&& 0' in dumux/common/boundaryflag.hh.

When I add COMPILE_DEFINITIONS
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
in the dune_add_test section of my CMakeLists.txt I get the following
warning:

/home/samuel/dumux/dumux-vegas-geothermal/build-cmake/config.h:269:0:
warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
  #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1

Best regards,
Samuel


On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:

Actually, it might work also for ALUGrid
if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because
that triggers the default behavior of boundaryFlag().

Bernd


--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag von
Flemisch, Bernd 
Gesendet: Montag, 8. April 2019 23:55:11
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and

element?
  
Martin is right about the boundaryId. I guess that means it doesn't

work with ALUGrid like this at the moment. For other grids,
scvf.boundaryFlag()
should return the boundarySegmentIndex, so
gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
should return the right thing. Are you bound to ALUGrid or can you
try with UGGrid?

Apart from that, we should see how to make things consistent.

Kind regards
Bernd

--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag von
Martin Schneider 
Gesendet: Montag, 8. April 2019 22:41:51
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and

element?
  
Hi Samuel,


maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
of AluGrid which is only properly defined if you are using a DGF

grid

file.
The CO2 test uses such a DGF file, which is why it works there.

Maybe having a look at the tests in test/io/gridmanager helps.

Best regards,
Martin


On 08.04.19 19:34, Samuel Scherrer wrote:

Hi Timo, Hi Bernd,

thanks a lot for your help.
I'm compiling the dune modules with the cmake.opts in the dumux
repository, which contains "-
DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in

"CMAKE_FLAGS", so

I assume that I don't need any additional changes.

The problem file in co2/implicit looks like what I need. However,

when

using scvf.boundaryFlag() I always get the same value, 1, but

when

I

instead loop over all interfaces of the current element and use

the

'getBoundaryDomainMarker'-function I do get the values I expect.

I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you

know

what might be going wrong here?

Best regards,
Samuel



On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:

Hi Samuel,

as an addition to Bernd's answer, you might have to set
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
for compiling dune-grid and the grid modules. I'm not sure if

this

is

still required.

Best wish

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Samuel Scherrer
Hi Bernd,

Yes, I set "-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE" in
cmake.opts and ran

dune-common/bin/dunecontrol --opts=cmake.opts all

Kind regards,
Samuel



On Tue, 2019-04-09 at 09:32 +, Flemisch, Bernd wrote:
> Did you leave the ":BOOL" like in
> -DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE
> ?
> 
> Kind regards
> Bernd
> 
> 
> --
> ___
> 
> Bernd Flemisch phone: +49 711 685 69162
> IWS, Universität Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> ___
> Von: Samuel Scherrer 
> Gesendet: Dienstag, 9. April 2019 10:49:39
> An: Flemisch, Bernd; DuMuX User Forum
> Betreff: Re: AW: [DuMuX] How to get intersections from scvf and
> element?
>  
> Hi Bernd,
> 
> I had trouble installing UGGrid, so I would prefer using ALUGrid.
> However, disabling the code for ALUGrid in boundaryflag.hh does the
> trick, but I'm having trouble setting
> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I just
> added '&& 0' in dumux/common/boundaryflag.hh.
> 
> When I add COMPILE_DEFINITIONS
> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
> in the dune_add_test section of my CMakeLists.txt I get the following
> warning:
> 
> /home/samuel/dumux/dumux-vegas-geothermal/build-cmake/config.h:269:0:
> warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
>  #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1
> 
> Best regards,
> Samuel
> 
> 
> On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:
> > Actually, it might work also for ALUGrid
> > if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because
> > that triggers the default behavior of boundaryFlag().
> > 
> > Bernd
> > 
> > 
> > --
> > ___
> > 
> > Bernd Flemisch phone: +49 711 685 69162
> > IWS, Universität Stuttgart fax:   +49 711 685 60430
> > Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> > D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> > ___________
> > Von: Dumux  im Auftrag von
> > Flemisch, Bernd 
> > Gesendet: Montag, 8. April 2019 23:55:11
> > An: DuMuX User Forum; Samuel Scherrer
> > Betreff: Re: [DuMuX] How to get intersections from scvf and
> element?
> >  
> > Martin is right about the boundaryId. I guess that means it doesn't
> > work with ALUGrid like this at the moment. For other grids,
> > scvf.boundaryFlag()
> > should return the boundarySegmentIndex, so
> > gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
> > should return the right thing. Are you bound to ALUGrid or can you
> > try with UGGrid?
> > 
> > Apart from that, we should see how to make things consistent.
> > 
> > Kind regards
> > Bernd
> > 
> > --
> > ___
> > 
> > Bernd Flemisch phone: +49 711 685 69162
> > IWS, Universität Stuttgart     fax:   +49 711 685 60430
> > Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> > D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> > ___
> > Von: Dumux  im Auftrag von
> > Martin Schneider 
> > Gesendet: Montag, 8. April 2019 22:41:51
> > An: DuMuX User Forum; Samuel Scherrer
> > Betreff: Re: [DuMuX] How to get intersections from scvf and
> element?
> >  
> > Hi Samuel,
> > 
> > maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
> > of AluGrid which is only properly defined if you are using a DGF
> grid
> > file.
> > The CO2 test uses such a DGF file, which is why it works there.
> > 
> > Maybe having a look at the tests in test/io/gridmanager helps.
> > 
> > Best regards,
> > Martin
> > 
> > 
> > On 08.04.19 19:34, Samuel Scherrer wrote:
> > > Hi Timo, Hi Bernd,
> > >
> > > thanks a lot for your help.
> > > I'm compiling the dune modules with the cmake.opts in the dumux
> > > repository, which contains "-
> > > DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in
> > "CMAKE_FLAGS", so
> > > I assume that I don't need 

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Flemisch, Bernd
Did you leave the ":BOOL" like in

-DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=FALSE

?


Kind regards

Bernd



--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___

Von: Samuel Scherrer 
Gesendet: Dienstag, 9. April 2019 10:49:39
An: Flemisch, Bernd; DuMuX User Forum
Betreff: Re: AW: [DuMuX] How to get intersections from scvf and element?

Hi Bernd,

I had trouble installing UGGrid, so I would prefer using ALUGrid.
However, disabling the code for ALUGrid in boundaryflag.hh does the
trick, but I'm having trouble setting
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I just
added '&& 0' in dumux/common/boundaryflag.hh.

When I add COMPILE_DEFINITIONS DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
in the dune_add_test section of my CMakeLists.txt I get the following
warning:

/home/samuel/dumux/dumux-vegas-geothermal/build-cmake/config.h:269:0:
warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
 #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1

Best regards,
Samuel


On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:
> Actually, it might work also for ALUGrid
> if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because
> that triggers the default behavior of boundaryFlag().
>
> Bernd
>
>
> --
> ___
>
> Bernd Flemisch phone: +49 711 685 69162
> IWS, Universität Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: 
> www.hydrosys.uni-stuttgart.de<http://www.hydrosys.uni-stuttgart.de>
> ___
> Von: Dumux  im Auftrag von
> Flemisch, Bernd 
> Gesendet: Montag, 8. April 2019 23:55:11
> An: DuMuX User Forum; Samuel Scherrer
> Betreff: Re: [DuMuX] How to get intersections from scvf and element?
>
> Martin is right about the boundaryId. I guess that means it doesn't
> work with ALUGrid like this at the moment. For other grids,
> scvf.boundaryFlag()
> should return the boundarySegmentIndex, so
> gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
> should return the right thing. Are you bound to ALUGrid or can you
> try with UGGrid?
>
> Apart from that, we should see how to make things consistent.
>
> Kind regards
> Bernd
>
> --
> ___
>
> Bernd Flemisch phone: +49 711 685 69162
> IWS, Universität Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: 
> www.hydrosys.uni-stuttgart.de<http://www.hydrosys.uni-stuttgart.de>
> _______________
> Von: Dumux  im Auftrag von
> Martin Schneider 
> Gesendet: Montag, 8. April 2019 22:41:51
> An: DuMuX User Forum; Samuel Scherrer
> Betreff: Re: [DuMuX] How to get intersections from scvf and element?
>
> Hi Samuel,
>
> maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
> of AluGrid which is only properly defined if you are using a DGF grid
> file.
> The CO2 test uses such a DGF file, which is why it works there.
>
> Maybe having a look at the tests in test/io/gridmanager helps.
>
> Best regards,
> Martin
>
>
> On 08.04.19 19:34, Samuel Scherrer wrote:
> > Hi Timo, Hi Bernd,
> >
> > thanks a lot for your help.
> > I'm compiling the dune modules with the cmake.opts in the dumux
> > repository, which contains "-
> > DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in
> "CMAKE_FLAGS", so
> > I assume that I don't need any additional changes.
> >
> > The problem file in co2/implicit looks like what I need. However,
> when
> > using scvf.boundaryFlag() I always get the same value, 1, but when
> I
> > instead loop over all interfaces of the current element and use the
> > 'getBoundaryDomainMarker'-function I do get the values I expect.
> >
> > I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
> > what might be going wrong here?
> >
> > Best regards,
> > Samuel
> >
> >
> >
> > On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:
> >> Hi Samuel,
> >>
> >> as an addition to Bernd's

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Timo Koch

Hi Samuel,

you can't just redefine the macro because it's already defined somewhere 
in Dune, that's what the error means.


You need to reconfigure the dune libraries with the the new setting in 
the opts file.


Timo


On 09.04.19 10:49, Samuel Scherrer wrote:

Hi Bernd,

I had trouble installing UGGrid, so I would prefer using ALUGrid.
However, disabling the code for ALUGrid in boundaryflag.hh does the
trick, but I'm having trouble setting
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I just
added '&& 0' in dumux/common/boundaryflag.hh.

When I add COMPILE_DEFINITIONS DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
in the dune_add_test section of my CMakeLists.txt I get the following
warning:

/home/samuel/dumux/dumux-vegas-geothermal/build-cmake/config.h:269:0:
warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
  #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1

Best regards,
Samuel


On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:

Actually, it might work also for ALUGrid
if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because
that triggers the default behavior of boundaryFlag().

Bernd


--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag von
Flemisch, Bernd 
Gesendet: Montag, 8. April 2019 23:55:11
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and element?
  
Martin is right about the boundaryId. I guess that means it doesn't

work with ALUGrid like this at the moment. For other grids,
scvf.boundaryFlag()
should return the boundarySegmentIndex, so
gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
should return the right thing. Are you bound to ALUGrid or can you
try with UGGrid?

Apart from that, we should see how to make things consistent.

Kind regards
Bernd

--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag von
Martin Schneider 
Gesendet: Montag, 8. April 2019 22:41:51
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and element?
  
Hi Samuel,


maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
of AluGrid which is only properly defined if you are using a DGF grid
file.
The CO2 test uses such a DGF file, which is why it works there.

Maybe having a look at the tests in test/io/gridmanager helps.

Best regards,
Martin


On 08.04.19 19:34, Samuel Scherrer wrote:

Hi Timo, Hi Bernd,

thanks a lot for your help.
I'm compiling the dune modules with the cmake.opts in the dumux
repository, which contains "-
DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in

"CMAKE_FLAGS", so

I assume that I don't need any additional changes.

The problem file in co2/implicit looks like what I need. However,

when

using scvf.boundaryFlag() I always get the same value, 1, but when

I

instead loop over all interfaces of the current element and use the
'getBoundaryDomainMarker'-function I do get the values I expect.

I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
what might be going wrong here?

Best regards,
Samuel



On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:

Hi Samuel,

as an addition to Bernd's answer, you might have to set
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
for compiling dune-grid and the grid modules. I'm not sure if this

is

still required.

Best wishes
Timo

On 08.04.19 17:37, Flemisch, Bernd wrote:

Hi Samuel,

I think that it is given by scvf.boundaryFlag(). Have a look at


https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh

Kind regards
Bernd



--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag

von

Samuel Scherrer 
Gesendet: Montag, 8. April 2019 17:30:26
An: dumux@listserv.uni-stuttgart.de
Betreff: [DuMuX] How to get intersections from scvf and element?
   
Hi Dumux people,


I'm currently trying to use a grid generated with gmsh a

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-09 Thread Samuel Scherrer
Hi Bernd,

I had trouble installing UGGrid, so I would prefer using ALUGrid.
However, disabling the code for ALUGrid in boundaryflag.hh does the
trick, but I'm having trouble setting
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS to false. At the moment I just
added '&& 0' in dumux/common/boundaryflag.hh.

When I add COMPILE_DEFINITIONS DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS=0
in the dune_add_test section of my CMakeLists.txt I get the following
warning:

/home/samuel/dumux/dumux-vegas-geothermal/build-cmake/config.h:269:0:
warning: "DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS" redefined
 #define DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS 1

Best regards,
Samuel


On Tue, 2019-04-09 at 05:47 +, Flemisch, Bernd wrote:
> Actually, it might work also for ALUGrid
> if DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because
> that triggers the default behavior of boundaryFlag().
> 
> Bernd
> 
> 
> --
> ___
> 
> Bernd Flemisch phone: +49 711 685 69162
> IWS, Universität Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> ___
> Von: Dumux  im Auftrag von
> Flemisch, Bernd 
> Gesendet: Montag, 8. April 2019 23:55:11
> An: DuMuX User Forum; Samuel Scherrer
> Betreff: Re: [DuMuX] How to get intersections from scvf and element?
>  
> Martin is right about the boundaryId. I guess that means it doesn't
> work with ALUGrid like this at the moment. For other grids,
> scvf.boundaryFlag()
> should return the boundarySegmentIndex, so
> gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
> should return the right thing. Are you bound to ALUGrid or can you
> try with UGGrid?
> 
> Apart from that, we should see how to make things consistent.
> 
> Kind regards
> Bernd
> 
> --
> ___
> 
> Bernd Flemisch phone: +49 711 685 69162
> IWS, Universität Stuttgart fax:   +49 711 685 60430
> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> ___
> Von: Dumux  im Auftrag von
> Martin Schneider 
> Gesendet: Montag, 8. April 2019 22:41:51
> An: DuMuX User Forum; Samuel Scherrer
> Betreff: Re: [DuMuX] How to get intersections from scvf and element?
>  
> Hi Samuel,
> 
> maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
> of AluGrid which is only properly defined if you are using a DGF grid
> file.
> The CO2 test uses such a DGF file, which is why it works there.
> 
> Maybe having a look at the tests in test/io/gridmanager helps.
> 
> Best regards,
> Martin
> 
> 
> On 08.04.19 19:34, Samuel Scherrer wrote:
> > Hi Timo, Hi Bernd,
> >
> > thanks a lot for your help.
> > I'm compiling the dune modules with the cmake.opts in the dumux
> > repository, which contains "-
> > DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in
> "CMAKE_FLAGS", so
> > I assume that I don't need any additional changes.
> >
> > The problem file in co2/implicit looks like what I need. However,
> when
> > using scvf.boundaryFlag() I always get the same value, 1, but when
> I
> > instead loop over all interfaces of the current element and use the
> > 'getBoundaryDomainMarker'-function I do get the values I expect.
> >
> > I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
> > what might be going wrong here?
> >
> > Best regards,
> > Samuel
> >
> >
> >
> > On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:
> >> Hi Samuel,
> >>
> >> as an addition to Bernd's answer, you might have to set
> >> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
> >> for compiling dune-grid and the grid modules. I'm not sure if this
> is
> >> still required.
> >>
> >> Best wishes
> >> Timo
> >>
> >> On 08.04.19 17:37, Flemisch, Bernd wrote:
> >>> Hi Samuel,
> >>>
> >>> I think that it is given by scvf.boundaryFlag(). Have a look at
> >>>
> > 
> https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh
> >>> Kind regards
> >>> Bernd
> >>>
> >>>
> >>>
> >>> --
> >>> _

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Flemisch, Bernd
Actually, it might work also for ALUGrid if 
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS is set to _false_ because that triggers 
the default behavior of boundaryFlag().


Bernd



--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___

Von: Dumux  im Auftrag von Flemisch, 
Bernd 
Gesendet: Montag, 8. April 2019 23:55:11
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and element?


Martin is right about the boundaryId. I guess that means it doesn't work with 
ALUGrid like this at the moment. For other grids,
scvf.boundaryFlag()
should return the boundarySegmentIndex, so
gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
should return the right thing. Are you bound to ALUGrid or can you try with 
UGGrid?

Apart from that, we should see how to make things consistent.

Kind regards
Bernd


--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___

Von: Dumux  im Auftrag von Martin 
Schneider 
Gesendet: Montag, 8. April 2019 22:41:51
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and element?

Hi Samuel,

maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
of AluGrid which is only properly defined if you are using a DGF grid file.
The CO2 test uses such a DGF file, which is why it works there.

Maybe having a look at the tests in test/io/gridmanager helps.

Best regards,
Martin


On 08.04.19 19:34, Samuel Scherrer wrote:
> Hi Timo, Hi Bernd,
>
> thanks a lot for your help.
> I'm compiling the dune modules with the cmake.opts in the dumux
> repository, which contains "-
> DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in "CMAKE_FLAGS", so
> I assume that I don't need any additional changes.
>
> The problem file in co2/implicit looks like what I need. However, when
> using scvf.boundaryFlag() I always get the same value, 1, but when I
> instead loop over all interfaces of the current element and use the
> 'getBoundaryDomainMarker'-function I do get the values I expect.
>
> I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
> what might be going wrong here?
>
> Best regards,
> Samuel
>
>
>
> On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:
>> Hi Samuel,
>>
>> as an addition to Bernd's answer, you might have to set
>> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
>> for compiling dune-grid and the grid modules. I'm not sure if this is
>> still required.
>>
>> Best wishes
>> Timo
>>
>> On 08.04.19 17:37, Flemisch, Bernd wrote:
>>> Hi Samuel,
>>>
>>> I think that it is given by scvf.boundaryFlag(). Have a look at
>>>
> https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh
>>> Kind regards
>>> Bernd
>>>
>>>
>>>
>>> --
>>> ___
>>>
>>> Bernd Flemisch phone: +49 711 685 69162
>>> IWS, Universität Stuttgart fax:   +49 711 685 60430
>>> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
>>> D-70569 Stuttgarturl: 
>>> www.hydrosys.uni-stuttgart.de<http://www.hydrosys.uni-stuttgart.de>
>>> ___
>>> Von: Dumux  im Auftrag von
>>> Samuel Scherrer 
>>> Gesendet: Montag, 8. April 2019 17:30:26
>>> An: dumux@listserv.uni-stuttgart.de
>>> Betreff: [DuMuX] How to get intersections from scvf and element?
>>>
>>> Hi Dumux people,
>>>
>>> I'm currently trying to use a grid generated with gmsh and would
>>> like
>>> to set the boundaries based on BoundaryDomainMarkers.
>>> I found that it's possible to access the boundary domain markers
>>> via
>>> the function 'getBoundaryDomainMarkers', which accepts either a
>>> Intersection or a boundary segment index as argument.
>>>
>>&g

Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Flemisch, Bernd
Martin is right about the boundaryId. I guess that means it doesn't work with 
ALUGrid like this at the moment. For other grids,
scvf.boundaryFlag()
should return the boundarySegmentIndex, so
gridData->getBoundaryDomainMarker(scvf.boundaryFlag())
should return the right thing. Are you bound to ALUGrid or can you try with 
UGGrid?

Apart from that, we should see how to make things consistent.

Kind regards
Bernd


--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___

Von: Dumux  im Auftrag von Martin 
Schneider 
Gesendet: Montag, 8. April 2019 22:41:51
An: DuMuX User Forum; Samuel Scherrer
Betreff: Re: [DuMuX] How to get intersections from scvf and element?

Hi Samuel,

maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
of AluGrid which is only properly defined if you are using a DGF grid file.
The CO2 test uses such a DGF file, which is why it works there.

Maybe having a look at the tests in test/io/gridmanager helps.

Best regards,
Martin


On 08.04.19 19:34, Samuel Scherrer wrote:
> Hi Timo, Hi Bernd,
>
> thanks a lot for your help.
> I'm compiling the dune modules with the cmake.opts in the dumux
> repository, which contains "-
> DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in "CMAKE_FLAGS", so
> I assume that I don't need any additional changes.
>
> The problem file in co2/implicit looks like what I need. However, when
> using scvf.boundaryFlag() I always get the same value, 1, but when I
> instead loop over all interfaces of the current element and use the
> 'getBoundaryDomainMarker'-function I do get the values I expect.
>
> I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
> what might be going wrong here?
>
> Best regards,
> Samuel
>
>
>
> On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:
>> Hi Samuel,
>>
>> as an addition to Bernd's answer, you might have to set
>> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
>> for compiling dune-grid and the grid modules. I'm not sure if this is
>> still required.
>>
>> Best wishes
>> Timo
>>
>> On 08.04.19 17:37, Flemisch, Bernd wrote:
>>> Hi Samuel,
>>>
>>> I think that it is given by scvf.boundaryFlag(). Have a look at
>>>
> https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh
>>> Kind regards
>>> Bernd
>>>
>>>
>>>
>>> --
>>> ___
>>>
>>> Bernd Flemisch phone: +49 711 685 69162
>>> IWS, Universität Stuttgart fax:   +49 711 685 60430
>>> Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
>>> D-70569 Stuttgarturl: 
>>> www.hydrosys.uni-stuttgart.de<http://www.hydrosys.uni-stuttgart.de>
>>> ___
>>> Von: Dumux  im Auftrag von
>>> Samuel Scherrer 
>>> Gesendet: Montag, 8. April 2019 17:30:26
>>> An: dumux@listserv.uni-stuttgart.de
>>> Betreff: [DuMuX] How to get intersections from scvf and element?
>>>
>>> Hi Dumux people,
>>>
>>> I'm currently trying to use a grid generated with gmsh and would
>>> like
>>> to set the boundaries based on BoundaryDomainMarkers.
>>> I found that it's possible to access the boundary domain markers
>>> via
>>> the function 'getBoundaryDomainMarkers', which accepts either a
>>> Intersection or a boundary segment index as argument.
>>>
>>> How do I now get the intersection/boundary segment index when I
>>> have a
>>> given element and scvf, e.g. inside the 'neumann' function
>>> (solution
>>> dependent neumann boundary)?
>>>
>>> Best regards,
>>> Samuel
>>>
>>> ___
>>> Dumux mailing list
>>> Dumux@listserv.uni-stuttgart.de
>>> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>>>
>>>
>>> ___
>>> Dumux mailing list
>>> Dumux@listserv.uni-stuttgart.de
>>> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
>> ___
>> Dumux mailing list
>> Dumux@listserv.uni-stuttgart.de
>> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> ___
> Dumux mailing list
> Dumux@listserv.uni-stuttgart.de
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Martin Schneider

Hi Samuel,

maybe I am wrong but the scvf.boundaryFlag() returns the boundaryId
of AluGrid which is only properly defined if you are using a DGF grid file.
The CO2 test uses such a DGF file, which is why it works there.

Maybe having a look at the tests in test/io/gridmanager helps.

Best regards,
Martin


On 08.04.19 19:34, Samuel Scherrer wrote:

Hi Timo, Hi Bernd,

thanks a lot for your help.
I'm compiling the dune modules with the cmake.opts in the dumux
repository, which contains "-
DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in "CMAKE_FLAGS", so
I assume that I don't need any additional changes.

The problem file in co2/implicit looks like what I need. However, when
using scvf.boundaryFlag() I always get the same value, 1, but when I
instead loop over all interfaces of the current element and use the
'getBoundaryDomainMarker'-function I do get the values I expect.

I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
what might be going wrong here?

Best regards,
Samuel



On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:

Hi Samuel,

as an addition to Bernd's answer, you might have to set
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
for compiling dune-grid and the grid modules. I'm not sure if this is
still required.

Best wishes
Timo

On 08.04.19 17:37, Flemisch, Bernd wrote:

Hi Samuel,

I think that it is given by scvf.boundaryFlag(). Have a look at


https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh

Kind regards
Bernd



--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___
Von: Dumux  im Auftrag von
Samuel Scherrer 
Gesendet: Montag, 8. April 2019 17:30:26
An: dumux@listserv.uni-stuttgart.de
Betreff: [DuMuX] How to get intersections from scvf and element?
  
Hi Dumux people,


I'm currently trying to use a grid generated with gmsh and would
like
to set the boundaries based on BoundaryDomainMarkers.
I found that it's possible to access the boundary domain markers
via
the function 'getBoundaryDomainMarkers', which accepts either a
Intersection or a boundary segment index as argument.

How do I now get the intersection/boundary segment index when I
have a
given element and scvf, e.g. inside the 'neumann' function
(solution
dependent neumann boundary)?

Best regards,
Samuel

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


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

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

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


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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Samuel Scherrer
Hi Timo, Hi Bernd,

thanks a lot for your help.
I'm compiling the dune modules with the cmake.opts in the dumux
repository, which contains "-
DDUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=True" in "CMAKE_FLAGS", so
I assume that I don't need any additional changes.

The problem file in co2/implicit looks like what I need. However, when
using scvf.boundaryFlag() I always get the same value, 1, but when I
instead loop over all interfaces of the current element and use the
'getBoundaryDomainMarker'-function I do get the values I expect.

I'm using the gmsh mesh-format version 2.2 and ALUGrid. Do you know
what might be going wrong here?

Best regards,
Samuel



On Mon, 2019-04-08 at 18:09 +0200, Timo Koch wrote:
> Hi Samuel,
> 
> as an addition to Bernd's answer, you might have to set
> DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE
> for compiling dune-grid and the grid modules. I'm not sure if this is
> still required.
> 
> Best wishes
> Timo
> 
> On 08.04.19 17:37, Flemisch, Bernd wrote:
> > Hi Samuel,
> > 
> > I think that it is given by scvf.boundaryFlag(). Have a look at
> > 
https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh
> > 
> > Kind regards
> > Bernd
> > 
> > 
> > 
> > --
> > ___
> > 
> > Bernd Flemisch phone: +49 711 685 69162
> > IWS, Universität Stuttgart fax:   +49 711 685 60430
> > Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
> > D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
> > ___
> > Von: Dumux  im Auftrag von
> > Samuel Scherrer 
> > Gesendet: Montag, 8. April 2019 17:30:26
> > An: dumux@listserv.uni-stuttgart.de
> > Betreff: [DuMuX] How to get intersections from scvf and element?
> >  
> > Hi Dumux people,
> > 
> > I'm currently trying to use a grid generated with gmsh and would
> > like
> > to set the boundaries based on BoundaryDomainMarkers.
> > I found that it's possible to access the boundary domain markers
> > via
> > the function 'getBoundaryDomainMarkers', which accepts either a
> > Intersection or a boundary segment index as argument.
> > 
> > How do I now get the intersection/boundary segment index when I
> > have a
> > given element and scvf, e.g. inside the 'neumann' function
> > (solution
> > dependent neumann boundary)?
> > 
> > Best regards,
> > Samuel
> > 
> > ___
> > Dumux mailing list
> > Dumux@listserv.uni-stuttgart.de
> > https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> > 
> > 
> > ___
> > Dumux mailing list
> > Dumux@listserv.uni-stuttgart.de
> > https://listserv.uni-stuttgart.de/mailman/listinfo/dumux
> 
> ___
> Dumux mailing list
> Dumux@listserv.uni-stuttgart.de
> https://listserv.uni-stuttgart.de/mailman/listinfo/dumux

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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Timo Koch

Hi Samuel,


as an addition to Bernd's answer, you might have to set 
DUNE_GRID_EXPERIMENTAL_GRID_EXTENSIONS:BOOL=TRUE


for compiling dune-grid and the grid modules. I'm not sure if this is 
still required.



Best wishes

Timo


On 08.04.19 17:37, Flemisch, Bernd wrote:


Hi Samuel,


I think that it is given byscvf.boundaryFlag(). Have a look at

https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh


Kind regards

Bernd




--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61    email: be...@iws.uni-stuttgart.de
D-70569 Stuttgart    url: www.hydrosys.uni-stuttgart.de
___

*Von:* Dumux  im Auftrag von 
Samuel Scherrer 

*Gesendet:* Montag, 8. April 2019 17:30:26
*An:* dumux@listserv.uni-stuttgart.de
*Betreff:* [DuMuX] How to get intersections from scvf and element?
Hi Dumux people,

I'm currently trying to use a grid generated with gmsh and would like
to set the boundaries based on BoundaryDomainMarkers.
I found that it's possible to access the boundary domain markers via
the function 'getBoundaryDomainMarkers', which accepts either a
Intersection or a boundary segment index as argument.

How do I now get the intersection/boundary segment index when I have a
given element and scvf, e.g. inside the 'neumann' function (solution
dependent neumann boundary)?

Best regards,
Samuel

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

___
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
___

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


Re: [DuMuX] How to get intersections from scvf and element?

2019-04-08 Thread Flemisch, Bernd
Hi Samuel,


I think that it is given by scvf.boundaryFlag(). Have a look at

https://git.iws.uni-stuttgart.de/dumux-repositories/dumux/blob/master/test/porousmediumflow/co2/implicit/problem.hh


Kind regards

Bernd




--
___

Bernd Flemisch phone: +49 711 685 69162
IWS, Universität Stuttgart fax:   +49 711 685 60430
Pfaffenwaldring 61email: be...@iws.uni-stuttgart.de
D-70569 Stuttgarturl: www.hydrosys.uni-stuttgart.de
___

Von: Dumux  im Auftrag von Samuel 
Scherrer 
Gesendet: Montag, 8. April 2019 17:30:26
An: dumux@listserv.uni-stuttgart.de
Betreff: [DuMuX] How to get intersections from scvf and element?

Hi Dumux people,

I'm currently trying to use a grid generated with gmsh and would like
to set the boundaries based on BoundaryDomainMarkers.
I found that it's possible to access the boundary domain markers via
the function 'getBoundaryDomainMarkers', which accepts either a
Intersection or a boundary segment index as argument.

How do I now get the intersection/boundary segment index when I have a
given element and scvf, e.g. inside the 'neumann' function (solution
dependent neumann boundary)?

Best regards,
Samuel

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