Reading ansys fluent case and data with fluent 6.3

artemiss1984 · November 17, 2017, 03:55

I have a question. Any answer is appreciated.

Is it really possible to read an Ansys fluent case and data files in fluent 6.3.26?
I have done it for some cases but receive error in other cases.

Thanks

LuckyTran · November 17, 2017, 11:11

I think v16 or v17 was when they switched over to a new a slightly different syntax.

What changed was they added the infamous (object-oriented) brackets { } around variables and code sections that allows the reader/interpreter to skip entire sections quickly. This seems to be a common trend, heck even solidworks did the same thing in 2016 or 2017.

November 17, 2017, 03:55	Reading ansys fluent case and data with fluent 6.3	#1
artemiss1984 Member Join Date: Apr 2009 Posts: 38 Rep Power: 17	I have a question. Any answer is appreciated. Is it really possible to read an Ansys fluent case and data files in fluent 6.3.26? I have done it for some cases but receive error in other cases. Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
decomposePar problem: Cell 0contains face labels out of range	vaina74	OpenFOAM Pre-Processing	37	July 20, 2020 05:38
A CFX-POST error (ver 14.5.7)	wangyflp88	CFX	2	July 22, 2017 00:17
[Commercial meshers] Problem converting fluent mesh	vinz	OpenFOAM Meshing & Mesh Conversion	28	October 12, 2015 06:37
The fluent stopped and errors with "Emergency: received SIGHUP signal"	yuyuxuan	FLUENT	0	December 3, 2013 22:56
Possible Bug in pimpleFoam (or createPatch) (or fluent3DMeshToFoam)	cfdonline2mohsen	OpenFOAM	3	October 21, 2013 09:28

November 17, 2017, 11:11		#2
LuckyTran Senior Member Lucky Join Date: Apr 2011 Location: Orlando, FL USA Posts: 5,674 Rep Power: 65	I think v16 or v17 was when they switched over to a new a slightly different syntax. What changed was they added the infamous (object-oriented) brackets { } around variables and code sections that allows the reader/interpreter to skip entire sections quickly. This seems to be a common trend, heck even solidworks did the same thing in 2016 or 2017.