You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- center points enhanced to select particle ids based on the particles located in box, sphere and cylinder
- readme.md modified
- DEMsystem is modified to pass id
Copy file name to clipboardExpand all lines: src/PostprocessData/readme.md
+19-7Lines changed: 19 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,14 @@ The `PostprocessData` module in phasicFlow provides powerful tools for analyzing
5
5
- in-simulation: this is postprocessing that is active during simulation. When running a solver, it allows for real-time data analysis and adjustments based on the simulation's current state. See below to see how you can activate in-simulation postprocessing.
6
6
- post-simulation: this is postprocessing that is done after the simulation is completed. It allows for detailed analysis of the simulation results, including data extraction and visualization based on the results that are stored in time-folders. If you want to use post-simulation, you need to run utility `postprocessPhasicFlow` in terminal (in the simulation case setup folder) to run the postprocessing. This utility reads the `postprocessDataDict` file and performs the specified operations on the simulation data.
in-simulation postprocessing is not implemented for MPI execution. For post-simulation postprocessing, you can use the `postprocessPhasicFlow` utility without MPI, even though the actual simulation has been done using MPI.
13
+
14
+
</div>
15
+
8
16
## 1. Overview
9
17
10
18
Postprocessing in phasicFlow allows you to:
@@ -118,12 +126,17 @@ Regions define where in the domain the postprocessing operations are applied:
118
126
119
127
| Region Type | Description | Required Parameters | Compatible with |
| `line` | Spheres along a line with specified radius | `p1`, `p2`, `nSpheres`, `radius` | bulk |
124
-
| `centerPoints` | Specific particles selected by ID | `ids` | individual |
125
-
126
-
## 6. Processing Operations
129
+
| `sphere` | A spherical region | `radius`, `center` defined in `sphereInfo` dict| bulk |
130
+
| `multipleSpheres` | Multiple spherical regions | `centers`, `radii` defined in `multiplSpheresInfo` dict | bulk |
131
+
| `line` | Spheres along a line with specified radius | `p1`, `p2`, `nSpheres`, `radius` defined in `lineInfo` dict| bulk |
132
+
| `box`| A cuboid region | `min`, `max` defined in `boxInfo` dict | bulk |
133
+
| `centerPoints`* | Specific particles selected by ID | `ids` | individual |
134
+
| `centerPoints`* | Specific particles selected by center points located in a box | `boxInfo` | individual |
135
+
| `centerPoints`* | Specific particles selected by center points located in a sphere | `sphereInfo` | individual |
136
+
| `centerPoints`* | Specific particles selected by center points located in a cylinder | `cylinderInfo` | individual |
137
+
| <td colspan="4">\* Particles selection is done when simulation reaches the time that is specified by `startTime` of the post-process component and this selection remains intact up to the end of simulation. This is very good for particle tracking purposes or when you want to analyze specific particles behavior over time.</td> |
138
+
139
+
## 6. Processing Operations for Bulk Properties
127
140
128
141
Within each processing region of type `bulk`, you can define multiple operations to be performed:
0 commit comments