Known problems with LASAT

Problem 2020-07-31
Betroffen GeoMapper / GeoOsm up to 1.0.0

Title

Access to OSM server
Description

The interface to the tile server of OpenStreetMap has changed in the first quarter of 2020. No tiles can be downloaded with the old interface.

Workaround -
Resolved 2020-01-28 (GeoOsm 1.0.2)

Problem 2020-07-08
Applies to LTdefcheck up to 1.3.5

Title

LTool DefCheck with meteo.def without time series
Description

If no time series is defined in meteo.def, the LASAT tool DefCheck hangs on checking the project.

Workaround Insert a short dummy time series, e.g.
! T1 T2 dummy
Z -inf +inf 0

Resolved 2020-07-31 (LTdefcheck 1.3.6)


Resolved problems

Problem 2018-10-22
Applies to Lasat up to 3.4.13

Title

Seasonal mixing layer height
Description

In case an absolute reference date is given in param.def and the boundary layer version 5.2 or 5.3 with the Coriolis parameter 1.1e-4 1/s is given in meteo.def, LASAT applies for a time series calculation and the stability classes Klug/Manier IV and V (unstable) according to the standard VDI 3783/8 (2017) a mixing layer height that depends on the month of the year. However, LASAT only uses the month of the reference date, without any further update in course of the time series. Tests have shown that this error has only little effect on the result.

Workaround -
Resolved 2019-01-08 (3.4.16)

Problem 2018-10-04
Applies to Lasat up to 3.4.13

Title

Change of source parameters in combination with PLURIS
Description

The plume rise calculation with PLURIS (flag PLURIS) is internally carried out at the beginning of a new interval of the meteorological time series. This is usually sufficient as also source parameters do usually not change at smaller intervals (both being defined as hourly averages). However, if source parameters required for the plume rise calculation change before meteorological data do, this change is not taken into account.

Workaround Specify meteorology on time intervals at least as short as used for the source parameters.
Resolved 2019-01-08 (3.4.16)

Problem 2017-06-27
Applies to Lopxtr up to 1.1.35

Title

Result evaluation for indices exceeding 9999
Description

The tool Lopxtr reads LASAT concentration files and checks the consistency of day indices in the file name and number of files. Index i2 of the last file minus index i1 of the first file plus one is the number of files, n = i2 - i1 + 1. A problem occurs if the index changes from 9999 to 10000 (does not occur in typical situations): On internal sorting, the file name with index 10000 is the first and the one with index 9999 the last. This gives n = 9999 - 10000 + 1 = 0 and the tool notes that something is wrong and aborts with an error message.

Workaround -
Resolved 2017-06-27 (Lopxtr 1.1.36)

Problem 2017-05-15
Applies to Lasat 3.4.3

Title

Abort of a PLURIS calculation
Description PLURIS and the program aborts if it encounters an interval with invalid meteorology.
Workaround -
Resolved 2017-05-17, Lasat 3.4.5

Problem 2017-05-15
Applies to Lasat, Lprwnd, Lprprf 3.4.3

Title

Licence problems with Windows 10
Description Under certain conditions the licence is not encountered with Windows 10.
Workaround -
Resolved 2017-05-17, Lasat, Lprwnd, Lprprf 3.4.5

Problem 2017-05-15
Applies to GeoMapper 1.0

Title

Reading pre-defined nested grids
Description When reading pre-defined nested grids it is checked if the borders of two subsequent grids are separated by at least 2 grid cells, but AUSTAL2000 creates in certain cases grids with only one grid separation.
Workaround Adjustment of the grids
Resolved 2017-05-17, GeoMapper 1.1

1