Hi @Juan
So I tried using the script you mentioned, but I get an error when I input my MSH file (I also double checked that I can actually run the example in the link you sent, just to make sure I’m running this right):
The furthest back that I could trace the error from the functions called is in the
run() function of
test_convert.py (line 384). The way I understand it, it seems like
yaml_map is populated in line 391 with the new interface
‘N_junctions_P_junctions’, which is then assigned to
interface_names (in line 422), which is then passed into
get_interface_map (line 424-425), which is the function where the error occurs (line 258). Since
‘N_junctions’ and
‘P_junctions’ are my only volume physical groups, I think it makes sense that this interface was created, but I’m not sure how to go about dealing with this.
Do you know why this is happening?
Also, since last time, I change my Physical Groups a bit, which now are (from .geo file):
Physical Surface(“Top”) = {27, 51, 74, 97, . . .};
Physical Surface(“Bottom”) = {1};
Physical Volume(“N_junctions”) = {1, 38};
Physical Volume(“P_junctions”) = {2, 3, 4, 5, . . .};
Using the following picture as reference, ‘P_junctions’ are the cylinder volumes, ‘N_junctions’ are the rest of the volumes, ‘Bottom’ is the blue plane, and ‘Top’ are the orange planes which are made up of the circles and the plane around them.
When using DevSim, I also tried having different regions for each of the volume Physical Groups, but ran into another problem. I made ‘Bottom’ and ‘Top’ to be contacts in the region created by the ‘N_junctions’, but I get an error that many of the coordinates in the ‘Top’ contact are not on that region. I get a similar error when I try to make the contact using the region created by the ‘P_junctions’.
Do you know if this is related to why I’m getting the error when I try to use test_convert.py? Or is this a completely new problem, and if so, do you know how I can fix it?