Internal Boundary Condition Mis-“listed” as External

[Anonymous]

I cleaned up files and started a new project. Everything about the model scenario is imported into the new project, terrain rebuilt. Now when I try running the model it throws the following error for all of my internal boundary conditions.

Boundary Condition Line ‘SVF_south’ appears to be an Internal boundary condition for 2D Flow Area ‘Area2D’ but is listed as External.. If this BC Line is intended to be External, please move it outside the boundary.

Is this some kind of bug? I do not see where to “list” the BCs as internal. Any Suggestions? Maybe I just need to wiggle the end of each BC a little.

[Scott Miller]

Wiggling the ends worked… but it feels like a hack.

[Anonymous]

Maybe by importing all the features they don’t automatically get registered internally as features as part of a plan. By moving them slightly you probably forced HECRAS to realise they are now new features in the model.

[Anonymous]

This appears to happen if you have re enforced break lines or made computation point changes in the mesh. In Ras mapper–>Geometries–>Boundary Conditions–>Right Click–Edit Geometry (Beta). Then right click and stop editing, save.

This seems to reset the boundary into the mesh (without moving/wiggling any ends). You should see the red internal boundary shapes again. (I’m using Version 5.0.5).

[Lonnie A]

I’ve relayed this to HEC and believe it’s been fixed in v506…when that comes out I’m not certain. Usually I just have to move one boundary end point slightly for it to recognize the proper location. This is the same fix I use often for when I get a odd non-descript fortran error of red text right at the start of a run.

[Author]

Posts