Example 65 explains the procedure to follow in the case adaptive meshing has been used to evaluate the flow field. Indeed, two limitations of the mixing module forbid to use meshes whom some parts have been sub-divided. Firstly, in case of transient simulations, the mesh of the flow domain can/will change with time: new elements and new nodes are created/deleted. Secondly, as the mesh is refined locally, non-conformity appears: sub-divided elements are adjacent to non sub-divided elements. As the tracking of material points does not allow such cases, we propose the following procedure:
In Polydata, during the definition of the flow task, we ask for the output of CSV results files.
In Polyflow, we evaluate the transient flow, using adaptive meshing; at each time step, a CSV file is generated that contains the current flow field.
In Polydata, we perform a conversion of the CSV files into new Polyflow results files onto a new uniformly refined mesh (the mesh of the flow domain will remain constant in time); at the end of this step, we have a new mesh and a set of res files (1 res file per time step) compatible with this new mesh.
In Polydata, we define a mixing task, based on the new mesh and the new results files.
In Polyflow, we compute the trajectories of a set of material points.
In Polystat, we perform a statistical analysis on these trajectories.