I have a simulation result from multiphase simulations where I would like to have stream tracers defined from the input plane to the output plane. I tried to create a stream tracer with custome data source i.e. the input plane but i am not able to get the proper intended results. Ideally i would like to have the liquid recirculation zones behind the bubbles and flow structures being distorted due to passage of bubbles. Please find attached the screenshots.
If I understand correctly, you want to see streamlines in the whole volume of your dataset. The stream filter will display only streamlines that pass through the source.
So you can try with the ‘common’ stream filter and use a line as source (default source), and modify the line as needed (e.g. click on ‘X’ to have a line along X axis)
Second possibility, you can try with a subset of your Point data as custom source of the stream filter. See this state file as example: streamlines.pvsm (464.3 KB)
(Note that I have an error reported when executing this state file, but I don’t know why as computation ends correclty)
Thanks for the info. Thats exactly what I needed. I tried loading your state file and I do see the streamlines all across the domain. Is there a way to control the density of these streamlines. Normally in the case of point source or Line source we can control the seed points but here I don’t find that option.
Also, regarding extracting the subset of surface should all of the domain needs to be selected as a subset ? And which dataset needs to be taken as the source of custom filter ? I tried it from the scratch and then paraview hangs. If i load your statefile it works perfectly fine.
The main logic here is in the extract filter. It creates a subgrid by extracting 1 point over X. This X is the sample rate you can set in the advanced properties.
The output of this extract filter is the seed source of the streamlines: each point of this subset will be used as start point of a streamline.
So, density of streamline will increase with number of points. But too many points will lead ParaView to hang, because of the computation size.
