[DuMuX] Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Couple tracer model with 1p_1p test
Dear Timo,
after doing the git pull, I could finally run the 1p_1p test and plug my
network data in, which worked perfectly. However, only the models in the 1d3d
folder seem to work, the tracer and all the other models are not running, there
seems to be a CMake linking problem, as I cannot build the code through the
build-cmake folder ("No rule to make target `test_3d2p' ").
Already tried building the build-cmake folder again a few times.
I guess these problems are all linked to the actual changes due to the
development in this branch.
Any ideas ?
Best,
Berk
-Timo <koch_t...@hotmail.com> schrieb: -
An: "dumux@listserv.uni-stuttgart.de" <dumux@listserv.uni-stuttgart.de>
Von: Timo <koch_t...@hotmail.com>
Datum: 16.05.2018 11:17
Kopie: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch>
Betreff: Re: [DuMuX] Antwort: Re: Antwort: Re: Antwort: Re: Couple tracer model
with 1p_1p test
Hi Berk,
can you do a git pull origin feature/multidomain-on-3.0 on the
feature/multidomain-on-3.0 branch? As this branch is currently under heavy
development there are a lot of changes
and it might happen that temporarily not everything compiles. We'll clean that
up later. After the git pull, the 1p_1p example should hopefully work again.
Timo
On 16.05.2018 11:03, berk.ner...@uzh.ch wrote:
Dear Timo,
I cloned the dune-foamgrid module and rebuild the build-cmake folder after
deleting the old one in dumux. The foam grid module has been found as an
optional module.
Still getting errors (this time " error: no matching member function for call
to 'updateCouplingContext' "), but different ones.
I attached a part of the output to the email as it was very long.
Thank you again.
Best,
Berk
-Timo <koch_t...@hotmail.com> schrieb: -
An: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch>
Von: Timo <koch_t...@hotmail.com>
Datum: 16.05.2018 10:23
Kopie: "dumux@listserv.uni-stuttgart.de" <dumux@listserv.uni-stuttgart.de>
Betreff: Re: Antwort: Re: Antwort: Re: [DuMuX] Couple tracer model with 1p_1p
test
Dear Berk,
you need the dune-foamgrid module
(https://gitlab.dune-project.org/extensions/dune-foamgrid) which is a grid
manager for surface and network grids to run this example.
You need to rerun the dunecontrol script. You might need to delete the build
folders first. The CMake output of the dumux module will print if dune-foamgrid
has been found as an additional module.
Timo
Viele Grüße,
Timo
Am 16.05.2018 um 10:08 schrieb <berk.ner...@uzh.ch> <berk.ner...@uzh.ch>:
Dear Timo,
please find the terminal output of make test_1p_1p attached to this e-mail.
Also thank you for the hint, I have rebuild the build-cmake folder with the
optic.opts option file now (the output when trying to build test_1p_1p is still
the same).
Best,
Berk
-Timo <koch_t...@hotmail.com> schrieb: -
An: DuMuX User Forum <dumux@listserv.uni-stuttgart.de>
Von: Timo <koch_t...@hotmail.com>
Datum: 15.05.2018 17:51
Kopie: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch>
Betreff: Re: Antwort: Re: [DuMuX] Couple tracer model with 1p_1p test
On 15.05.2018 17:43, berk.ner...@uzh.ch wrote:
Dear Timo,
Thank you very much for the hints.
I know what you mean with the different versions and branches now, but I used
dune1 and dune2 in the email because I wasn't sure which dune and dumux
versions I was actually using.
I now downloaded the newest versions of dune and dumux (dune 2.6 and dumux
2.12, as "git clone -b releases/3.0-git
https://git.iws.uni-stuttgart.de/dumux-repositories/dumux.git; dumux did not
work), and switched to the branch you mentioned (feature/multidomain-on-3.0).
I think that as you said this will resolve the stupid problems I was having. I
seem to have some troubles when compiling everything with
"./dune-common/bin/dunecontrol --opts=dumux/debug.opts all " though, the
build-cmake folder etc. is build without errors, but when entering
/build-cmake/test/multidomain/embedded/1d3d/1p_1p or 1p_richards, I am getting
many errors when compiling with "make test_1p_1p" or "make test 1p_richards".
Hi Berk,
there is no release branch yet for 3.0 because it's not released yet. The
branch is simply called master. The branch with the multidomain code is
feature/multidomain-on-3.0 as you noticed correctly.
Can you attach the output of make test_1p_1p?
BTW using the debug option file will produce very slow code. You can also use
the optim.opts option file and then switch setting the CMAKE_BUILD_TYPE
variable for the specific application you want to debug.
To this end add set(CMAKE_BUILD_TYPE Debug) in the CMakeLists.txt of the
application. Analogously, set(CMAKE_BUILD_TYPE Release) will use compiler
flags that produce optimized binaries.
Timo
Do you have any ideas why this is happening ?
Thank you again for the help.
Best,
Berk
[DuMuX] Antwort: Re: Antwort: Re: Antwort: Re: Antwort: Re: Couple tracer model with 1p_1p test
Hi Timo, Perfect, 1p_1p is finally working, I will do the coupling with the tracer model now. I also noticed that instead of having a 1d3d-problem.hh file to couple flow and tissue, the coupling is done in the cpp-file with the main function in this newer branch, any specific reasons for this change ? Many thanks for the help. Best, Berk -Timo <koch_t...@hotmail.com> schrieb: - An: "dumux@listserv.uni-stuttgart.de" <dumux@listserv.uni-stuttgart.de> Von: Timo <koch_t...@hotmail.com> Datum: 16.05.2018 11:17 Kopie: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch> Betreff: Re: [DuMuX] Antwort: Re: Antwort: Re: Antwort: Re: Couple tracer model with 1p_1p test Hi Berk, can you do a git pull origin feature/multidomain-on-3.0 on the feature/multidomain-on-3.0 branch? As this branch is currently under heavy development there are a lot of changes and it might happen that temporarily not everything compiles. We'll clean that up later. After the git pull, the 1p_1p example should hopefully work again. Timo On 16.05.2018 11:03, berk.ner...@uzh.ch wrote: Dear Timo, I cloned the dune-foamgrid module and rebuild the build-cmake folder after deleting the old one in dumux. The foam grid module has been found as an optional module. Still getting errors (this time " error: no matching member function for call to 'updateCouplingContext' "), but different ones. I attached a part of the output to the email as it was very long. Thank you again. Best, Berk -Timo <koch_t...@hotmail.com> schrieb: - An: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch> Von: Timo <koch_t...@hotmail.com> Datum: 16.05.2018 10:23 Kopie: "dumux@listserv.uni-stuttgart.de" <dumux@listserv.uni-stuttgart.de> Betreff: Re: Antwort: Re: Antwort: Re: [DuMuX] Couple tracer model with 1p_1p test Dear Berk, you need the dune-foamgrid module (https://gitlab.dune-project.org/extensions/dune-foamgrid) which is a grid manager for surface and network grids to run this example. You need to rerun the dunecontrol script. You might need to delete the build folders first. The CMake output of the dumux module will print if dune-foamgrid has been found as an additional module. Timo Viele Grüße, Timo Am 16.05.2018 um 10:08 schrieb <berk.ner...@uzh.ch> <berk.ner...@uzh.ch>: Dear Timo, please find the terminal output of make test_1p_1p attached to this e-mail. Also thank you for the hint, I have rebuild the build-cmake folder with the optic.opts option file now (the output when trying to build test_1p_1p is still the same). Best, Berk -Timo <koch_t...@hotmail.com> schrieb: - An: DuMuX User Forum <dumux@listserv.uni-stuttgart.de> Von: Timo <koch_t...@hotmail.com> Datum: 15.05.2018 17:51 Kopie: "berk.ner...@uzh.ch" <berk.ner...@uzh.ch> Betreff: Re: Antwort: Re: [DuMuX] Couple tracer model with 1p_1p test On 15.05.2018 17:43, berk.ner...@uzh.ch wrote: Dear Timo, Thank you very much for the hints. I know what you mean with the different versions and branches now, but I used dune1 and dune2 in the email because I wasn't sure which dune and dumux versions I was actually using. I now downloaded the newest versions of dune and dumux (dune 2.6 and dumux 2.12, as "git clone -b releases/3.0-git https://git.iws.uni-stuttgart.de/dumux-repositories/dumux.git; dumux did not work), and switched to the branch you mentioned (feature/multidomain-on-3.0). I think that as you said this will resolve the stupid problems I was having. I seem to have some troubles when compiling everything with "./dune-common/bin/dunecontrol --opts=dumux/debug.opts all " though, the build-cmake folder etc. is build without errors, but when entering /build-cmake/test/multidomain/embedded/1d3d/1p_1p or 1p_richards, I am getting many errors when compiling with "make test_1p_1p" or "make test 1p_richards". Hi Berk, there is no release branch yet for 3.0 because it's not released yet. The branch is simply called master. The branch with the multidomain code is feature/multidomain-on-3.0 as you noticed correctly. Can you attach the output of make test_1p_1p? BTW using the debug option file will produce very slow code. You can also use the optim.opts option file and then switch setting the CMAKE_BUILD_TYPE variable for the specific application you want to debug. To this end add set(CMAKE_BUILD_TYPE Debug) in the CMakeLists.txt of the application. Analogously, set(CMAKE_BUILD_TYPE Release) will use compiler flags that produce optimized binaries. Timo Do you have any ideas why this is happening ? Thank you again for the help. Best, Berk -Timo <koch_t...@hotmail.com> schrieb: - An: "dumux@listserv.uni-stuttgart.de" <dumux@listserv.uni-stuttgart.de> Von: Timo <koch_t...@hotmail.com> Datum: 14.05.2018 16:28 Kopie: "berk.
