! LASPORT 2.3 update information

Additional documentation of components of LASPORT are available to LASPORT users on demand.

Frequently asked questions

1


Known problems

Problem2019-09-06
Applies to Lasport 2.3 to 2.3.10

Title

Dispersion calculation only for nvPN
Description

If a dispersion calculation is carried out only for nvPN (number of non-volatile UFP), the applied quantity per simulation particle in LASAT is set too high and thus too few simulation particles are used (clearly visible in the results).

Workaround Use an additional substance.
Resolved-

Problem2019-09-07
Applies to Lasport up to 2.3.10

Title

Import of emission indices from a journal evaluation
Description

On import of emission indices into a project from a journal evaluation, the values are rounded to 1 microgram. This is reasonable for all standard trace substances because the values are much higher. But in case of a user-defined substance with much smaller values, this issue must be considered.

Workaround Copy values by hand from file LspEmis.log to file _emission.csv.
Resolved-

Resolved problems

Problem 2019-06-04
Applies to Lasport 2.3 to 2.3.10

Title

Using scaled maps from GeoMapper
Description

If scaled maps from the LASAT tool GeoMapper are applied and if the LASPORT project uses a reference point, then the coordinate values are not properly displayed because internally the y-value of the reference point is applied as x-value. This can be seen directly from the x/y-values which are displayed in the lower right corner of the map in menu Object locations. Correspondingly, coordinate values imported from the map to the object definitions are not correct.

Workaround -
Resolved 2019-06-04 (patch 2.3.10)

Problem 2019-01-22
Applies to Lasport up to 2.3.7

Title

Monitor calculation for a movement journal without taxiing times
Description

If no taxiing times are specified in the movement journal, LASPORT determines the taxiing time as stated in the program description from the given average taxiing speed (parameter IdleVelocity (m/s)). However, if the file _traffic.csv, as applied in scenario calculations, contains non-zero mean taxiing times per taxiway (sections [TABLE.IDLEWAYS.ARRIVAL.MINUTES] and [TABLE.IDLEWAYS.DEPARTURE.MINUTES]), these are used. In addition, the average taxiing speed cannot be modified in the user interface.

Workaround Set the mean taxiing times in _traffic.csv to 0 in order to apply the mean taxiing speed if no explicit taxiing times are provided in the journal. If required, change the mean taxiing speed directly in the project file _project.csv.
Resolved 2019-06-04 (patch 2.3.10)

Problem 2017-06-27
Applies to Lasport 2.2.0 to 2.2.12

Title

Result evaluation for May 2017
Description

The tool Lopxtr from the LASAT tool set reads the daily means and checks the consistency of day indices in the file name (starting with 1 for 1990-01-01) 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 during May 2017: The index changes from 9999 to 10000, but when internally 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.

In patch 2.2.13 (Lopxtr 1.1.31) the index evaluation has been improved.

Workaround -
Resolved 2017-06-27 (2.2.13, Lopxtr 1.1.31)

1