the problem of batch ( or .jou file)

liulangdefeng2222 · July 7, 2016, 01:18

Hi, everyone
When I used the .jou file to compute many cases which included dynamic meshes( just smoothing without remesh), using the same .jou file at different PC or at the same PC at different time would have different results. Sometimes, it will fail to deform mesh and emerge negative volume.
I want to know why? What I should change?
PS: OS: PC windows 7sp1; vesion: Ansys Fluent 17.1 & visual studio 2013
Hope some could help me.
Thanks

pakk · July 7, 2016, 05:33

Without seeing your journal file, this is very hard to answer. Technically, your .jou file could include some statement that depends on time or computer name. But that is unlikely...

And I don't understand your situation completely. You say you get different results, but do you mean you get different results on different computers/times for the same cases? Or different results on different computers/times for different cases?

It it is the last one (different cases give different results), then I don't see how your question is related to journal-files. If you have different cases, you get different results. Some cases converge, some diverge. Find out what went wrong, change the settings and re-run. The magic button 'always converge' does not exist yet.

liulangdefeng2222 · July 8, 2016, 04:16

I am sorry that I didn't state the problem clearly. It is the same case that use the same .jou file at different computers. Sometimes, it might result in negative meshes( mesh deformation failed). I don't know what's the reason.

liulangdefeng2222 · July 8, 2016, 04:19

Quote:

Originally Posted by pakk

Without seeing your journal file, this is very hard to answer. Technically, your .jou file could include some statement that depends on time or computer name. But that is unlikely...

And I don't understand your situation completely. You say you get different results, but do you mean you get different results on different computers/times for the same cases? Or different results on different computers/times for different cases?

It it is the last one (different cases give different results), then I don't see how your question is related to journal-files. If you have different cases, you get different results. Some cases converge, some diverge. Find out what went wrong, change the settings and re-run. The magic button 'always converge' does not exist yet.

I am sorry that I didn't state the problem clearly. It is the same case that use the same .jou file at different computers. Sometimes, it might result in negative meshes( mesh deformation failed). I don't know what's the reason.

pakk · July 8, 2016, 04:33

If the same case, with the same journal file, on the same computer, with all input the same, run on different times gives different results, and the journal file is not designed to do this, then this is very, very, very strange.

The most likely explanation for me is that you, accidentally, don't have the same case file, or have slightly different input.
I can not give a better guess without seeing your case/journal file/pc. (Don't see this as a request to send me your case-file, I won't have time to look at it...)

July 7, 2016, 01:18	the problem of batch ( or .jou file)	#1
liulangdefeng2222 New Member Xiaohua Li Join Date: Nov 2013 Posts: 15 Rep Power: 13	Hi, everyone When I used the .jou file to compute many cases which included dynamic meshes( just smoothing without remesh), using the same .jou file at different PC or at the same PC at different time would have different results. Sometimes, it will fail to deform mesh and emerge negative volume. I want to know why? What I should change? PS: OS: PC windows 7sp1; vesion: Ansys Fluent 17.1 & visual studio 2013 Hope some could help me. Thanks

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[OpenFOAM.org] Error creating ParaView-4.1.0 OpenFOAM 2.3.0	tlcoons	OpenFOAM Installation	13	April 20, 2016 18:34
centOS 5.6 : paraFoam not working	yossi	OpenFOAM Installation	2	October 9, 2013 02:41
OpenFOAM on MinGW crosscompiler hosted on Linux	allenzhao	OpenFOAM Installation	127	January 30, 2009 20:08
DxFoam reader update	hjasak	OpenFOAM Post-Processing	69	April 24, 2008 02:24
DecomposePar links against liblamso0 with OpenMPI	jens_klostermann	OpenFOAM Bugs	11	June 28, 2007 18:51

July 7, 2016, 05:33		#2
pakk Senior Member Join Date: Nov 2013 Posts: 1,965 Rep Power: 27	Without seeing your journal file, this is very hard to answer. Technically, your .jou file could include some statement that depends on time or computer name. But that is unlikely... And I don't understand your situation completely. You say you get different results, but do you mean you get different results on different computers/times for the same cases? Or different results on different computers/times for different cases? It it is the last one (different cases give different results), then I don't see how your question is related to journal-files. If you have different cases, you get different results. Some cases converge, some diverge. Find out what went wrong, change the settings and re-run. The magic button 'always converge' does not exist yet.

July 8, 2016, 04:16		#3
liulangdefeng2222 New Member Xiaohua Li Join Date: Nov 2013 Posts: 15 Rep Power: 13	I am sorry that I didn't state the problem clearly. It is the same case that use the same .jou file at different computers. Sometimes, it might result in negative meshes( mesh deformation failed). I don't know what's the reason.

July 8, 2016, 04:33		#5
pakk Senior Member Join Date: Nov 2013 Posts: 1,965 Rep Power: 27	If the same case, with the same journal file, on the same computer, with all input the same, run on different times gives different results, and the journal file is not designed to do this, then this is very, very, very strange. The most likely explanation for me is that you, accidentally, don't have the same case file, or have slightly different input. I can not give a better guess without seeing your case/journal file/pc. (Don't see this as a request to send me your case-file, I won't have time to look at it...)