Particle Status Codes
Each particles carries its own status information during the simulation that describes whether it is moving through the filter or has reached its final position. The status also contains the information, why the particles reached a final state: if may have left the domain, or been captured by the filter material, or some error may have occurred.
When opening *.gpp particle files or .gpt trajectory files in GeoPy, the table below can be used to understand the particle status. When loading particles directly in GeoDict, the status is automatically converted.
Initial or intermediate status codes |
|
-1 |
Initialize velocity from .vap file |
0 |
Particle continues moving |
1 |
Particle collision point, particle continues moving |
Final status codes for unfiltered particles (8-16) |
|
8 |
Particle left domain through Z+ side (outlet) |
9 |
Particle left domain through Z- side (inlet) |
10 |
Particle hit end material ID |
11 |
Particle reached maximum displacement (AddiDict only) |
12 |
Time-out: particle continues moving in next batch interval |
13 |
Particle left domain through X+ side (AddiDict only) |
14 |
Particle left domain through X- side (AddiDict only) |
15 |
Particle left domain through Y+ side (AddiDict only) |
16 |
Particle left domain through Y- side (AddiDict only) |
Final status codes for filtered particles (32-37) |
|
32 |
Particle trapped by adhesion / Hamaker model |
33 |
Status code reserved for Collision UDFs |
34 |
Particle trapped by Sieving model |
35 |
Particle trapped by Caught On First Touch model |
36 |
Particle trapped while passing through porous layers / Pass-Through model |
37 |
Particle trapped by adsorption (AddiDict only) |
Error codes |
|
40 |
Error: initial particle position overlaps with structure |
41 |
Error: particle stalled by too many bounces on same position |
42 |
Error: particle stalled by continuously having time steps size zero |
