[Gfs-devel] Where are the keywords predication in input file stored ?

[HE, He CM [ME]]

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

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.