Opened 15 years ago
Last modified 13 years ago
#345 new defect
STS boundary condition does not work with parallel ANUGA
Reported by: | ole | Owned by: | leharne |
---|---|---|---|
Priority: | normal | Milestone: | ANUGA maintenance |
Component: | Functionality and features | Version: | |
Severity: | normal | Keywords: | parallel boundary sts |
Cc: | leharne.fountain@… |
Description
It appears that setting a File_boundary using an STS boundary file does not work when ANUGA is run in parallel.
I am guessing at the following reason: The STS file is first used to create the mesh. When the file boundary is built for a subdomain indices of edges are taken to refer to the global ordering of edges along the boundary.
For this to work with parallel ANUGA there has to be some mapping from the local indices of the sub domain boundary to the global ordering used by the STS file.
This could even be achieved by checking the x, y coordinates of each edge midpoint whet the file boundary object is being built.