Open jhabriel opened 2 years ago
Thanks. This is likely related to an update to tagging of physical lines and poitns in PorePy some time ago. I will try to look into it, but it take at least a few days.
@jhabriel Did you end up modifying the files here, or using an older version of PorePy?
@keileg: I did not manage to make this work, and I ended up using an older version of PorePy to make the 3D Geiger work. For the record, I also tried to pass constraints
as an optional parameter for meshing the 3D geometry directly from the CSV. Unfortunately, this does not work either; PorePy complains when constraints are specified on the boundaries.
Bottom line, the only feasible solutions are: (1) specify the boundary lines and points in the new geo files manually, or (2) update the tags of the old geo files so it is compatible with the newest version of PorePy.
Due to limited time, I did not pursue any of the above solutions.
In particular, loading the .geo files corresponding to the 3D benchmark, case 2, does not generate 1D (and 0D) fractures and mortars. This might be due to changes in the way physical lines and points are tagged/accessed.