[原创] Notice for GAMBIT AND POLYFLOW USERS

carljian

There is a serious error or conflict in instruction of POLYFLOW documentation at section: 7.2.1 Subdomains in GAMBIT.
As to this point, please also refer to GAMIBIT documentation at section: 4.2.1 Specify Boundary Types NOTE: section.
In fact, subdomain is a table name in data base; so long as the table(s) is (are) created by GAMBIT, it (they) can be read (retrieved) by POLYDATA with SQL(Structured Query Language) then show the result (a list) at a GUI. If indices are not specified at subdomains (tables) or the format of index is error, the warning will be appeared at GUI. Although you are allowed to keep going, POLYDATA will treat whole geometry as one subdomain (one table). That is a typical error according to transport phenomena.   
Please read and think carefully about instruction!
Carl Jiang

joli

In gambit, the name of subdomain and boundary must be number such as 1, 2.

hfang79

yes,for example,inlet1 or outlet2.

carljian

the correct format should be "inlet.1" or "outlet.2" with "." from IS of view,in which "inlet" and "outlet" could be column names under one table name.
And the numbers are attached after column names to form unique KEY in order to avoid conflict with other names. As soon as unique keys are made, software (POLYDATA or other software) will be able to read data storing in the columns with SQL and list column name such as "inlet.1" maping to "inlet 1" and "outlet.2" maping to "outlet 2" on GUI.Such procedure is called as conversion from GAMBIT file with ".neu" (something like that) extension to to other extension.
However,"instruction of POLYFLOW documentation at section: 7.2.1 Subdomains in GAMBIT" doesn't point out and " GAMIBIT documentation at section: 4.2.1 Specify Boundary Types NOTE:xxx " tells users correct format.The reason made so is the documentations were written by two different groups in that company. But it easily leads to a mistake for initial users. As a good programmer must tell users correct and clear documentation.
A few days ago I made such a mistake because of following POLYFLOW documentation.I used to ask for help here, but nobody has told me what could happen so far. Wish my comments could be useful for later users.
Thanks for two people  response at top columns.
  

carljian

In above case, table name must be one of them--- "Groups","Volumes" or "Faces".Mesh data are sored into columns named by you with number to form unique KEY for SQL selection at data base,using a command such as SELECT "column name.number" FROM "Groups", "Volumes" or "Faces" (one of them) then show column name (space) number on "conversion" GUI.
Such concepts are very useful for people who don't know IT well to find and solve the encountered problems.

guigui8888

楼上的兄台可否传个POLYFLOW或GAMBIT的例子或帮助。
小弟正在学习
谢谢