gfs-devel Mailing List for The Gerris Flow Solver
Brought to you by:
popinet
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(2) |
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(9) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
2003 |
Jan
(1) |
Feb
(1) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2004 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(6) |
Nov
(3) |
Dec
(3) |
2005 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(3) |
Jul
(17) |
Aug
(7) |
Sep
(3) |
Oct
(5) |
Nov
(1) |
Dec
|
2006 |
Jan
|
Feb
(3) |
Mar
|
Apr
(11) |
May
(1) |
Jun
|
Jul
|
Aug
(7) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
(4) |
May
|
Jun
(5) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
(1) |
Nov
|
Dec
(8) |
2008 |
Jan
(9) |
Feb
|
Mar
(1) |
Apr
(8) |
May
(4) |
Jun
(3) |
Jul
(12) |
Aug
(14) |
Sep
(13) |
Oct
(5) |
Nov
(7) |
Dec
(1) |
2009 |
Jan
(7) |
Feb
|
Mar
(2) |
Apr
(13) |
May
(6) |
Jun
(4) |
Jul
(9) |
Aug
(7) |
Sep
(10) |
Oct
(7) |
Nov
(2) |
Dec
(8) |
2010 |
Jan
(7) |
Feb
(4) |
Mar
(7) |
Apr
(7) |
May
(7) |
Jun
(7) |
Jul
(25) |
Aug
(2) |
Sep
(8) |
Oct
(7) |
Nov
(16) |
Dec
(7) |
2011 |
Jan
(12) |
Feb
(6) |
Mar
(7) |
Apr
(2) |
May
(4) |
Jun
|
Jul
(5) |
Aug
(8) |
Sep
(51) |
Oct
(143) |
Nov
(21) |
Dec
(20) |
2012 |
Jan
(40) |
Feb
(23) |
Mar
(13) |
Apr
(9) |
May
(16) |
Jun
(16) |
Jul
(56) |
Aug
(13) |
Sep
(30) |
Oct
(24) |
Nov
(53) |
Dec
(4) |
2013 |
Jan
(16) |
Feb
(2) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(14) |
Dec
(21) |
2014 |
Jan
(3) |
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
(3) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(14) |
Nov
(1) |
Dec
|
2015 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
(2) |
Apr
(2) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
From: Hridyesh K. <Hri...@lo...> - 2019-10-31 07:14:58
|
Hi All, I am getting error in custom input file. OS version centos6.5 Gnu debugger output is below: #0 0x0000003562c32925 in raise () from /lib64/libc.so.6 #1 0x0000003562c34105 in abort () from /lib64/libc.so.6 #2 0x000000356484a98a in g_logv () from /lib64/libglib-2.0.so.0 #3 0x000000356484aa23 in g_log () from /lib64/libglib-2.0.so.0 #4 0x00002b2118c48862 in height_normal (cell=0x146e498, v=0x1330fd0) at vof.c:3430 #5 vof_height_plane (cell=0x146e498, v=0x1330fd0) at vof.c:3453 #6 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #7 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #8 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #9 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #10 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #11 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #12 0x00002b2118bdc21c in cell_traverse_level (cell=<value optimized out>, max_depth=10, func=0x2b2118c48720 <vof_height_plane>, data=0x1330fd0) at ftt.c:829 #13 0x00002b2118c17ac3 in domain_foreach (c=<value optimized out>, func=0x2b2118c137a0 <box_traverse>, data=0x7fffbf8dc280) at domain.c:615 #14 0x00002b2118c11ea2 in gfs_domain_cell_traverse (domain=<value optimized out>, order=<value optimized out>, flags=<value optimized out>, max_depth=<value optimized out>, func=<value optimized out>, data=<value optimized out>) at domain.c:1400 #15 0x00002b2118c43d02 in variable_tracer_vof_height_update (v=0x1330fd0, domain=0x1325220) at vof.c:3513 #16 0x00002b2118c449e0 in variable_tracer_vof_event (event=0x1330fd0, sim=0x1325220) at vof.c:992 #17 0x00002b2118c29584 in gfs_simulation_init (sim=0x1325220) at simulation.c:1073 #18 0x00002b2118c2c738 in simulation_run (sim=0x1325220) at simulation.c:456 #19 0x00002b2118c28268 in gfs_simulation_run (sim=0x1325220) at simulation.c:1806 #20 0x0000000000402b98 in main (argc=3, argv=0x7fffbf8dc708) at gerris.c:494 Thanks & regards, [https://www.locuz.com/in/Signature/images/locuz_logo.png] [https://www.locuz.com/in/Signature/images/fb.png]<https://www.facebook.com/locuz.esl> [https://www.locuz.com/in/Signature/images/tw.png] <https://twitter.com/LocuzInc> [https://www.locuz.com/in/Signature/images/in.png] <https://www.linkedin.com/company/locuz-enterprise-solutions-ltd> [https://www.locuz.com/in/Signature/images/yt.png] <https://www.youtube.com/channel/UCRcTXqPR2I5mBWee6ChFKpA?view_as=subscriber> Hridyesh Kumar Locuz Enterprise Solutions Ltd [https://www.locuz.com/in/Signature/images/mail.png] hri...@lo...<mailto:hri...@lo...> [https://www.locuz.com/in/Signature/images/web.png] www.locuz.com<https://www.locuz.com/in/> [https://www.locuz.com/in/Signature/images/ClouTor.png]<https://www.locuz.com/in/products/cloutor/> [https://www.locuz.com/in/Signature/images/ganana.png]<https://www.locuz.com/in/products/ganana-cluster-manager> [https://www.locuz.com/in/Signature/images/Conquo.png]<https://www.locuz.com/in/products/conquo> |
From: Rexmelle D. Jr. <rex...@ya...> - 2017-09-15 00:26:42
|
Hi, I'm a beginner on Gerris and trying to run some of the examples provided. I am using ubuntu 16.04 and I can't run some of the examples that requires libwavewatch2D.so. I tried to install the wwatch3 module and downloaded the source code. I have already compiled, however, I still can't install the module. Thanks,Rexmelle Decapia |
From: Pramod K. <pra...@gm...> - 2017-07-05 11:33:02
|
Dear all, I have some saved gerris results files (e.g. "results_time_N.gfs", where N = 0.5, 1.0, 1.5, 2.0, ......) at a fixed time interval (e.g. 0.5 s) from a previous gfs simulation. In a new simulation, I want to read U, V, W variables from these saved simulation results files at a fixed time interval (e.g. 0.5 s). I want to use these U, V, W values for a tracer dispersion in the same domain so that I do no have to solve again for the flow-filed from gerris. For this I can replace the 'GfsSimulation' with 'GfsAdvection' in a starting result file and can solve for the tracer dispersion only with constant flow with respect to time. But in order to change the flow-filed at a fixed time interval, I need to read these saved gerris results files for U, V, W and replace the previous U, V, W values from the new ones. Can anyone please suggest me how to read these .gfs results file for flow-field at the fixed time intervals and use them in the gerris script to replace the previous flow? I think if we could read these result files, we can use them in Init{} to replace the previous U, V, W with new values at each time interval? I have searched for answers but couldn't find any. Hope someone can help me. Thanks in advance :) Pramod -- Dr. Pramod Kumar Laboratoire de Mecanique et Energetique d'Evry (LMEE), Universite d'Evry-Val d'Essonne 40 Rue du Pelvoux, Evry Cedex-91020, France Email: pra...@un..., pra...@gm... |
From: 王瑞 <229...@qq...> - 2017-04-25 08:14:54
|
Dear professor I'd like to add our codes concerning Moving Contact Lines to Gerris. We use Phase Field Method(PFM) to trace the iunterface. My question is that,: 1. Is Gmodule the only way to add code to Gerris? 2. If I define a new Gmodule PhaseField, what should I do in this Gmodule so that simulation_run() will call PF function instead of VOF Tracer function? I am looking forward to your reply urgently. Best regards Ray |
From: 王瑞 <229...@qq...> - 2017-04-10 13:02:46
|
Dear Professor, I am so sorry that your reply was blocked out by my QQ e-mail and I didn't see it until now! I thought there was no reply from Gfs_devel. Actually, I have started reading the Gerris source codes, but it is really difficult to understand for a beginner without any guidance. Since you suggested that I should use Basilisk rather than Gerris, would it be better if I turn to use Basilisk now? I have been studying Gerris for almost two months, including reading your articles in 2003 and 2009. Now I can use Gerris language to design and simulate simple problems. I am wondering whether this experience would help if I turn to Basilisk. Should I use Basilisk instead of Gerris now? I am looking forward to your reply. Best regards, Ray ------------------ Original ------------------ From: "Stephane Popinet";<po...@ba...>; Date: Wed, Mar 8, 2017 10:01 PM To: "gfs-devel"<gfs...@li...>; Subject: Re: [Gfs-devel] Help: How to read the source code efficiently andadd our code to Gerris? Dear Ray, Have you read: http://gfs.sourceforge.net/wiki/index.php/Gerris_Flow_Solver_Programming_Course_for_Dummies You should also consider using Basilisk rather than Gerris, as it is a much simpler code. http://basilisk.fr cheers Stephane ------------------------------------------------------------------------------ Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford _______________________________________________ Gfs-devel mailing list Gfs...@li... https://lists.sourceforge.net/lists/listinfo/gfs-devel |
From: Stephane P. <po...@ba...> - 2017-03-08 14:02:09
|
Dear Ray, Have you read: http://gfs.sourceforge.net/wiki/index.php/Gerris_Flow_Solver_Programming_Course_for_Dummies You should also consider using Basilisk rather than Gerris, as it is a much simpler code. http://basilisk.fr cheers Stephane |
From: 王瑞 <229...@qq...> - 2017-03-08 08:53:59
|
Dear professor, I am a fresh graduate student from Department of Fluid Mechanics, University of Science and Technology of China. I am very interested in quad/octree AMR and want to become a developer of Gerris by adding our code concerning Moving Contact Lines(MCL) to Gerris. But I have trouble reading the source code because I don't know the exact meaning or function of each variable and function. I am wondering that is there any advice or guide from you to help me understand the source code more efficiently, which will speed up the process we add our code to Gerris. By the way, how to add new code to Gerris is also a problem, and I will be appreciated if you teach me how to operate it. Best Regards, Ray |
From: Vladimir K. <vla...@cf...> - 2016-09-16 17:04:51
|
Justin, we use the latest version of gtk: gtkglext-1.2.0.tar.bz2. All the best, Vladimir On 9/16/2016 10:16 AM, Justin Goldsmith wrote: I have ftgl and several versions of gtk installed. Is gfsview dependent on specific versions of these? checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GERRIS2D... yes checking for GERRIS3D... yes checking for OSMESA... yes checking for GTK... no configure: WARNING: GTK dependencies not met. checking for FTGL... no configure: WARNING: FTGL dependencies not met. configure: creating ./config.status config.status: creating Makefile config.status: creating view/Makefile config.status: creating view/desktop/Makefile config.status: creating gl2ps/Makefile config.status: creating gl/Makefile config.status: creating batch/Makefile config.status: creating debian/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands [root@2014lab4 gfsview-snapshot-121130]# dnf install gtk1 gtk2 gtk3 ftgl Last metadata expiration check: 0:24:56 ago on Fri Sep 16 09:26:13 2016. Package gtk+-1:1.2.10-82.fc24.x86_64 is already installed, skipping. Package gtk2-2.24.31-1.fc24.x86_64 is already installed, skipping. Package gtk3-3.20.9-1.fc24.x86_64 is already installed, skipping. Package ftgl-2.1.3-0.14.rc5.fc24.x86_64 is already installed, skipping. Dependencies resolved. Nothing to do. Complete! Thanks, Justin D Goldsmith IT Manager Center for Space Plasma and Aeronomic Research<http://www.uah.edu/cspar> Office: CRH2007<https://goo.gl/maps/sXf3DeHNrQm> - Phone: 256-961-7787 On Tue, Sep 6, 2016 at 10:07 AM, Justin Goldsmith <jd...@ua...<mailto:jd...@ua...>> wrote: Any idea what the names of the packages are for those dependencies for Fedora 23 (through either dnf or a manual download)? I thought I had them installed, but it may be the wrong versions or wrong packages in general. Thanks, Justin D Goldsmith IT Manager Center for Space Plasma and Aeronomic Research<http://www.uah.edu/cspar> Office: CRH2007<https://goo.gl/maps/sXf3DeHNrQm> - Phone: 256-961-7787<tel:256-961-7787> On Thu, Sep 1, 2016 at 2:12 AM, Stephane Popinet <po...@ba...<mailto:po...@ba...>> wrote: Hi Justin, Several required libraries are missing/badly configured on your system: > checking for OSMESA... yes > checking for GTK... no > configure: WARNING: GTK dependencies not met. You will only have gfsview-batch, not gfsview (which requires GTK for the graphical interface). > checking for FTGL... no > configure: WARNING: FTGL dependencies not met. You won't have "text" objects in gfsview. > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory > compilation terminated. OpenGL/Mesa is not installed/configured properly on your system. hope this helps Stephane ------------------------------------------------------------------------------ _______________________________________________ Gfs-devel mailing list Gfs...@li...<mailto:Gfs...@li...> https://lists.sourceforge.net/lists/listinfo/gfs-devel |
From: Justin G. <jd...@ua...> - 2016-09-16 15:15:42
|
I have ftgl and several versions of gtk installed. Is gfsview dependent on specific versions of these? checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GERRIS2D... yes checking for GERRIS3D... yes checking for OSMESA... yes checking for GTK... no configure: WARNING: GTK dependencies not met. checking for FTGL... no configure: WARNING: FTGL dependencies not met. configure: creating ./config.status config.status: creating Makefile config.status: creating view/Makefile config.status: creating view/desktop/Makefile config.status: creating gl2ps/Makefile config.status: creating gl/Makefile config.status: creating batch/Makefile config.status: creating debian/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands [root@2014lab4 gfsview-snapshot-121130]# dnf install gtk1 gtk2 gtk3 ftgl Last metadata expiration check: 0:24:56 ago on Fri Sep 16 09:26:13 2016. Package gtk+-1:1.2.10-82.fc24.x86_64 is already installed, skipping. Package gtk2-2.24.31-1.fc24.x86_64 is already installed, skipping. Package gtk3-3.20.9-1.fc24.x86_64 is already installed, skipping. Package ftgl-2.1.3-0.14.rc5.fc24.x86_64 is already installed, skipping. Dependencies resolved. Nothing to do. Complete! Thanks, Justin D Goldsmith *IT Manager* *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: 256-961-7787* On Tue, Sep 6, 2016 at 10:07 AM, Justin Goldsmith <jd...@ua...> wrote: > Any idea what the names of the packages are for those dependencies for > Fedora 23 (through either dnf or a manual download)? I thought I had them > installed, but it may be the wrong versions or wrong packages in general. > > > > Thanks, > Justin D Goldsmith > *IT Manager* > *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* > *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: > 256-961-7787 <256-961-7787>* > > On Thu, Sep 1, 2016 at 2:12 AM, Stephane Popinet <po...@ba...> > wrote: > >> Hi Justin, >> >> Several required libraries are missing/badly configured on your system: >> >> > checking for OSMESA... yes >> > checking for GTK... no >> > configure: WARNING: GTK dependencies not met. >> >> You will only have gfsview-batch, not gfsview (which requires GTK for >> the graphical interface). >> >> > checking for FTGL... no >> > configure: WARNING: FTGL dependencies not met. >> >> You won't have "text" objects in gfsview. >> >> > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory >> > compilation terminated. >> >> OpenGL/Mesa is not installed/configured properly on your system. >> >> hope this helps >> >> Stephane >> >> ------------------------------------------------------------ >> ------------------ >> _______________________________________________ >> Gfs-devel mailing list >> Gfs...@li... >> https://lists.sourceforge.net/lists/listinfo/gfs-devel >> > > |
From: Justin G. <jd...@ua...> - 2016-09-06 16:04:25
|
Any idea what the names of the packages are for those dependencies for Fedora 23 (through either dnf or a manual download)? I thought I had them installed, but it may be the wrong versions or wrong packages in general. Thanks, Justin D Goldsmith *IT Manager* *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: 256-961-7787* On Thu, Sep 1, 2016 at 2:12 AM, Stephane Popinet <po...@ba...> wrote: > Hi Justin, > > Several required libraries are missing/badly configured on your system: > > > checking for OSMESA... yes > > checking for GTK... no > > configure: WARNING: GTK dependencies not met. > > You will only have gfsview-batch, not gfsview (which requires GTK for > the graphical interface). > > > checking for FTGL... no > > configure: WARNING: FTGL dependencies not met. > > You won't have "text" objects in gfsview. > > > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory > > compilation terminated. > > OpenGL/Mesa is not installed/configured properly on your system. > > hope this helps > > Stephane > > ------------------------------------------------------------ > ------------------ > _______________________________________________ > Gfs-devel mailing list > Gfs...@li... > https://lists.sourceforge.net/lists/listinfo/gfs-devel > |
From: Stephane P. <po...@ba...> - 2016-09-01 07:12:39
|
Hi Justin, Several required libraries are missing/badly configured on your system: > checking for OSMESA... yes > checking for GTK... no > configure: WARNING: GTK dependencies not met. You will only have gfsview-batch, not gfsview (which requires GTK for the graphical interface). > checking for FTGL... no > configure: WARNING: FTGL dependencies not met. You won't have "text" objects in gfsview. > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory > compilation terminated. OpenGL/Mesa is not installed/configured properly on your system. hope this helps Stephane |
From: Justin G. <jd...@ua...> - 2016-08-31 20:27:13
|
Hi guys, I just signed up for this list, so I hope I'm asking the right list about this. I've got the whole gerris suite installed except for gfsview. When I try to run ./configure, this is my readout: --------------------------------- [root@2014lab4 gfsview-snapshot-121130]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for mpicc... no checking for style of include used by make... GNU checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for library containing strerror... none required checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking whether gcc and cc understand -c and -o together... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for fgrep... /usr/bin/grep -F checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B checking the name lister (/usr/bin/nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1572864 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop checking for /usr/bin/ld option to reload object files... -r checking for objdump... objdump checking how to recognize dependent libraries... pass_all checking for dlltool... dlltool checking how to associate runtime and link libraries... printf %s\n checking for ar... ar checking for archiver @FILE support... @ checking for strip... strip checking for ranlib... ranlib checking command to parse /usr/bin/nm -B output from gcc object... ok checking for sysroot... no checking for mt... no checking if : is a manifest tool... no checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if gcc supports -fno-rtti -fno-exceptions... no checking for gcc option to produce PIC... -fPIC -DPIC checking if gcc PIC flag -fPIC -DPIC works... yes checking if gcc static flag -static works... no checking if gcc supports -c -o file.o... yes checking if gcc supports -c -o file.o... (cached) yes checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes checking whether -lc should be explicitly linked in... no checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for GERRIS2D... yes checking for GERRIS3D... yes checking for OSMESA... yes checking for GTK... no configure: WARNING: GTK dependencies not met. checking for FTGL... no configure: WARNING: FTGL dependencies not met. configure: creating ./config.status config.status: creating Makefile config.status: creating view/Makefile config.status: creating view/desktop/Makefile config.status: creating gl2ps/Makefile config.status: creating gl/Makefile config.status: creating batch/Makefile config.status: creating debian/Makefile config.status: creating config.h config.status: config.h is unchanged config.status: executing depfiles commands config.status: executing libtool commands [root@2014lab4 gfsview-snapshot-121130]# --------------------------------- Then when I try and make, this is what happens --------------------------------- [root@2014lab4 gfsview-snapshot-121130]# make make all-recursive make[1]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130' Making all in gl2ps make[2]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' Making all in gl make[2]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/local/share/gfsview"\" -DPACKAGE_LOCALE_DIR=\""/usr/local//locale"\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF .deps/libgfsgl2D_la-gfsgl.Tpo -c -o libgfsgl2D_la-gfsgl.lo `test -f 'gfsgl.c' || echo './'`gfsgl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/local/share/gfsview\" -DPACKAGE_LOCALE_DIR=\"/usr/local//locale\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF .deps/libgfsgl2D_la-gfsgl.Tpo -c gfsgl.c -fPIC -DPIC -o .libs/libgfsgl2D_la-gfsgl.o gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory compilation terminated. Makefile:358: recipe for target 'libgfsgl2D_la-gfsgl.lo' failed make[2]: *** [libgfsgl2D_la-gfsgl.lo] Error 1 make[2]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl' Makefile:335: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130' Makefile:264: recipe for target 'all' failed make: *** [all] Error 2 [root@2014lab4 gfsview-snapshot-121130]# --------------------------------- Then of course, make install fails as well --------------------------------- [root@2014lab4 gfsview-snapshot-121130]# make install Making install in gl2ps make[1]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' make[2]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' make[2]: Nothing to be done for 'install-exec-am'. make[2]: Nothing to be done for 'install-data-am'. make[2]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' make[1]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl2ps' Making install in gl make[1]: Entering directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\""/usr/local/share/gfsview"\" -DPACKAGE_LOCALE_DIR=\""/usr/local//locale"\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF .deps/libgfsgl2D_la-gfsgl.Tpo -c -o libgfsgl2D_la-gfsgl.lo `test -f 'gfsgl.c' || echo './'`gfsgl.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/local/share/gfsview\" -DPACKAGE_LOCALE_DIR=\"/usr/local//locale\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF .deps/libgfsgl2D_la-gfsgl.Tpo -c gfsgl.c -fPIC -DPIC -o .libs/libgfsgl2D_la-gfsgl.o gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory compilation terminated. Makefile:358: recipe for target 'libgfsgl2D_la-gfsgl.lo' failed make[1]: *** [libgfsgl2D_la-gfsgl.lo] Error 1 make[1]: Leaving directory '/home/jgoldsmith/Downloads/gfsview-snapshot-121130/gl' Makefile:335: recipe for target 'install-recursive' failed make: *** [install-recursive] Error 1 [root@2014lab4 gfsview-snapshot-121130]# --------------------------------- Any help or recommendations you might have would be greatly appreciated. Thanks, Justin D Goldsmith *IT Manager* *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: 256-961-7787* |
From: Justin G. <jd...@ua...> - 2016-08-31 20:19:44
|
I should specify that I'm installing from source on Fedora 23 Thanks, Justin D Goldsmith *IT Manager* *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: 256-961-7787* On Wed, Aug 31, 2016 at 2:56 PM, Justin Goldsmith <jd...@ua...> wrote: > Hi guys, I just signed up for this list, so I hope I'm asking the right > list about this. > > I've got the whole gerris suite installed except for gfsview. When I try > to run ./configure, this is my readout: > > --------------------------------- > [root@2014lab4 gfsview-snapshot-121130]# ./configure > checking build system type... x86_64-unknown-linux-gnu > checking host system type... x86_64-unknown-linux-gnu > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for a thread-safe mkdir -p... /usr/bin/mkdir -p > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > checking whether to enable maintainer-specific portions of Makefiles... no > checking for mpicc... no > checking for style of include used by make... GNU > checking for gcc... gcc > checking whether the C compiler works... yes > checking for C compiler default output file name... a.out > checking for suffix of executables... > checking whether we are cross compiling... no > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking dependency style of gcc... gcc3 > checking for library containing strerror... none required > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking for gcc... (cached) gcc > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking dependency style of gcc... (cached) gcc3 > checking whether gcc and cc understand -c and -o together... yes > checking how to run the C preprocessor... gcc -E > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking how to print strings... printf > checking for a sed that does not truncate output... /usr/bin/sed > checking for fgrep... /usr/bin/grep -F > checking for ld used by gcc... /usr/bin/ld > checking if the linker (/usr/bin/ld) is GNU ld... yes > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B > checking the name lister (/usr/bin/nm -B) interface... BSD nm > checking whether ln -s works... yes > checking the maximum length of command line arguments... 1572864 > checking whether the shell understands some XSI constructs... yes > checking whether the shell understands "+="... yes > checking how to convert x86_64-unknown-linux-gnu file names to > x86_64-unknown-linux-gnu format... func_convert_file_noop > checking how to convert x86_64-unknown-linux-gnu file names to toolchain > format... func_convert_file_noop > checking for /usr/bin/ld option to reload object files... -r > checking for objdump... objdump > checking how to recognize dependent libraries... pass_all > checking for dlltool... dlltool > checking how to associate runtime and link libraries... printf %s\n > checking for ar... ar > checking for archiver @FILE support... @ > checking for strip... strip > checking for ranlib... ranlib > checking command to parse /usr/bin/nm -B output from gcc object... ok > checking for sysroot... no > checking for mt... no > checking if : is a manifest tool... no > checking for sys/types.h... yes > checking for sys/stat.h... yes > checking for stdlib.h... yes > checking for string.h... yes > checking for memory.h... yes > checking for strings.h... yes > checking for inttypes.h... yes > checking for stdint.h... yes > checking for unistd.h... yes > checking for dlfcn.h... yes > checking for objdir... .libs > checking if gcc supports -fno-rtti -fno-exceptions... no > checking for gcc option to produce PIC... -fPIC -DPIC > checking if gcc PIC flag -fPIC -DPIC works... yes > checking if gcc static flag -static works... no > checking if gcc supports -c -o file.o... yes > checking if gcc supports -c -o file.o... (cached) yes > checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports > shared libraries... yes > checking whether -lc should be explicitly linked in... no > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > checking whether to build shared libraries... yes > checking whether to build static libraries... yes > checking for pkg-config... /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for GERRIS2D... yes > checking for GERRIS3D... yes > checking for OSMESA... yes > checking for GTK... no > configure: WARNING: GTK dependencies not met. > checking for FTGL... no > configure: WARNING: FTGL dependencies not met. > configure: creating ./config.status > config.status: creating Makefile > config.status: creating view/Makefile > config.status: creating view/desktop/Makefile > config.status: creating gl2ps/Makefile > config.status: creating gl/Makefile > config.status: creating batch/Makefile > config.status: creating debian/Makefile > config.status: creating config.h > config.status: config.h is unchanged > config.status: executing depfiles commands > config.status: executing libtool commands > [root@2014lab4 gfsview-snapshot-121130]# > --------------------------------- > > > > > > Then when I try and make, this is what happens > > --------------------------------- > [root@2014lab4 gfsview-snapshot-121130]# make > make all-recursive > make[1]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130' > Making all in gl2ps > make[2]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > make[2]: Nothing to be done for 'all'. > make[2]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > Making all in gl > make[2]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -DPACKAGE_DATA_DIR=\""/usr/local/share/gfsview"\" > -DPACKAGE_LOCALE_DIR=\""/usr/local//locale"\" -DG_LOG_DOMAIN=\"GfsGl\" > -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration > -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 > -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF > .deps/libgfsgl2D_la-gfsgl.Tpo -c -o libgfsgl2D_la-gfsgl.lo `test -f > 'gfsgl.c' || echo './'`gfsgl.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/local/share/gfsview\" > -DPACKAGE_LOCALE_DIR=\"/usr/local//locale\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. > -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration > -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 > -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF > .deps/libgfsgl2D_la-gfsgl.Tpo -c gfsgl.c -fPIC -DPIC -o > .libs/libgfsgl2D_la-gfsgl.o > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory > compilation terminated. > Makefile:358: recipe for target 'libgfsgl2D_la-gfsgl.lo' failed > make[2]: *** [libgfsgl2D_la-gfsgl.lo] Error 1 > make[2]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl' > Makefile:335: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130' > Makefile:264: recipe for target 'all' failed > make: *** [all] Error 2 > [root@2014lab4 gfsview-snapshot-121130]# > --------------------------------- > > > > > > > Then of course, make install fails as well > > --------------------------------- > [root@2014lab4 gfsview-snapshot-121130]# make install > Making install in gl2ps > make[1]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > make[2]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > make[2]: Nothing to be done for 'install-exec-am'. > make[2]: Nothing to be done for 'install-data-am'. > make[2]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > make[1]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl2ps' > Making install in gl > make[1]: Entering directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl' > /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. > -DPACKAGE_DATA_DIR=\""/usr/local/share/gfsview"\" > -DPACKAGE_LOCALE_DIR=\""/usr/local//locale"\" -DG_LOG_DOMAIN=\"GfsGl\" > -I.. -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration > -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 > -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF > .deps/libgfsgl2D_la-gfsgl.Tpo -c -o libgfsgl2D_la-gfsgl.lo `test -f > 'gfsgl.c' || echo './'`gfsgl.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR=\"/usr/local/share/gfsview\" > -DPACKAGE_LOCALE_DIR=\"/usr/local//locale\" -DG_LOG_DOMAIN=\"GfsGl\" -I.. > -DFTT_2D=1 -pthread -I/usr/local/include -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -g -O2 -Wall -Werror-implicit-function-declaration > -Wmissing-prototypes -Wmissing-declarations -pipe -std=c99 > -D_XOPEN_SOURCE=500 -MT libgfsgl2D_la-gfsgl.lo -MD -MP -MF > .deps/libgfsgl2D_la-gfsgl.Tpo -c gfsgl.c -fPIC -DPIC -o > .libs/libgfsgl2D_la-gfsgl.o > gfsgl.c:56:22: fatal error: GL/glu.h: No such file or directory > compilation terminated. > Makefile:358: recipe for target 'libgfsgl2D_la-gfsgl.lo' failed > make[1]: *** [libgfsgl2D_la-gfsgl.lo] Error 1 > make[1]: Leaving directory '/home/jgoldsmith/Downloads/ > gfsview-snapshot-121130/gl' > Makefile:335: recipe for target 'install-recursive' failed > make: *** [install-recursive] Error 1 > [root@2014lab4 gfsview-snapshot-121130]# > --------------------------------- > > > > Any help or recommendations you might have would be greatly appreciated. > > > > Thanks, > Justin D Goldsmith > *IT Manager* > *Center for Space Plasma and Aeronomic Research <http://www.uah.edu/cspar>* > *Office: CRH2007 <https://goo.gl/maps/sXf3DeHNrQm> - **Phone: > 256-961-7787 <256-961-7787>* > |
From: Robson N. <rob...@gm...> - 2016-05-09 11:10:40
|
Hello everyone, I realised that in fundamental dimensions the surface tension coefficient has units of [M.T^-2]. But I still keep my question about the function below (I only would like to understand it better): gfs_function_set_units (GFS_SOURCE_TENSION_GENERIC (s)->sigma, 1.); in GfsSourceTension (tension.c line 327). Considering the function 'gfs_function_set_units ()' sets the spatial dimension [L], why this function is setting [L^1] for the surface tension coefficient? Regards, Robson |
From: HE, He CM [ME] <he....@po...> - 2016-05-04 15:19:53
|
Dear Stephane and other guys, Currently, I am doing the droplets impacting on the dry solid surface. In terms of the dynamic angle, I know the work had been done by Mr. S. Afkham (JCP 2009), however, I just used the simple dynamic contact model (Tanner's Law) by returning a dynamic contact angle value. 1. After reading source code about the function named "bc_angle_read", and "gfs_function_set_units (GFS_BC_VALUE (*o)->val, 0.);", it is hard to see how the specific values of contact angle be read into the program. 2. If I set "BcAngle T -1000", it is not physical for sure, but the program will not end. The droplet still occurs wetting on the surface. I suppose that kind of robustness should be included in Gerris. The Gerris version I used is: gerris: using 2D libgfs version 1.3.2 (131206-155120) compiled with flags: MPI: yes pkg-config: yes m4: yes Copyright (C) 2001-2011 NIWA. 3. I also would like to know where are the keywords in input files stored in source codes. I put all files (GTS & GERRIS source code files) together, and using command, e.g. grep --include=\*.{c,h} -rnw '/home/path'/ -e "BcAngle" but cannot find this keyword. In that case, I curious how the code read the input file by predicting each keyword? I am new to Gerris code. Any suggestions? Thanks in advance! Best Regards, Andy HE [http://mlm.polyu.edu.hk/intimate/templates/images/PolyU/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information. |
From: HE, He CM [ME] <he....@po...> - 2016-05-03 10:47:48
|
Dear Stephane, I would like to ask for some help about the droplet impacting on a dry solid surface. 1. Firstly, it is the boundary condition, how the VOF tracer variable to be assigned on the default symmetric boundary at every time step. Does the value on the boundary [http://mlm.polyu.edu.hk/intimate/templates/images/PolyU/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information. |
From: HE, He CM [ME] <he....@po...> - 2016-05-03 10:47:15
|
Dear Stephane, I would like to ask for some help about the droplet impacting on a dry solid surface. 1. Firstly, it is the boundary condition, how the VOF tracer variable to be assigned on the default symmetric boundary at every time step? Are the VOF tracer values on the boundary assigned according to the intermediately interior cells? 2. If I use default boundary (with V=0 if the boundary is vertical) as no-slip boundary condition, do I need to care about the VOF tracer value on the boundary? 3. In terms of the contact angle, does it workable only when the cells close to the solid surface with a non-zero VOF tracer value? Becasue I find when I implement VOFTracer=1 on the boundary condition every time step, the different contact angles seem to yield the same resluts. Thank you in advance! Best Regards, Andy He ________________________________ From: HE, He CM [ME] Sent: Tuesday, May 3, 2016 6:33 PM To: gfs...@li...; Gfs...@li... Subject: droplet impacting on a dry solid surface Dear Stephane, I would like to ask for some help about the droplet impacting on a dry solid surface. 1. Firstly, it is the boundary condition, how the VOF tracer variable to be assigned on the default symmetric boundary at every time step. Does the value on the boundary [http://mlm.polyu.edu.hk/intimate/templates/images/PolyU/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information. |
From: HE, He CM [ME] <he....@po...> - 2016-04-26 06:48:01
|
Dear Gerris developers, I have been using Gerris code to do lots of simulations on droplets collision recently. However, I am really want to step into the source code. Thus, I am writing to ask for several instructions that how to get it started easily. During the code reading, I quite know the ingenious code inplement, however, I don't know how ingenious it is. Specifically, take several lines of code as example: GfsEventClass * gfs_adapt_thickness_class (void) { static GfsEventClass * klass = NULL; if (klass == NULL) { GtsObjectClassInfo info = { "GfsAdaptThickness", sizeof (GfsAdaptThickness), sizeof (GfsEventClass), (GtsObjectClassInitFunc) gfs_adapt_thickness_class_init, (GtsObjectInitFunc) gfs_adapt_thickness_init, (GtsArgSetFunc) NULL, (GtsArgGetFunc) NULL }; klass = gts_object_class_new (GTS_OBJECT_CLASS (gfs_adapt_class ()), &info); } return klass; } This kind of code occurs almost in every class definition. However, for me, it is where hardly to follow. I appreciate a lot if anyone could give me some guidances about how to get into the code from the begining. for example, the book which contains the class inplements that very close to that in Gerris, or some prerequsites to read the code. Actually, I have some programming experience, but far more simple simulation. Thanks in advance and best regards, Andy He [http://mlm.polyu.edu.hk/intimate/templates/images/PolyU/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information. |
From: HE, He CM [ME] <he....@po...> - 2016-04-26 06:48:00
|
Dear Gerris developers, I have been using Gerris code to do lots of simulations on droplets collision recently. However, I am really want to step into the source code. Thus, I am writing to ask for several instructions that how to get it started easily. During the code reading, I quite know the ingenious code inplement, however, I don't know how ingenious it is. Specifically, take several lines of code as example: GfsEventClass * gfs_adapt_thickness_class (void) { static GfsEventClass * klass = NULL; if (klass == NULL) { GtsObjectClassInfo info = { "GfsAdaptThickness", sizeof (GfsAdaptThickness), sizeof (GfsEventClass), (GtsObjectClassInitFunc) gfs_adapt_thickness_class_init, (GtsObjectInitFunc) gfs_adapt_thickness_init, (GtsArgSetFunc) NULL, (GtsArgGetFunc) NULL }; klass = gts_object_class_new (GTS_OBJECT_CLASS (gfs_adapt_class ()), &info); } return klass; } This kind of code occurs almost in every class definition. However, for me, it is where hardly to follow. I appreciate a lot if anyone could give me some guidances about how to get into the code from the begining. for example, the book which contains the class inplements that very close to that in Gerris, or some prerequsites to read the code. Actually, I have some programming experience, but far more simple simulation. Thanks in advance and best regards, Andy He [http://mlm.polyu.edu.hk/intimate/templates/images/PolyU/PolyU_Email_Signature.jpg] Disclaimer: This message (including any attachments) contains confidential information intended for a specific individual and purpose. If you are not the intended recipient, you should delete this message and notify the sender and The Hong Kong Polytechnic University (the University) immediately. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited and may be unlawful. The University specifically denies any responsibility for the accuracy or quality of information obtained through University E-mail Facilities. Any views and opinions expressed are only those of the author(s) and do not necessarily represent those of the University and the University accepts no liability whatsoever for any losses or damages incurred or caused to any party as a result of the use of such information. |
From: Robson N. <rob...@gm...> - 2016-04-20 09:39:54
|
Dear All, I'm confused about the function gfs_function_set_units (GFS_SOURCE_TENSION_GENERIC (s)->sigma, 1.); in GfsSourceTension (tension.c line 327). Considering that surface tension coefficient has unit of forcer per unit length [N].[m]^-1, the unit in the above function would not be -1? Regards, Robson |
From: Vladimir K. <vi...@cf...> - 2015-10-01 15:51:41
|
Dear Gerris developers, We have a question of how to solve the gerris NS solver in a restricted domain. If we have a VOF variable which defines a solid-gas interface (no GfsSolid objects in the domain). We want to solve the NS solver only in the gas phase. If we limit ourselves to the stair-step approximation (in which the VOF variable can be a standard variable), we have to set dp/dn = 0 and U=V=W=0 on the gas-solid interface faces (full cell faces) and solve the pressure correction and velocity-momentum (advection+diffusion) only in the gas phase. Is there a simple solution to do this without going deep into the code ? Thanks, Vladimir |
From: Vladimir K. <vi...@cf...> - 2015-01-05 20:35:28
|
Jose, In addition to your patch, one needs to add: gfs_all_reduce (domain, v->centered, MPI_INT, MPI_MIN); after "has_dirichlet" call. This will properly set the "v->centered" flag for parallel runs. Otherwise, some procs (which do not have solid objects) will have v->centered = TRUE and this will mess up the things (especially the linear/hypre solver stencils) Regards, Vladimir On 1/12/2014 9:53 AM, Jose M. López-Herrera Sánchez wrote: > Hi all, > > Actually, the gfsvariablePoisson does not solve properly when solids > are present. This is due to a wrong argument at > gfs_poisson_coefficients (). The attached patch correct this issue. > > Cheers > > Jose > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > > > _______________________________________________ > Gfs-devel mailing list > Gfs...@li... > https://lists.sourceforge.net/lists/listinfo/gfs-devel |
From: Vladimir K. <vi...@cf...> - 2015-01-05 19:16:27
|
Dear Gerris developers, There is an issue with initialization of the Hypre module in that the Hypre solvers (hypre_diffusion_solve and hypre_poisson_solve) are (almost) never activated for GfsVariableTracer and GfsVariablePoisson. The only case when they are activated is when "GModule hypre" line comes after GfsVariableTracer/GfsVariablePoisson declaration in the parameter file. This is almost never the case (especially for restart files when "GModule hypre" are written at the header of the output files). To fix this issue, the following block from hypre.c/gfs_module_read has to be repeated at the end of simulation_read: {//this takes care of HYPRE module initialization GSList * i = GFS_DOMAIN (sim)->variables; while (i) { if (GFS_IS_VARIABLE_TRACER (i->data)) { GfsAdvectionParams * par = &sim->advection_params; if (par->diffusion_solve != gfs_diffusion) { fprintf (stderr, "setting HYPRE solver for var = %s \n", GFS_VARIABLE (i->data)->name); GFS_VARIABLE_TRACER (i->data)->advection.diffusion_solve = par->diffusion_solve; } } else if (GFS_IS_VARIABLE_POISSON (i->data)) { GfsMultilevelParams * par = &sim->approx_projection_params; if (par->poisson_solve != gfs_poisson_solve) { fprintf (stderr, "setting HYPRE solver for var = %s \n", GFS_VARIABLE (i->data)->name); GFS_VARIABLE_POISSON (i->data)->par.poisson_solve = par->poisson_solve; } } i = i->next; } }//end HYPRE module initialization Because gfs_module_read typically comes before GtsObject reads (including GfsVariable reads), the variables are not yet set and hypre solvers are not properly initialized. (Similarly, the solvers for SourceViscosity and SourceDiffusion need to be treated). Hope it's useful for those using the Hypre module. Regards, Vladimir |
From: Stephane Z. <ste...@gm...> - 2014-11-01 07:27:49
|
Dear Frederik IMHO, since you are trying to develop a vapor bubble model you would be better off developping it in basilisk which is Stephane P's next piece of sofware. You would have much better control of the steps of the algorithm. hope it helps Stéphane Le 30 oct. 2014 à 23:16+0100, Frederik Brasz <cf...@gm...> a écrit : > Hi all, > > I've been working through the code and trying to understand which variables are modified in each step of the simulation and how they affect other steps, and I'm stuck at the lines gfs_source_tension_coefficients and gfs_correct_normal_velocities within gfs_velocity_face_sources, which is called from mac_projection. > > In gfs_source_tension_coefficients, from my understanding, the result is to traverse all faces where the curvature kappa is defined and set > s->f[face->d].v = alpha*sigma*kappa*solid_fraction > where s = GFS_STATE(face->cell) (or neighbor cells) and f contains temporary face variables un and v. > > Then in gfs_correct_normal_velocities, GFS_SOURCE_TENSION_GENERIC (s)->c (which I believe is the volume fraction field) is passed as the effective pressure, the pressure gradient dp is calculated, and the normal velocity of faces (which are stored in s->f[face->d].un) are incremented by + or - dp*dt. > > It appears that the weight of the normal velocity is stored in f[d].v and to get the right correction due to surface tension, the normal velocity at a face should be changed by f[d].un*f[d].v, but I don't see this happen here. More importantly, the very next step in mac_projection is gfs_poisson_coefficients (domain, alpha, TRUE, TRUE, TRUE), which resets f[d].v for all faces and directions to 0, so it looks to me like the values of f[d].v are never used. > > Does anyone know what I'm missing here? > > Thanks, > Frederik > ------------------------------------------------------------------------------ > _______________________________________________ > Gfs-devel mailing list > Gfs...@li... > https://lists.sourceforge.net/lists/listinfo/gfs-devel |
From: Vladimir K. <vi...@cf...> - 2014-10-31 00:24:23
|
a fix has been found: in variable_poisson_event, we need to reduce the units of the RHS (aka div) by 2 with the reference to the variable to be solved for: gfs_function_set_units (p.f, v->units - 2.); The new call comes between DivData p = { GFS_VARIABLE_FUNCTION (event)->f, div }; --> new call to gfs_function_set_units (p.f, v->units - 2.); and gfs_domain_traverse_leaves (domain, (FttCellTraverseFunc) rescale_div, &p); Cheers, Vladimir. On 10/30/2014 11:13 AM, Vladimir Kolobov wrote: > Dear Gerris Developers, > > There is an issue with GfsVariablePoisson with non-unity domain scaling. > > If L is set to something different from 1 in PhysicalParams, the > solutions of the Poisson equations in the attached script differ by a > factor of L*L. > > This is because gfs_function_value in calculating RHS is used in > GfsVariablePoisson which returns adimensional_value. > > If one sets > > VariablePoisson { istep = 1 } Phi Div*0.1*0.1 > > the solutions coincide. > > This just a note to those using GfsVariablePoisson that the divergence > (RHS of the Poisson equation) needs to be scaled with L*L. > > Cheers, > > Vladimir > > ==================================== > > 1 0 GfsPoisson GfsBox GfsGEdge {} { > Time { iend = 10 } > > Refine 5 > > PhysicalParams { L = 0.1 } > > Init {} { > Div = { > return 1.; > } > } > > VariablePoisson { istep = 1 } Phi Div > > OutputSimulation { start = end } end-SOLVER.gfs > } > GfsBox { > left = Boundary { BcDirichlet P 0. BcDirichlet Phi 0. } > right = Boundary { BcDirichlet P 0. BcDirichlet Phi 0. } > top = Boundary { BcNeumann P 0. BcNeumann Phi 0. } > bottom = Boundary { BcNeumann P 0. BcNeumann Phi 0. } > } > > ------------------------------------------------------------------------------ > _______________________________________________ > Gfs-devel mailing list > Gfs...@li... > https://lists.sourceforge.net/lists/listinfo/gfs-devel > > |