Code breaks while controller sets up the output for post processing a fracture.
The problem is an inconsistency at postprocess_fracture.py:get_fracture_variable()
There's a confusion if we're iterating over indices of a list (type = int), or the elements of said list (type = Fracture).
This bug appears to have originated at commits
dea70e1
3ed69f3
65fc63f
They seem to have left the migration to "loading meshes byAddress" incomplete, i.e. may assume that a mesh property of a fracture may be an int instead of a reference to a CartesianMesh.
I'll submit a pull request that fixes this by, mainly, reverting those commits.
Description
Code breaks while controller sets up the output for post processing a fracture.
The problem is an inconsistency at
postprocess_fracture.py:get_fracture_variable()int), or the elements of said list (type =Fracture).This bug appears to have originated at commits
They seem to have left the migration to "loading meshes byAddress" incomplete, i.e. may assume that a
meshproperty of a fracture may be anintinstead of a reference to aCartesianMesh.I'll submit a pull request that fixes this by, mainly, reverting those commits.