NoiseModelling icon indicating copy to clipboard operation
NoiseModelling copied to clipboard

Errors in calculation depending on the separation between receivers

Open IsotoCedex opened this issue 1 year ago • 4 comments

NoiseModelling version 4.0.5

Describe the bug Calculating large scale model (Large number of sources, receivers, buildings). Accurate DEM (25x25 m)

When the distance between receivers is less than 150 m, a calculation error occurs, which is repeated in several phases of the process.

When calculation processs finishes, the Lday_geom, levening_geom... tables are empty.

If the distance between receivers is greater than 150 m, calculate carefully.

I have tried uninstalling and installing NoiseModelling, and redoing from the beginning. The problem always repeats itself.

To Reproduce

Process file: Process.txt SourceData files: https://drive.google.com/file/d/1L9Xis8nylmkYW5ukrb7V0SGkto2JrHmL/view?usp=sharing

Geoserver log

See this errror "INSERT INTO LDAY_RESULT VALUES (? , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [22001-214] org.h2.jdbc.JdbcSQLDataException: Valor demasiado largo para la columna "HZ8000 NUMERIC(5, 2)": "CAST(-1155.2235037857104 AS DOUBLE PRECISION) (53)"

Attach geoserver log: geoserver - copia.log

IsotoCedex avatar Jan 18 '24 10:01 IsotoCedex

Hi,

There is an issue with the column type that can't store -1155.2235 dB

We could set a minimum value when storing levels or change the column type.

What emission value you set on your sound source ? (because there is only DEM in your files)

nicolas-f avatar Jan 18 '24 10:01 nicolas-f

Sorry.

Here is the correct ZIP file: https://drive.google.com/file/d/1JwSKRckz9PZm5GgxGi8hfSL50nR8kM3N/view?usp=sharing

I have verified that the following files exist:

image

Emission (lw_roads) seems to be right: image

IsotoCedex avatar Jan 18 '24 11:01 IsotoCedex

Any news?? ;)

IsotoCedex avatar Jan 23 '24 10:01 IsotoCedex

It should not crash with the last automated build:

https://github.com/Universite-Gustave-Eiffel/NoiseModelling/actions/runs/7624814011/artifacts/1188395116

But looking if it is an issue with such a large computation will take some time.

If you are using the geoserver based release you have to replace the noisemodelling jar file noisemodelling-jdbc and the groovy script Noise_level_from_source.groovy and Noise_level_from_traffic.groovy

nicolas-f avatar Jan 25 '24 10:01 nicolas-f