I started to do a simple test run, which passes the input check and then immediately gives a “Segmentation Violation” dialog and stops the calculation. What does this mean?
There are certain TNM object placements that will cause TNM to overflow. Because TNM performs many of its geometric calculations by drawing triangles along the source-receiver path, division by zero calculations are possible if the extensions of the objects are pointing at receiver locations. Overflows also are more likely to occur if there is a high density of path-oriented objects (e.g., terrain lines, building rows), such as two terrain lines too close together. When deciding how close your terrain lines should be, always take line-of-sight into account. For example, cases involving noise barriers may have different elevations in front of and behind the barrier; if not modeled properly, the highest vehicle source (at a height of 3.66 m [12 ft.]) could be inadvertently blocked by the barrier or exposed to the receiver. In general, use good engineering judgment to simplify your geometry. If TNM outputs a segmentation violation message, don’t click OK right away; make a note of which r
Related Questions
- I started to do a simple test run, which passes the input check and then immediately gives a "Segmentation Violation" dialog and stops the calculation. What does this mean?
- Is there a simple home test or mold detection device that can actually detect mold immediately?
- How do I write and run a simple JUnit test?
