okey, but this is not a default feature of paraview, this is a python script you made yourself,no?

Yes .. more or less. With some basic commands copied from trace.

(basically commands obtained through ``from Paraview.simple import *``)

A bug-fixes release: https://www.kitware.com/paraview-5-13-3-release-notes/

Hi, I'm a big noob, what do these two scales represent? https://cdn.discordapp.com/attachments/616621476853841930/1359912207323758873/IMG_1793.jpg?ex=67f93470&is=67f7e2f0&hm=6b2a7ad327afb1391a9d410e7244fda04b867f853ffc574acca089a3f71544d6& https://cdn.discordapp.com/attachments/616621476853841930/1359912208183726311/IMG_1794.jpg?ex=67f93470&is=67f7e2f0&hm=6a4f30ae7076fb866027c716de442b3c2ff29c1521eeda8fb51058039469b293&

Velocity magnitude and pressure fields 🤔

Thanks, but why is there no low pressure in the back?

At the trailing edge of the airfoil?

yeah ?

That is the correct behaviour for an airfoil that isn't stalled. The pressure at the trailing edge recovers to approximately the same as at the leading edge as the flow decelerates

Ahhh ok thanks you!

Hey, quick question: I think I knew how to do it but forgot. I've got the thermal gradient G as a scalar from my simulations and I would like to extract the components in x, y and z (Gx, Gy, Gz) to compare with the temperature gradient calculated from the temperature field with the Gradient filter, how to do this ?

Do you see them listed as independent scalars, eg if you use Calculator?

Nope, I just have one scalar for G as calculated during the simulation, without them listed as Gx, Gy and Gz into the scalars list

Why is your gradient a scalar? It should be different along different directions. How do you calculate this quantity G?

To summarise, to save storage, I only export the magnitude of the gradient and not the components I'm simulating welding, and to analyse the solidification history, I need to store the thermal gradient at the solidification front in the solidified. So in the liquid metal, I calculate the thermal gradient following the equation attached, and in the solidified region it is a frozen value, hence the fact that it is a scalar. https://cdn.discordapp.com/attachments/616621476853841930/1364523868001140867/image.png?ex=6809fb61&is=6808a9e1&hm=fa42c0e8f676c9eb24f0d4db2134c762755cd35eff5acc5a5cc6617737858161&

That being said, I can go back to the simulation and export all components to compare with the gradient calculated with the paraview filter. I just thought there would be a way to extract the components from the scalar

Yeah so that's just the magnitude. When you did that calculation you lost information on direction. You could either export the components, or export the G unit vector G/|G|.

Either of those will let you reconstruct the Gradient vector field.

Yeah that makes sense actually, thanks for the help 🙂

Just had a quick check up on a previous simulation where I exported more information; it looks like I can fairly use Gy calculated from the temperature field by paraview https://cdn.discordapp.com/attachments/616621476853841930/1364532014744604682/image.png?ex=680a02f8&is=6808b178&hm=a62fb40bda9bcd1a019365c54822de34cce7af18da87019923e35aa65830dec9&

Are you comparing the results of gradient calculation in paraview vs gradient calculation in openfoam?

That'll be 99.99% equal if you use cell data. Point data will introduce interpolation related differences and the more correct values (closer to satisfying governing equations) will be openfoam ones.

I used Fluent for my simulations, I don't know how different it may be from openfoam But I used point data and not cell data for the comparison

I created a cell zone that I can see that exists when i run checkMesh, but in paraview even when i turn on 'read zones' i dont see it listed. I am missing something? it should appear in 'mesh region' section, no?

It looks like it doesn't directly appear in mesh regions, but if you use the extract block filter you should see it

thanks!

@François Mazen (Kitware) worth to make a paraview issue about this?

Yes, definitely! Feel free to tag me in the issue report: https://gitlab.kitware.com/paraview/paraview/-/issues/new