Multiple CreateExclusion calls does not work
Bug #1205145 reported by
Dion Weatherley
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ESyS-Particle |
Fix Released
|
Critical
|
SteffenAbe | ||
Bug Description
In a model with multiple bonded interaction groups (pp_bonds1 and pp_bonds2) and a single friction interaction group (pp_friction), the following two exclusions were specified:
sim.CreateExclusion ("pp_bonds1"
sim.CreateExclusion ("pp_bonds2"
One would expect this would ensure that any pairs of particles bonded together via either of the two bonded interaction groups would not also undergo frictional interactions until the bond is broken.
Careful analysis of force FieldSaver output for the various interaction groups shows that only the second CreateExclusion(..) is invoked i.e. only particles bonded via pp_bonds2 interactions do not simultaneously undergo frictional interactions.
Revision history for this message
| Dion Weatherley (d-weatherley) wrote | #1 |
| Changed in esys-particle: | |
| status: | New → Fix Committed |
| assignee: | nobody → SteffenAbe (s-abe) |
| Changed in esys-particle: | |
| milestone: | none → 2.2.2 |
| Changed in esys-particle: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
A bug fix has been committed (trunk revision 1104). Many thanks to Steffen Abe for rapidly fixing this.
This is a critical bug affecting all versions of ESyS-Particle prior to rev. 1104. For affected versions of ESyS-Particle, simulation results will be wrong for models with multiple CreateExclusion(..) calls involving the same interaction group (e.g. pp_friction in the bug report).
WARNING: Users employing affected models should *immediately* upgrade to ESyS-Particle rev. 1104 or later.