Inconsistent field ordering in PDRMesh
Relies on the iteration of the IOobjectList being identical to that of names(), which is not guaranteed at all. If these are not identical, the correspondence of naming will be incorrect.
Site will likely be offline for maintenance 27/28 March - more details soon
Relies on the iteration of the IOobjectList being identical to that of names(), which is not guaranteed at all. If these are not identical, the correspondence of naming will be incorrect.
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Link issues together to show that they're related. Learn more.
mentioned in commit 163add5f11b7e38ce93f3e76987d8b64be7afd43
Can leave this BUG unpatched in earlier versions. It was provoked by some intermediate changes that (as a side-effect) caused the object names to be sorted. The regular iteration order thus did not correspond.
Nonetheless, the changes made (always dealing in sorted order) improve future robustness.
closed