BC's details unavailable from imported msh file
 

Dear chandra and zxaar

as per the advise received from you, In Gambit I had imported *.msh file from fluent *.cas file. But the boundary conditions details are not available in the *.dbs file? how will I get the boundary condition details in the dbs file so that I can edit the bc's and export new msh file for fluent run.

Re: BC's details unavailable from imported msh fil
 

when you extract mesh from .cas file as i mentioned the boundary conditions are available.

Re: BC's details unavailable from imported msh fil
 

I get the following error: is this a very serious error, please help.

Starting /pkgs/gambit2.0/Fluent.Inc/utility/fe2ram4.3/ultra/fe2ram.4.3.2 -m1e-06 -d3 -tRAMPANT -oFIDAP7 /home/ashish/3dmodel.cas.tar.cas

RAMPANT file to FIDAP7 file

Read 1994678 nodes, 1868000 elements, 14 groups. 1868000 hex elements

merged 0 nodes (1994678 remain)ERROR() error code = 101077

WHERE = -?- ERROR() error code = 101077

WHERE = -?-

Thanks a lot.

Re: BC's details unavailable from imported msh fil
 

why is the model compressed, uncompress it and see if it changes anything. Anyway it should have already worked i guess.

Re: BC's details unavailable from imported msh fil
 

I will try and get back.

Re: BC's details unavailable from imported msh fil
 

Hello zxaar,

the boundary conditions are available in the mesh file, but when i import the mesh in gambit i do not see the boundary conditions details, can you please help.

thanks.

Re: BC's details unavailable from imported msh fil
 

Hello zxaar

one more thing which i found was when i read the msh file thus obtained as above and read in fluent i find that the zone id's have changed and when i solve i get the Floating Point Exception (Underflow) Error. this was not the case with the original fluent case file. can you please help.

thanks,

ashish.

Re: BC's details unavailable from imported msh fil
 

if you use the latest version of gambit, you will see it preserves the boundary condition names as they were.

Re: BC's details unavailable from imported msh fil
 

use journal file to describe the boundary conditions etc, when you describe BCs by TUI you can just use their name to specify the BC, you do not need the zoneid, let it change.

Re: BC's details unavailable from imported msh fil
 

i specified the bc's in gambit and exportet the mesh, but while solving in fluent i get the error. where as the original case file does not give any error.

please help.

regards,

ashish.

Re: BC's details unavailable from imported msh fil
 

you haven't told what error it gives.

Re: BC's details unavailable from imported msh fil
 

Hello zxaar

I though that you have read my earlier message in this thread:

"one more thing which i found was when i read the msh file thus obtained as above and read in fluent i find that the zone id's have changed and when i solve i get the Floating Point Exception (Underflow) Error. this was not the case with the original fluent case file. can you please help."

thanks,

ashish.

Re: BC's details unavailable from imported msh fil
 

i also thought you have read my other message, See when you read the mesh, and if you do not want to describe them again and again manually. describe them with the help of journal file. If you do this way, you do not need to worry about zoneid, you can specify by their names. So create a journal file to do the work for you. I will put and example here, or on wikipedia in FAQ section today.

Re: BC's details unavailable from imported msh fil
 

Here is an example of journal:

define boundary-conditions velocity-inlet inlet n n y y n 10 y n y 0 0.001 define boundary-conditions pressure-outlet outlet n 101325 n n y n y 2 0.001 n define boundary-conditions fluid rotzone n n n n n y 0 0 0 -50.00 0 0 0 0 0 1 n n n

put these things into a journal and read the journal, you can note that i have not used the zoneid but the zone name, inlet and outlet,

Re: BC's details unavailable from imported msh fil
 

thanks for your journal. i will use this and get back.

regards,

ashish.

Re: BC's details unavailable from imported msh fil
 

you might have to create your own suitable to ur case, its easy to do it.