! LASPORT 2.3 update information

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

Frequently asked questions


Known problems

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


Monitor calculation for a movement journal without taxiing times

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 -

Resolved problems

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


Result evaluation for May 2017

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)

Problem 2016-07-20
Applies to Lasport 2.2.0 to 2.2.11


Importing a day course evaluation of a movement journal into the current project

In the statistical evaluation of a movement journal, the day course is evaluated in the time zone of the journal and presented in tabular form. When importing this result into the current project, this table is taken without change, even if the project applies a time zone different from the journal.

Workaround Apply the same time zone in the movement journal and the project for evaluation and import of day courses.
Resolved 2016-07-20 (2.2.12; evaluation takes place in the time zone of the project)

Problem 2016-03-07
Applies to Lasport 2.2.0 to 2.2.10, monitor calculation with a journal containing a valid column AOD and no valid column GCD


Automatic internal supplement of the great circle distance (GCD)

If a movement journal does not contain a valid GCD (great circle distance) but column AOD (airport of destination) with valid entries, the GCD can be derived and used to select in case of several subprofiles of a given climb profile name the appropriate one. This supplement can be done explicitly in course of a journal extension in menu "Flight journal". The supplement requires the list of airports from the LASPORT database. The list is internally read if a journal is trated in menu "Flight journal". In a subsequent emission or dispersion calculation, this supplement is carried out automatically, too. However, if prior to the calculation the menu "Flight journal" has not been used, the list of airports has not been read and the supplement is not done. This can lead to differences in emission of a few percent for the segments TG, CI, and CF, for AzB profiles usually only group Large is affected.

Workaround Either explicitly supplement the GCD into the journal or, after supplementing the journal, restart the program before carrying out an emission or dispersion calculation.
Resolved 2016-03-07 (2.2.11; generally no automatic internal supplement of the GCD is carried out, but in case of doubts the sub-profile with the second-smallest GCD is applied).

Problem 2015-11-05
Applies to Lasport 2.2.0 to 2.2.10


Selection of concentration files in menu "Concentrations"

In the selection boxes, "Uncertainty" can be selected for percentiles, but such file does not exist (LASAT does not calculate uncertainties of percentiles). For nested grids, the file name of a concentration time series is not created correctly by the selection boxes (with grid index which in fact is not part of the file name).

Workaround Ignore the "Uncertainty" selection option for percentiles. In case of nested grids, select the time series file explicitly with button "Load File".
Resolved 2015-11-05 (2.2.10)

Problem 2015-05-27
Applies to Lasport up to 2.2.5


Extrapolation of climb profiles beyond their definition range in emission calculations

In emission calculations with profile-based times-in-mode and a specified maximum height exceeding the definition height of a climb profile, the profile is not extended with constant slope as it is the case for the dispersion calculation but assumed to be flat up to a distance of 50 km. This leads to increased emissions in segment CF in file LspEmis.log (in contrast to file LspTrans.log). The definition height for certification-based profiles is at least 915.0 m and for performance-based profiles it is 914.4 m. 

Workaround Always chose a maximum height for emission calculations (menu "Analyse" or parameter "Zmax" in file _analyse.csv) equal or below 915.0 m in certification-based emission calculations and equal or below 914.4 m in performance-based emission calculations.
Resolved 2015-05-27 (Lasport 2.2.6)