[immortality]

Hi Bruno,thanks
I used parallel run,now I have to reconstruct specified times?(the equivalent times in two sequential times) and then how use that command?!

[wyldckat]

Hi Ehsan,

Originally Posted by immortality

I used parallel run,now I have to reconstruct specified times?(the equivalent times in two sequential times) and then how use that command?!

Sorry, I don't understand what you are specifically asking about
Please provide more details.

Best regards,
Bruno

[immortality]

Bruno I don't know how to use the command when the fields are decomposed in processor folders! I have been mixed up!

[wyldckat]

Why don't you use the reconstructPar with the "-time" option?
And why don't you manually copy only the fields that you want to look at, form one time folder to the other?

[immortality]

I thought it have to be done through -parallel option.
do you know how can get rid of those red cells and have a more smooth result?
they are both in p field and subtract field.

[wyldckat]

A few advices:

• Whenever the results look suspicious, check if the values in parallel are identical to the reconstructed ones. It's always possible that some point/face/cell numbering isn't synced in parallel, but it should be when reconstructed.
• Whenever there is such a large difference of values between contiguous cells, that might indicate that you do not have enough mesh resolution for describing properly what happened at the location of the cell with the largest differences in values.
• A form of smoothing is the "vertex/point" representation.
• The results are what they are. Many times we have to live with how imperfect they are, because better results are not achievable in the time frame for the project at hand.
• Any excessive form of post-processing will only reduce the validity of your results, unless it was previously proven that for your case, the interpolation/smoothing process has a minimal error in comparison.
• edit: You can use Gimp for reducing the size and quality of images before uploading them.

[immortality]

may it be a characrestic of rhoCentralFoam?
its an image from near,are cells few in your opinion?
I didn't grasp totally about writePrecision and its role,I have set it to 16,but these results existed when it was only 6,and I don't think time step be responsible for that because it was in lower time steps too(maxCo=.1 till maxCo=.2 that I've tried)

[wyldckat]

From the looks of it and from what I can remember from this test case...

1. From the previous pictures, it looked like there was only one big red cell surrounded by green cells. That's why I wrote my other comment on insufficient resolution.
2. But looking at this zoomed in image and remembering the case, what we're seeing is the effect of pressure shock-waves crossing each other's paths. Therefore, more refinement will probably only mean that you'll see with more resolution this crossing of the shock-waves.
   • You could use the trick that is explained in the very first tutorial of the User Guide, namely to use a time step from X seconds before and mapping its fields into a simulation with 2x the mesh resolution, to see how much it would change with the higher resolution.
3. If you are using a precision of 16 digits, it would be preferable to use "binary" coding instead of "ascii". I say this because it's 16 to 18 bytes per value in "ascii", versus 8 bytes in "binary", therefore your files could be around 50% in size of what they currently are.

[immortality]

yes you are true,they are the points that originated oblique shocks hit together and make pressure to be higher than neighbor cells.It was odd for me that had forgotten about it and ignored this problem,thank you for saving me