When I tried to calculate a contour of sound levels, NMPlot outputs an “invalid floating point error” and then halts contour calculations. What is causing this?
• In Version 1.1: I took care of the “Out of Memory” problem, but now when I run NMPlot, I receive a FATAL ERROR message about the file format created by Noisemap not being the one expected by NMPlot. I had already downloaded NMPLOTX.EXE Version 3.06, so I don’t think that’s the problem. Is this something fixed in Version 2.0?
Related Questions
- When I tried to calculate a contour of sound levels, NMPlot outputs an "invalid floating point error" and then halts contour calculations. What is causing this?
- Im using Version 1.0b to calculate contours but NMPlot says that the contour settings were either too high or too low. What does that mean?
- How does Glaunach calculate valve unsilenced sound power levels ?